Skip to content

Outage tracker / Twilio

Is Twilio down?

I'm having a problem

Operationalchecked 6 minutes ago

We reached Twilio from all 10 regions we check.

As of Oct 5, 2026, 8:11 PM UTC, Twilio answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

Twilio reports an active incident: "SMS Delivery Delays From a Subset of Twilio Short Codes to Brisanet Brazil" (minor incident, since Oct 5, 2026, 2:49 PM 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 Oct 5, 2026, 8:11 PM UTC
US-East174 msOperational
US-West216 msOperational
Europe239 msOperational
Asia-Pacific311 msOperational
US-Central349 msOperational
Canada166 msOperational
UK127 msOperational
Southeast Asia980 msOperational
Australia494 msOperational
South America429 msOperational
their status pagetheir claim, not our reading

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

from Twilio's own status page, checked Oct 5, 2026, 7:58 PM UTC

Twilio reports an active incident: SMS Delivery Delays From a Subset of Twilio Short Codes to Brisanet Brazil (minor incident, since Oct 5, 2026, 2:49 PM 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 10 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 v3Operational
  • 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 AmericaDegraded performance
  • MMS Long Code, North AmericaOperational
  • Peer-to-Peer RoomsOperational
  • SIP Interface AU1Operational
  • SIP Interface IE1Operational
  • SIP Interface US1Operational
  • SMTPOperational
  • Termination AU1Operational
  • Termination IE1Operational
  • Termination US1Operational
  • VerifyOperational
  • Zipwhip Support TicketingOperational
  • API v2Operational
  • 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
396msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 314ms2026-09-07 UTC: p95 288ms2026-09-08 UTC: p95 314ms2026-09-09 UTC: p95 557ms2026-09-10 UTC: p95 416ms2026-09-11 UTC: p95 432ms2026-09-12 UTC: p95 305ms2026-09-13 UTC: p95 342ms2026-09-14 UTC: p95 408ms2026-09-15 UTC: p95 366ms2026-09-16 UTC: p95 569ms2026-09-17 UTC: p95 649ms2026-09-18 UTC: p95 624ms2026-09-19 UTC: p95 563ms2026-09-20 UTC: p95 546ms2026-09-21 UTC: p95 568ms2026-09-22 UTC: p95 465ms2026-09-23 UTC: p95 483ms2026-09-24 UTC: p95 425ms2026-09-25 UTC: p95 470ms2026-09-26 UTC: p95 400ms2026-09-27 UTC: p95 353ms2026-09-28 UTC: p95 492ms2026-09-29 UTC: p95 475ms2026-09-30 UTC: p95 470ms2026-10-01 UTC: p95 527ms2026-10-02 UTC: p95 511ms2026-10-03 UTC: p95 368ms2026-10-04 UTC: p95 470ms2026-10-05 UTC: p95 396ms
Sep 6Sep 20Oct 5
US-West
435msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 767ms2026-09-07 UTC: p95 643ms2026-09-08 UTC: p95 465ms2026-09-09 UTC: p95 313ms2026-09-10 UTC: p95 338ms2026-09-11 UTC: p95 574ms2026-09-12 UTC: p95 374ms2026-09-13 UTC: p95 271ms2026-09-14 UTC: p95 285ms2026-09-15 UTC: p95 534ms2026-09-16 UTC: p95 540ms2026-09-17 UTC: p95 584ms2026-09-18 UTC: p95 558ms2026-09-19 UTC: p95 554ms2026-09-20 UTC: p95 559ms2026-09-21 UTC: p95 708ms2026-09-22 UTC: p95 776ms2026-09-23 UTC: p95 475ms2026-09-24 UTC: p95 561ms2026-09-25 UTC: p95 628ms2026-09-26 UTC: p95 744ms2026-09-27 UTC: p95 493ms2026-09-28 UTC: p95 506ms2026-09-29 UTC: p95 730ms2026-09-30 UTC: p95 644ms2026-10-01 UTC: p95 568ms2026-10-02 UTC: p95 433ms2026-10-03 UTC: p95 450ms2026-10-04 UTC: p95 468ms2026-10-05 UTC: p95 435ms
Sep 6Sep 20Oct 5
Europe
334msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 226ms2026-09-07 UTC: p95 263ms2026-09-08 UTC: p95 339ms2026-09-09 UTC: p95 330ms2026-09-10 UTC: p95 394ms2026-09-11 UTC: p95 383ms2026-09-12 UTC: p95 212ms2026-09-13 UTC: p95 342ms2026-09-14 UTC: p95 332ms2026-09-15 UTC: p95 336ms2026-09-16 UTC: p95 663ms2026-09-17 UTC: p95 837ms2026-09-18 UTC: p95 787ms2026-09-19 UTC: p95 771ms2026-09-20 UTC: p95 768ms2026-09-21 UTC: p95 499ms2026-09-22 UTC: p95 415ms2026-09-23 UTC: p95 703ms2026-09-24 UTC: p95 710ms2026-09-25 UTC: p95 535ms2026-09-26 UTC: p95 273ms2026-09-27 UTC: p95 257ms2026-09-28 UTC: p95 499ms2026-09-29 UTC: p95 490ms2026-09-30 UTC: p95 435ms2026-10-01 UTC: p95 403ms2026-10-02 UTC: p95 494ms2026-10-03 UTC: p95 384ms2026-10-04 UTC: p95 328ms2026-10-05 UTC: p95 334ms
Sep 6Sep 20Oct 5
Asia-Pacific
793msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 716ms2026-09-07 UTC: p95 804ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 789ms2026-09-10 UTC: p95 874ms2026-09-11 UTC: p95 845ms2026-09-12 UTC: p95 903ms2026-09-13 UTC: p95 666ms2026-09-14 UTC: p95 770ms2026-09-15 UTC: p95 833ms2026-09-16 UTC: p95 818ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 827ms2026-09-20 UTC: p95 692ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 813ms2026-09-23 UTC: p95 757ms2026-09-24 UTC: p95 767ms2026-09-25 UTC: p95 881ms2026-09-26 UTC: p95 903ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 942ms2026-09-29 UTC: p95 990ms2026-09-30 UTC: p95 810ms2026-10-01 UTC: p95 921ms2026-10-02 UTC: p95 873ms2026-10-03 UTC: p95 884ms2026-10-04 UTC: p95 839ms2026-10-05 UTC: p95 793ms
Sep 6Sep 20Oct 5
US-Central
628msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 624ms2026-09-07 UTC: p95 571ms2026-09-08 UTC: p95 414ms2026-09-09 UTC: p95 403ms2026-09-10 UTC: p95 567ms2026-09-11 UTC: p95 895ms2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 372ms2026-09-14 UTC: p95 627ms2026-09-15 UTC: p95 401ms2026-09-16 UTC: p95 967ms2026-09-17 UTC: p95 544ms2026-09-18 UTC: p95 508ms2026-09-19 UTC: p95 455ms2026-09-20 UTC: p95 454ms2026-09-21 UTC: p95 546ms2026-09-22 UTC: p95 576ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 848ms2026-09-25 UTC: p95 581ms2026-09-26 UTC: p95 452ms2026-09-27 UTC: p95 513ms2026-09-28 UTC: p95 463ms2026-09-29 UTC: p95 440ms2026-09-30 UTC: p95 701ms2026-10-01 UTC: p95 474ms2026-10-02 UTC: p95 653ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 646ms2026-10-05 UTC: p95 628ms
Sep 6Sep 20Oct 5
Canada
512msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 510ms2026-09-07 UTC: p95 445ms2026-09-08 UTC: p95 460ms2026-09-09 UTC: p95 431ms2026-09-10 UTC: p95 495ms2026-09-11 UTC: p95 450ms2026-09-12 UTC: p95 403ms2026-09-13 UTC: p95 417ms2026-09-14 UTC: p95 592ms2026-09-15 UTC: p95 695ms2026-09-16 UTC: p95 717ms2026-09-17 UTC: p95 974ms2026-09-18 UTC: p95 880ms2026-09-19 UTC: p95 524ms2026-09-20 UTC: p95 484ms2026-09-21 UTC: p95 631ms2026-09-22 UTC: p95 526ms2026-09-23 UTC: p95 790ms2026-09-24 UTC: p95 725ms2026-09-25 UTC: p95 491ms2026-09-26 UTC: p95 968ms2026-09-27 UTC: p95 936ms2026-09-28 UTC: p95 436ms2026-09-29 UTC: p95 504ms2026-09-30 UTC: p95 808ms2026-10-01 UTC: p95 514ms2026-10-02 UTC: p95 654ms2026-10-03 UTC: p95 699ms2026-10-04 UTC: p95 483ms2026-10-05 UTC: p95 512ms
Sep 6Sep 20Oct 5
UK
264msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 350ms2026-09-07 UTC: p95 289ms2026-09-08 UTC: p95 321ms2026-09-09 UTC: p95 287ms2026-09-10 UTC: p95 264ms2026-09-11 UTC: p95 330ms2026-09-12 UTC: p95 288ms2026-09-13 UTC: p95 338ms2026-09-14 UTC: p95 250ms2026-09-15 UTC: p95 254ms2026-09-16 UTC: p95 689ms2026-09-17 UTC: p95 735ms2026-09-18 UTC: p95 754ms2026-09-19 UTC: p95 389ms2026-09-20 UTC: p95 322ms2026-09-21 UTC: p95 246ms2026-09-22 UTC: p95 319ms2026-09-23 UTC: p95 369ms2026-09-24 UTC: p95 321ms2026-09-25 UTC: p95 405ms2026-09-26 UTC: p95 518ms2026-09-27 UTC: p95 534ms2026-09-28 UTC: p95 750ms2026-09-29 UTC: p95 463ms2026-09-30 UTC: p95 372ms2026-10-01 UTC: p95 373ms2026-10-02 UTC: p95 331ms2026-10-03 UTC: p95 403ms2026-10-04 UTC: p95 418ms2026-10-05 UTC: p95 264ms
Sep 6Sep 20Oct 5
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 956ms2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 967ms2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 830ms2026-09-15 UTC: p95 897ms2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 944ms2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 958ms2026-10-01 UTC: p95 939ms2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
Australia
856msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 978ms2026-09-07 UTC: p95 929ms2026-09-08 UTC: p95 896ms2026-09-09 UTC: p95 973ms2026-09-10 UTC: p95 837ms2026-09-11 UTC: p95 849ms2026-09-12 UTC: p95 938ms2026-09-13 UTC: p95 798ms2026-09-14 UTC: p95 840ms2026-09-15 UTC: p95 846ms2026-09-16 UTC: p95 896ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 883ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 952ms2026-09-22 UTC: p95 969ms2026-09-23 UTC: p95 888ms2026-09-24 UTC: p95 899ms2026-09-25 UTC: p95 900ms2026-09-26 UTC: p95 952ms2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 875ms2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 874ms2026-10-01 UTC: p95 871ms2026-10-02 UTC: p95 985ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 893ms2026-10-05 UTC: p95 856ms
Sep 6Sep 20Oct 5
South America
922msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 780ms2026-09-07 UTC: p95 990ms2026-09-08 UTC: p95 945ms2026-09-09 UTC: p95 717ms2026-09-10 UTC: p95 866ms2026-09-11 UTC: p95 649ms2026-09-12 UTC: p95 599ms2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 896ms2026-09-15 UTC: p95 769ms2026-09-16 UTC: p95 892ms2026-09-17 UTC: p95 942ms2026-09-18 UTC: p95 870ms2026-09-19 UTC: p95 786ms2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 793ms2026-09-23 UTC: p95 749ms2026-09-24 UTC: p95 683ms2026-09-25 UTC: p95 840ms2026-09-26 UTC: p95 784ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 773ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 750ms2026-10-02 UTC: p95 990ms2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 844ms2026-10-05 UTC: p95 922ms
Sep 6Sep 20Oct 5

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, function by function

Twilio answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIUS-East: Awaiting dataUS-West: Awaiting dataEurope: Awaiting dataAsia-Pacific: Awaiting dataUS-Central: Awaiting dataCanada: Awaiting dataUK: Awaiting dataSoutheast Asia: Awaiting dataAustralia: Awaiting dataSouth America: Awaiting data

Get an email when we see Twilio go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Twilio, and again when they can reach it again. That is our own measurement from ten regions, not Twilio's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 174msstatus code: 401checked: Oct 5, 2026, 8:11 PM 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: 216msstatus code: 401checked: Oct 5, 2026, 8:11 PM 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.
    • US-Central
      Operationallatency: 349msstatus code: 401checked: Oct 5, 2026, 8:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Twilio normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 166msstatus code: 401checked: Oct 5, 2026, 8:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Twilio normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 429msstatus code: 401checked: Oct 5, 2026, 8:00 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Twilio normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 239msstatus code: 401checked: Oct 5, 2026, 8:10 PM 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.
    • UK
      Operationallatency: 127msstatus code: 401checked: Oct 5, 2026, 8:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Twilio normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 311msstatus code: 401checked: Oct 5, 2026, 8:11 PM 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.
    • Southeast Asia
      Operationallatency: 980msstatus code: 401checked: Oct 5, 2026, 8:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Twilio normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 494msstatus code: 401checked: Oct 5, 2026, 8:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Twilio normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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

SMS Delivery Delays From a Subset of Twilio Short Codes to Brisanet Brazildeclared on their status page2026-10-05
Voice Call Failures from Network Subscribers to a Subset of Twilio France Phone Numbers, 3h 18mdeclared on their status page2026-10-05
SMS Delivery Delays and Failures between Twilio Long Codes and Multiple Networks in France, 5h 40mdeclared on their status page2026-10-05
Delayed Messaging Logs and Status Callbacks in IE1 Region, 2h 14mdeclared on their status page2026-10-05
SMS Delivery Delays from a Subset of Twilio Long Codes to AT&T United States, 19mdeclared on their status page2026-10-05
SMS Delivery Delays from a Subset of Twilio Phone Numbers to Cellcom Israel, 10h 30mdeclared on their status page2026-10-04
Degraded Service in london-ix edge in ie1 TNX, 36mdeclared on their status page2026-10-03
SMS Delivery Delays from Twilio to Banglalink Bangladesh, 8h 33mdeclared on their status page2026-10-03

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

Put this badge in your README

Twilio uptime measured by RealUptimeLive, 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

At or above your target

We measured none of downtime for Twilio over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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 10 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. Read the full methodology.