SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

How to Check if a Carrier Incident Is Causing Call Failures

Objective

If you are experiencing high call failures, dropped calls, or calls not reaching their destination, an active carrier incident may be the root cause. This article explains how to use the Twilio Status Page to check for known carrier incidents and determine whether an ongoing outage could be affecting your Programmable Voice calls.

 

Product

Programmable Voice

 

Environment

Twilio Console

 

User Account Permission/Role(s) Required 

No specific account permissions are required to view the Twilio Status Page. It is publicly accessible to all users.

 

Procedure 

Follow the steps below to check whether an active carrier incident may be related to the call failures you are observing.

  1. Visit the Twilio Status Page. 
  2. Review the current system status. On the main page, you will see an overview of all Twilio products and services. Look for any items marked as Degraded Performance, Partial Outage, or Major Outage.
  3. Check the Voice sections. Scroll down to find components related to Programmable Voice. These sections reflect the status of call routing and carrier connectivity.
  4. Open the Active Incidents section. If any incidents are listed, click on the incident title to view its details. Each incident page includes a description of the affected service, the geographic region or carrier impacted, and a timeline of updates.
  5. Compare the incident details with your call failures. To determine if the incident is related to your issue, verify the following:
  • Destination country or region: Check whether the incident affects the same country or region as the destination numbers in your failing calls.
  • Time window: Confirm that the incident start time overlaps with the period when your call failures began.
  • Carrier or route: If the incident specifies a particular carrier or route, check whether your call logs reference the same provider.
  1. Subscribe to status updates. To receive automatic notifications for future incidents, click Subscribe to Updates on the Status Page. You can choose to receive alerts by email, SMS, or RSS feed.
  2. Contact Twilio Support if needed. If you do not find an active incident that matches your issue, or if the incident is marked as resolved but you are still experiencing call failures, contact Twilio Support and share the affected Call SIDs so the team can investigate further.

 

Additional Information 

The following resources may help you investigate call failures in more detail:

  • Twilio Status Page: Check real-time status of all Twilio products and active incidents.
  • Twilio Voice Call Logs: View individual call records, SIP response codes, and call duration in the Twilio Console.
  • Twilio Voice Insights: Use Voice Insights to get detailed analytics and carrier-level data for your calls.

 

 

Have more questions? Submit a request
Powered by Zendesk