Hi, I have a number of voice agents setup to handle inbound calls. None of those agents are workging at the moment, all calls hangup before being answered. I have credits on both Twilio and VAPI. Is there a service issue, or is it just my account?

Thank you for the details. To help diagnose whether this is a service issue or specific to your account, could you please provide the Call ID and timestamp of a recent failed call from your Vapi dashboard? This will allow us to review the exact error and guide you further. Sources: - [Debugging voice agents](https://docs.vapi.ai/debugging) - [Troubleshoot call errors](https://docs.vapi.ai/calls/troubleshoot-call-errors) - [How to report issues](https://docs.vapi.ai/issue-reporting)

Sounds more like a routing or webhook failure than credits when calls drop before pickup, it’s usually Twilio not reaching your Vapi endpoint or the assistant failing to initialize in time. I’d double-check your Twilio number config (voice URL / SIP / webhook response) and see if any recent changes were made. Also worth checking logs on both sides to see where the drop happens exactly. Are you seeing the call hit Vapi at all, or is it dying completely on the Twilio side? @james_apex

Hi Matt, no logs inside VAPI, or twilio.

Have you been able to solve this or you still need help? @james_apex

If there are no logs on both Twilio and Vapi, the call likely isn’t even reaching either endpoint usually points to number config or routing upstream. I’d recheck the Twilio number’s voice handler (URL/SIP) and confirm it’s still pointed correctly, plus test with a simple fallback webhook. Also try calling the Twilio number from another line to rule out carrier-level blocking or misrouting. Did you recently change the number config or connect it through anything like SIP or a proxy layer? @james_apex