CheckUpstream measured Twilio at 100.000% availability across 2818 independent checks (global · api). 813 incidents were recorded in the past 12 months; the most recent resolved earlier today after 5 hours. Status signals are polled from Twilio's official Atlassian Statuspage status page, alongside independent probes and community reports. Twilio publishes 1 product-level SLA uptime commitment (up to 99.95%), and service credits must be claimed within 30 days of a breach.
30 days measured availability how this is computed
100.000%
global · api · n=2818 · p95 302ms (30d)
Share of our own checks against Twilio endpoints that returned Twilio's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 172 incidents · 4 of 30 days with none posted · 7d 17h of declared impact
Within Twilio's published 99.95% target for this window.
No tracked service had more incidents in the last 30 days (181 logged here).
Share of each window with no impact declared by Twilio
7d
70.554%
30d
74.214%
90d
90.790%
180d
88.542%
1y
91.318%
Downtime like this can be refundable
If you're a paying Twilio customer, outages in these windows may count against Twilio's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Twilio entitlement →Does Twilio actually matter to you?
A Twilio outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Predicted resolution
n=764~341m (p25 189m – p75 752m)
Based on 764 historical Minor incidents · currently 15247m elapsed.
From 164 incidents Twilio published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Twilio takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Excluded: 8 still open.
Sep 1, 01:28 UTC · in progress · Identified
Aug 31, 23:06 UTC · resolved in 4h 38m · Resolved
Aug 31, 20:30 UTC · in progress · Monitoring
Live Twilio status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/twilio)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Twilio is currently Degraded. CheckUpstream tracks Twilio in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Twilio's last resolved incident started earlier today and lasted 4h 38m (degraded performance).
Looking for the live "is Twilio down" view? See the Twilio Live status page.
Aug 31, 19:45 UTC · in progress · Monitoring
Aug 30, 15:54 UTC · resolved in 5h 15m · Resolved
Aug 30, 07:28 UTC · resolved in 12h 21m · Resolved
Aug 29, 19:42 UTC · resolved in 18m · Resolved
Aug 29, 19:29 UTC · resolved in 17h 10m · Resolved
Aug 29, 05:50 UTC · resolved in 5h 19m · Resolved
Aug 29, 04:09 UTC · resolved in 4h 30m · Resolved
Aug 28, 23:36 UTC · resolved in 22h 53m · Resolved
Aug 28, 22:38 UTC · resolved in 9h 2m · Resolved
Aug 28, 21:56 UTC · resolved in 2d 8h · Resolved
Aug 28, 21:50 UTC · resolved in 1h 29m · Resolved
Twilio's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Twilio endpoints. It is the share of checks that returned the expected response, not a figure taken from Twilio's status page.
Sign up to CheckUpstream and add Twilio to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Twilio's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.