Is Twilio down?
Twilio.com is currently experiencing an incident
An incident has been reported for Twilio.
The other half
Is it Twilio, or is it you?
This page answers half the question. It tells you about Twilio. It cannot tell you whether your own site is experiencing an incident, and that is the part your users notice. UptimeRobot checks your websites, APIs and servers, and tells you when one of them does.
50 monitors for your own websites. No card.
Current status
Incident
Incident reported 6h 52m 28s ago
Last check
Checked every 5 minutes
Last 24 hours
0.000%
Checks on provider website have reported 1 incident, 1d down
Response time
N/A
Average
N/A
Minimum
N/A
Maximum
The response-time chart above shows Twilio's status over time, based on our automated checks. Each point on the chart represents the result of a check run every 5 minutes.
Last 7 days
0.000%
1 incident, 7d down
Last 30 days
0.003%
1 incident, 24d, 6h, 9m, 25s down
Last 365 days
0.003%
1 incident, 24d, 6h, 9m, 25s down
Latest incidents
View 2026 Twilio outage archive →
How our status checker works?
We continuously monitor Twilio from our own infrastructure to give you an objective view of its status. Every every 5 minutes, we send a request to twilio.com from our primary location in the US and verify that the site responds correctly and within a normal time frame.
If the first check fails, we immediately repeat it from a second location to avoid false positives. When that second attempt also fails, we trigger a third confirmation check from a random global location. Only if all three checks confirm a problem, we mark Twilio as having an issue or a major outage.
Frequently asked questions
An incident has been reported for Twilio. See Latest incidents below for details.
An incident has been reported for Twilio, so the problem may not be on your side.
Try opening twilio.com from another browser, device, or network (e.g., mobile hotspot). You can also disable your VPN, clear DNS cache, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed Twilio outage.
We monitor twilio.com from our own infrastructure. When a check fails, we repeat the test from two other randomly chosen global locations to eliminate false positives. If these checks fail too, we mark Twilio as down.
A Twilio outage means our checks detected that twilio.com was not responding correctly after multiple checks from different global locations. This doesn't always mean every user is affected. Some outages are regional, some affect only certain features, and some appear as slow loading instead of a full failure.
Not exactly. UptimeRobot monitors twilio.com from the outside, so we can detect when something is wrong and show high-level symptoms such as connection timeouts, HTTP errors, or failed responses from specific regions.
However, we don't have visibility into internal systems, so we can't identify the exact root cause (like a failed deployment, database issue, or infrastructure problem).
What we can show you:
- When the issue started and when it was resolved
- How long the outage lasted
- Which regions were affected
- The type of error observed (for example, timeouts or HTTP status codes like 500 or 404)
For detailed root cause information and official updates, we recommend checking Twilio's official status page.
Yes, UptimeRobot lets you set up your own monitors for twilio.com so you get alerted the moment something goes wrong, and before your users notice. Our free plan includes 50 monitors with 5-minute check intervals. You'll also get details that this public status page doesn't show, such as response headers, response body, region-level results, and a full activity log.
Create a free UptimeRobot account and set up a monitor for twilio.com. You'll receive alerts via email, SMS, Slack, webhooks, and other integrations as soon as we detect an issue, and again when it's resolved. Because we monitor independently from Twilio's own infrastructure, you may be notified even before their official status page acknowledges the issue.
Alternatively, you can check whether Twilio offers notifications on its official status page.
Over the last 5 years, the average resolved outage for Twilio lasted 13h 14m. That average is the mean difference between created_at and resolved_at across 97 resolved incidents we track for this provider.
Over the last 5 years, Twilio appears on our outage timeline 100 times. Comparable communication tools averaged 22.4 incidents in the same period, so Twilio has more incidents than the average communication tool.
