Intermittent Webhook Delivery Issues - Getting 200...
# support
s
Having a weird issue that started about 2 days ago and wondering if anyone else has experienced this: Vapi is showing successful 200 responses for webhook/tool calls in the dashboard, but these requests are never actually hitting my server. My logs show zero incoming requests for these "successful" calls. What I'm Seeing: - Tool calls showing 200 status with empty
{}
responses - Duration around 20 seconds (suggests timeout) - AI says things like "Let me try again" when tools fail - Affects various endpoints randomly - sometimes works, sometimes doesn't Impact: Random failures across the entire call flow - sometimes directory lookups fail, sometimes transfers break mid-process, sometimes calls won't even start. Technical Setup: - Server is up and responsive - Comprehensive logging shows all requests - If server was down, should get 404/500, not 200 responses The timing (started 2 days ago) makes me think it might be a platform-wide issue rather than something on my end.
k
Send your call ID
s
Call ID: 033084a3-9bb9-40e3-9d5b-753356e389a6 Endpoint: /representatives Tool Call IDs from your logs: call_DDkARseIn7K14jmeKEIteQBf (14:21:48.932 - 14:22:08.938) call_N5nssteuzh0mMczO1G2HVSK4 (14:21:26.732 - 14:21:46.738)
The key issue here is that I have zero logs showing any incoming requests for these timestamps. It's not that my server is receiving the requests and taking 20 seconds to respond - no requests are hitting my server at all. If my server was receiving these webhook calls and timing out, I would see the request logs. The fact that your system shows 200 responses with {} bodies suggests the requests are being intercepted or phantom-responded to before they reach my actual server endpoint.
Update: Ran 100 consecutive tests - 100% success rate, 0.036s avg response time. Meanwhile Vapi webhooks timeout at 20s with empty responses.
============================================================ 📊 SUMMARY ============================================================ ✅ Successful tests: 100/100 ❌ Failed tests: 0/100 ⏱️ Average duration: 0.036s ⏱️ Min duration: 0.014s ⏱️ Max duration: 0.066s
The /representatives endpoint is particularly telling because it's the simplest possible case, no computation required because just returns a static JSON file; and no database calls, because pure file serving. I'm not computing anything "new".
Your logs show 200 OK responses with empty {} bodies after 20-second timeouts. This is not possible, standard timeout responses should be: 504 Gateway Timeout 408 Request Timeout 500 Internal Server Error Connection failure/reset NEVER 200 OK - which means "Success, request processed" The fact that you're logging 200 responses for requests that never reached our server proves your system is generating phantom success responses internally.
I also have an ongoing email thread with support, in which they confirm that the requests had a 20-second timeout. However, I don't know the name of the support specialist because the email was not signed, so I cannot provide that information.
Update: Investigating if corporate firewall might be blocking some webhook calls intermittently. What are Vapi's webhook source IP ranges?
@Kings_big💫
k
looking into it
s
@Kings_big💫 any updates?
c
No update yet
k
Vapi’s webhook source IPs are 44.229.228.186/32 and 44.238.177.138/32
2 Views