Payments & messaging APIs
Is Twilio down?
Live Twilio status, measured independently. We probe 6 Twilio endpoints from monitoring regions on every continent and record every outage we detect.
Twilio is up
Our probes are reaching Twilio normally from every region we check from.
Checked every minute from 6 regions on every continent.
- 24h uptimeUptime, 24 hours
- 7d uptimeUptime, 7 days
- 30d uptimeUptime, 30 days
- Website100% uptime, 30 days5 regions, 34 to 143 msCheckingp5091 msMedian responsep95235 msSlowest 5% of checks200 ms100024 h ago12 h agonow
- REST API99.33% uptime, 30 days6 regions, 147 to 578 msCheckingp50371 msMedian responsep95634 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Console99.99% uptime, 30 days5 regions, 310 to 1037 msCheckingp50653 msMedian responsep95825 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- SendGrid API99.99% uptime, 30 days6 regions, 160 to 664 msCheckingp50382 msMedian responsep95590 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Documentation99.98% uptime, 30 days5 regions, 38 to 183 msCheckingp50113 msMedian responsep95258 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Official status feed99.90% uptime, 30 days5 regions, 136 to 505 msCheckingp50307 msMedian responsep95451 msSlowest 5% of checks500 ms250024 h ago12 h agonow
Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet
Get notified when Twilio goes down
Follow these 6 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Twilio goes down. They don't count against your monitor quota. Free plan, no card required.
About Twilio outages
Twilio sends the SMS one-time codes, voice calls, and WhatsApp messages behind login and notification flows for a very large number of applications. A Twilio incident often looks like users not receiving verification codes rather than an obvious outage.
Carrier-side delivery problems are frequent and are outside what any API probe can see. We probe Twilio's website, REST API, Console, documentation, and the SendGrid email API, and link the official page, which lists carrier and country-level issues.
What we check
Every row is a real monitor in Uptimy, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website twilio.com is unreachable. | httpwww.twilio.com/en-us | HTTP 200 | 1 min |
REST API The Twilio API is not answering with its normal authentication response. Message and call requests fail. | httpapi.twilio.com/2010-04-01/Accounts.json | HTTP 401 | 1 min |
Console The Twilio Console is unreachable. | httpconsole.twilio.com | HTTP 200 | 2 min |
SendGrid API The SendGrid email API is not answering its normal authentication challenge. Transactional email sends fail. | httpapi.sendgrid.com/v3/user/profile | HTTP 401 | 2 min |
Documentation Twilio's documentation is unreachable. | httpwww.twilio.com/docs | HTTP 200 | 5 min |
Official status feed Twilio's status page is unreachable. | httpstatus.twilio.com/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Twilio's official status page.
Embed a live Twilio badge
A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.
Preview
Markdown
[](https://www.upti.my/status/twilio?utm_source=badge)HTML
<a href="https://www.upti.my/status/twilio?utm_source=badge"><img src="https://www.upti.my/status/twilio/badge.svg" alt="Twilio status"></a>Recent Twilio outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Twilio is up. Is your Twilio integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Twilio and fail quietly. Here is what teams that rely on Twilio monitor on their side.
Delivery, not just acceptance
Twilio accepting a message does not mean it arrived. Track delivery status webhooks and alert when the delivered rate drops.
Webhook monitoringOTP login flows
A browser check that requests a code through your own flow tells you when signups are blocked, whatever the cause.
Browser checksTwilio status: frequently asked questions
Usually not globally. Carrier filtering and country-specific routing problems are common and are listed on Twilio's official page under the affected country. Our API probe confirms whether Twilio is accepting requests at all.
Look at the per-region results above. If our probes fail from every region, Twilio has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Twilio may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Twilio" above: your Uptimy workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Twilio: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Other payments & messaging apis
Uptimy is not affiliated with Twilio. Twilio and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.