https://vapi.ai/ logo
Join Discord
Powered by
Is VAPI down? 524 errors, failed calls, concurrenc...
# support
a
We are experiencing many errors today with VAPI, org ID: 785a4230-e5b7-44df-ba87-c6f5cf5cf0b1. For example: Unknown status for all calls that are not answered, call ID = 480b556b-d9f6-47bc-807a-d73541d1841f, but there are many more. I can see in my Twilio console that these calls are unanswered, but VAPI seems to have missed reporting this status back. Additionally, we are encountering 524 error codes for assistant updates and "over concurrency limit" errors. We have a queuing mechanism in place and a 1-second delay between calls, yet we are still experiencing concurrency issues. How can we get notified if you experience downtime? It seems that status.vapi.ai is not entirely accurate.
a
HeyAkos Thank you for creating the ticket! A member of our team will reach out to you shortly.
v
message has been deleted
@Akos I'm sorry to hear that you're experiencing issues with VAPI. Let's address each of your concerns one by one: 1. For the unknown status of calls that are not answered, I will need to check the call status updates for the specific call ID you provided. I will initiate a status update check for call ID 480b556b-d9f6-47bc-807a-d73541d1841f. 2. Regarding the 524 error codes for assistant updates, this typically indicates a timeout occurred when attempting to reach our servers. I will report this to our technical team to investigate further. 3. For the "over concurrency limit" errors, even with a queuing mechanism and delay in place, it's possible that the number of simultaneous requests is exceeding the limit set for your organization. I will look into the current concurrency settings for your org ID and see if adjustments are necessary. 4. To get notified about downtime or any issues with VAPI, I recommend subscribing to our status page updates. If you find that the status page is not reflecting the actual service status, I will pass this feedback to our team to ensure that our status reporting is accurate and reliable. Please allow me some time to check on these issues and get back to you with more information. If you need immediate assistance, please reach out to our support team.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
a
@User any feedback on this?
s
@Akos can you try now and let me know how it goes for you.
a
Calls seem to be working now. Is the concurrency issue related to the unknown call statuses? Was that just a temporary issue?
s
Yes and soon it will be fixed as well.
a
@Shubham Bajaj We are experiencing the same "Unknown status" error issue. For example, callId="4eeb67b3-5202-41fe-8841-982666f89ce7". On the Twilio console, I see "No status." Currently, we have four calls with "Unknown status" in Vapi. Will this affect our concurrency limit again? Could you please check this for us? It's a bit frustrating.
s
@Akos DB outage, supabase is down https://status.supabase.com/
a
Actually it says : Jan 30, 2025 No incidents reported today. that call that I mentioned with id: 4eeb67b3-5202-41fe-8841-982666f89ce7 thats from today
Is the concurrency limit affected by this again, like yesterday?
s
3 Views
PreviousNext
Powered by