Is Twilio down right now?

Operational. We reached Twilio from all 4 regions we check.

How does RealUptime check if Twilio is down?

RealUptime checks Twilio with scheduled HTTP probes against its public, unauthenticated functional endpoints, run from named regions on a fixed cadence, plus an extra confirmation probe whenever a signal suggests a problem. This verifies that the functional endpoints we probe actually answer, not that every feature of Twilio works end to end.

What does "degraded" mean for Twilio?

Degraded means Twilio answered our probe but at several times its own seven-day median response time. Degraded only ever applies to a reading that answered: a surface that is down, or one that refused our probe, is reported as down or awaiting data instead, never softened into "degraded".

What is Twilio's current response time?

RealUptime's most recent measured response time for Twilio, by region: US-East: 225 ms, US-West: 90 ms, Europe: 161 ms, Asia-Pacific: 437 ms. This is the latest single probe reading per region, not an average.

When did RealUptime last check Twilio?

RealUptime's probes last checked Twilio at 2026-09-03T01:22:10.527Z.

Is Twilio down?

Short linkrlup.io/down/twilio

I'm having a problem

Operationalchecked 8 minutes ago

We reached Twilio from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Twilio (since Aug 20, 2026).

Twilio reports an active incident: "Unable to Login to Console" (all systems operational, since Sep 3, 2026, 12:56 AM UTC). That is their claim, not our measurement: our probes are currently reaching Twilio, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Sep 3, 2026, 1:22 AM UTC

US-East225 msOperational

US-West90 msOperational

Europe161 msOperational

Asia-Pacific437 msOperational

their status pagetheir claim, not our reading

Twilio reports: Minor incident (“Partially Degraded Service”)

from Twilio's own status page, checked Sep 3, 2026, 12:27 AM UTC

Twilio reports an active incident: Unable to Login to Console (all systems operational, since Sep 3, 2026, 12:56 AM UTC)

Twilio's status page reports Partially Degraded Service. Our probes are currently reaching Twilio successfully with normal latency. RealUptime's independent checks are currently succeeding from all 4 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

Twilio's own component breakdown, as they publish it

API v3Under maintenance
Authy 2FAOperational
ConsoleOperational
Conversation OrchestratorOperational
Flex Agent CopilotOperational
Group RoomsOperational
Mailsend: Comms APIOperational
Origination AU1Operational
Origination IE1Operational
Origination US1Operational
PSTN AU1Operational
PSTN IE1Operational
PSTN US1Operational
SMS Long Code, North AmericaOperational
SMS Long Code, North AmericaOperational
StudioOperational
Zipwhip Provisioner Dashboard and APIOperational
Conversation IntelligenceOperational
Event StreamsOperational
Event WebhooksOperational
Flex Agent DesktopOperational
FunctionsOperational
LogsOperational
MMS Long Code, North AmericaOperational
MMS Long Code, North AmericaDegraded performance
Peer-to-Peer RoomsOperational
SIP Interface AU1Operational
SIP Interface IE1Operational
SIP Interface US1Operational
SMTPUnder maintenance
Termination AU1Operational
Termination IE1Operational
Termination US1Operational
VerifyOperational
Zipwhip Support TicketingOperational
API v2Under maintenance
AssetsOperational
Authy AppOperational
Client Web AU1Operational
Client Web IE1Operational
Client Web US1Operational
Conversation Intelligence (classic)Operational
Debugger & AlarmsOperational
Dedicated IP AddressOperational
Flex Application PlatformOperational
Parse APIOperational
RecordingsOperational
SMS Short Code, North AmericaOperational
SMS Toll-Free, North AmericaOperational
Toll-Free Verification PortalOperational
BillingOperational
Client Mobile AU1Operational
Client Mobile IE1Operational
Client Mobile US1Operational
CompositionsOperational
Conversation MemoryOperational
DocumentationOperational
Flex InsightsOperational
LookupOperational
MMS Short Code, North AmericaOperational
MMS Toll-Free, North AmericaOperational
TwiML BinsOperational
Conference AU1Operational
Conference IE1Operational
Conference US1Operational
Enterprise KnowledgeOperational
Flex Queue StatsOperational
Network Traversal ServiceOperational
REST APIOperational
SMS Toll-Free, North AmericaOperational
SyncOperational
Bulk ExportDegraded performance
Flex Teams ViewOperational
Go RoomsOperational
MMS Toll-Free, North AmericaOperational
Recording AU1Operational
Recording IE1Operational
Recording US1Operational
Flex Admin ConsoleOperational
Queue AU1Operational
Queue IE1Operational
Queue US1Operational
Video InsightsOperational
Voice, North AmericaOperational
Flex RoutingOperational
Realtime TranscriptionsOperational
Text-to-Speech AU1Operational
Text-to-Speech IE1Operational
Text-to-Speech US1Operational
Voice, Latin AmericaOperational
Flex ConversationsOperational
Recording Transcriptions AU1Operational
Recording Transcriptions IE1Operational
Recording Transcriptions US1Operational
SMS, Latin AmericaDegraded performance
TaskRouterOperational
Customer Support CenterOperational
Flex Programmable ChatOperational
TwiML US1Operational
Voice, APACOperational

These are Twilio's components, named and scored by Twilio. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Twilio's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Twilio response time, by region

US-East

233msp95 · latest

1s500ms0ms

Aug 5Aug 19Sep 3

US-West

426msp95 · latest

1s500ms0ms

Aug 5Aug 19Sep 3

Europe

557msp95 · latest

1s500ms0ms

Aug 5Aug 19Sep 3

Asia-Pacific

944msp95 · latest

2s1s0ms

Aug 5Aug 19Sep 3

Is it Twilio, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Twilio -- it cannot diagnose Twilio's own systems.

What we measured, and what people reported

US-East
Operationallatency: 225msstatus code: 401checked: Sep 3, 2026, 1:08 AM UTC
0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Twilio normally. We do not have enough reports from US-East to say anything about what people there are seeing.
US-West
Operationallatency: 90msstatus code: 401checked: Sep 3, 2026, 1:01 AM UTC
0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Twilio normally. We do not have enough reports from US-West to say anything about what people there are seeing.
Europe
Operationallatency: 161msstatus code: 401checked: Sep 3, 2026, 1:21 AM UTC
0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Twilio normally. We do not have enough reports from Europe to say anything about what people there are seeing.
Asia-Pacific
Operationallatency: 437msstatus code: 401checked: Sep 3, 2026, 1:22 AM UTC
0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Twilio normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
US-Central
Not monitored from this regionTwilio is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Canada
Not monitored from this regionTwilio is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
UK
Not monitored from this regionTwilio is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Southeast Asia
Not monitored from this regionTwilio is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Australia
Not monitored from this regionTwilio is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
South America
Not monitored from this regionTwilio is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Twilio, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Twilio yet, which is not evidence that nothing is wrong.

Recent outages

Unable to Login to Consoledeclared on their status page2026-09-03

MMS Delivery Delays from Twilio to Multiple Networks in United Statesdeclared on their status page2026-09-03

RCS Registration Submission Issues in the United Statesdeclared on their status page2026-09-02

SMS Delivery Delays from a Subset of Twilio Short Codes to Algar Telecom Brazildeclared on their status page2026-09-02

SMS Delivery Receipt Delays From a Subset of Twilio Long Codes to H3G United Kingdomdeclared on their status page2026-09-02

SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in United States, 3h 10mdeclared on their status page2026-09-02

SMS Delivery Delays from Twilio to Multiple Networks in Spain, 3h 54mdeclared on their status page2026-09-02

SMS Delivery Delays from a Subset of Twilio Short Codes to Vivo Brazildeclared on their status page2026-09-02

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Twilio since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Twilio covering any window you pick, with our measurements and Twilio's own claim at the time, side by side.

Full availability history for Twilio: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Put this badge in your README

Live, from this page's own readings.

[![Twilio uptime measured by RealUptime](https://realuptime.io/outages/twilio/badge.svg?days=30)](https://realuptime.io/outages/twilio)

<a href="https://realuptime.io/outages/twilio"><img src="https://realuptime.io/outages/twilio/badge.svg?days=30" alt="Twilio uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Twilio's SLA implies, from our measurement

Window

What you pay per month

Uptime target in your contract

Include outages only one region saw (none)

At or above your target

We measured none of downtime for Twilio over the 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Twilio's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional

https://api.twilio.com/2010-04-01/Accounts

secondary

https://status.twilio.com/

RealUptime is not affiliated with Twilio; the name identifies what we measured, and nothing here speaks for Twilio's own team. We send a single web request to Twilio from 4 regions on our own schedule and time the response. We do not see inside Twilio's systems, do not use an account or real transaction, and are not the same signal Twilio's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Twilio is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Twilio operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.

Related services

Akamai Amplitude Anthropic Auth0 AWS (Amazon Web Services)