Space for ads
Checked every 5 minutes · How we measure this
As of 14:35 EDT on 8 Sep 2026, Twilio reports degraded or failing components on its own status page. Our probe still reached twilio.com in 58 ms, with 93.75% availability over the last 24 hours.
Availability is the share of our automated checks that succeeded in each interval. Response time is measured from our probe to twilio.com and excludes your own connection and browser rendering.
Reported by Twilio on its own status page. Verify on their status page.
Elastic SIP Trunking
0 problem reports
Twilio degraded performance
Detected by DownBits probe
Our Engineers are Investigating an Issue with Messaging.
Our engineers are currently investigating the customer impact of a retroactive issue with Messaging. We will follow up and provide customer impact details within 2 hours.
Confirmed on the vendor status page
SMS Delivery Failures from a Subset of Twilio Alphanumeric Sender IDs and Short Codes to Vodafone Italy
Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Alphanumeric Sender IDs and Short Codes to Vodafone network subscribers in Italy. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.
Confirmed on the vendor status page
SMS Delivery Failures From a Subset of Twilio Long Codes to Multiple Networks in France
We have observed a recovery in SMS delivery from a subset of Twilio Long Codes to network subscribers on multiple networks in France and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
Confirmed on the vendor status page
SMS Delivery Delays from Twilio to Megafon Tajikistan
We have observed a recovery in SMS delivery from Twilio to Megafon network subscribers in Tajikistan and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
Confirmed on the vendor status page
SMS Delivery Receipt Delays from a Subset of Twilio Long Codes to Nex-Tech Wireless United States
We have observed a recovery in SMS delivery receipts from a subset of Twilio Long Codes to Nex-Tech Wireless network subscribers in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
Confirmed on the vendor status page
MMS Delivery Delays from a Subset of Australia Subscribers to Twilio Australia Phone Numbers
Twilio customers may be experiencing MMS delivery delays from a Subset of network subscribers in Australia to Twilio Australia Phone Numbers. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.
Confirmed on the vendor status page
Twilio is reporting degraded or failing components on its own status page. Our probe is still reaching twilio.com normally — 24-hour availability from our checks is 93.75% — so the front door is up while something behind it is not. The component list on this page shows which parts Twilio says are affected. Last checked 8 minutes ago.
Measured from our automated checks, Twilio has been available 93.75% over 24 hours, 93.75% over 7 days, 93.75% over 30 days. We recorded 7 incidents in the last 30 days.
Twilio has averaged 228 ms across our successful checks in the past 24 hours, which is fast — comfortably within what a healthy service should return. Response time is measured from our probe to twilio.com and does not include rendering time in your browser.
Our probe is also failing to reach twilio.com normally, so this is not just you. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://twilio.com/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than Twilio. On Windows run ping twilio.com and nslookup twilio.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load twilio.com in a private or incognito window. If it works there, clear cookies and site data for twilio.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
