Skip to content

Outage tracker / Twilio

Is Twilio down?

I'm having a problem

Vendor reports an incidentWhat Twilio reports

Twilio reports an incident on its status page: Issue with 500 Errors on Porting Request Submissions.

Impact: minor. Since 2026-10-22 17:10 UTC.

Latest update, 2026-10-22 18:16 UTC: We have identified the issue with 500 Errors on Porting Request Submissions. This issue is affecting wireless only submissions on the Port-in US Toll-free and Port a number tabs. The Port-in US Local tab is still currently functional and the Port-in API is still functional. We are actively working to resolve this issue. If customers have an urgent porting request, they can submit it manually by sending an email to porting@twilio.com at this time. We will provide another update in 2 hours or as soon as additional information is available.

5 more incidents are open on its status page.

Twilio's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 5 minutes ago

Our checks of Twilio pass from all 10 regions we check.

As of Oct 22, 2026, 7:00 PM UTC, RealUptime's checks of Twilio passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 7:00 PM UTC
US-East197 msChecks passing
US-West135 msChecks passing
Europe1015 msChecks passing
Asia-Pacific1126 msChecks passing
US-Central774 msChecks passing
Canada793 msChecks passing
UK181 msChecks passing
Southeast Asia889 msChecks passing
Australia823 msChecks passing
South America649 msChecks passing
their status pagetheir claim, not our reading

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

from Twilio's own status page, checked Oct 22, 2026, 3:33 PM UTC

Twilio reports an active incident: Issue with 500 Errors on Porting Request Submissions (minor incident, since Oct 22, 2026, 5:10 PM UTC)

Twilio's status page reports Partially Degraded Service. Our checks of Twilio currently pass with normal latency. Our checks currently pass 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 the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

Twilio's own component breakdown, as they publish it (our last read of their page failed, so this is the previous reading)

  • 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 AmericaOperational
  • MMS Long Code, North AmericaDegraded performance
  • 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
  • Verify EventsOperational
  • Bulk ExportOperational
  • 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 AmericaOperational
  • TaskRouterOperational
  • Customer Support CenterOperational
  • TwiML US1Operational
  • Voice, APACDegraded performance

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
949msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 395ms2026-10-06 UTC: p95 409ms2026-10-07 UTC: p95 495ms2026-10-08 UTC: p95 483ms2026-10-09 UTC: p95 487ms2026-10-10 UTC: p95 466ms2026-10-11 UTC: p95 458ms2026-10-12 UTC: p95 628ms2026-10-13 UTC: p95 623ms2026-10-14 UTC: p95 591ms2026-10-15 UTC: p95 654ms2026-10-16 UTC: p95 631ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 872ms2026-10-20 UTC: p95 920ms2026-10-21 UTC: p95 834ms2026-10-22 UTC: p95 949ms
Sep 23Oct 7Oct 22
US-West
938msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 724ms2026-10-06 UTC: p95 548ms2026-10-07 UTC: p95 532ms2026-10-08 UTC: p95 498ms2026-10-09 UTC: p95 470ms2026-10-10 UTC: p95 569ms2026-10-11 UTC: p95 640ms2026-10-12 UTC: p95 634ms2026-10-13 UTC: p95 706ms2026-10-14 UTC: p95 644ms2026-10-15 UTC: p95 640ms2026-10-16 UTC: p95 689ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 788ms2026-10-22 UTC: p95 938ms
Sep 23Oct 7Oct 22
Europe
994msp95 · 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-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 330ms2026-10-06 UTC: p95 301ms2026-10-07 UTC: p95 387ms2026-10-08 UTC: p95 399ms2026-10-09 UTC: p95 267ms2026-10-10 UTC: p95 461ms2026-10-11 UTC: p95 315ms2026-10-12 UTC: p95 341ms2026-10-13 UTC: p95 281ms2026-10-14 UTC: p95 351ms2026-10-15 UTC: p95 302ms2026-10-16 UTC: p95 214ms2026-10-17 UTC: p95 377ms2026-10-18 UTC: p95 576ms2026-10-19 UTC: p95 541ms2026-10-20 UTC: p95 385ms2026-10-21 UTC: p95 601ms2026-10-22 UTC: p95 994ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.7sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 790ms2026-10-06 UTC: p95 932ms2026-10-07 UTC: p95 970ms2026-10-08 UTC: p95 824ms2026-10-09 UTC: p95 851ms2026-10-10 UTC: p95 887ms2026-10-11 UTC: p95 765ms2026-10-12 UTC: p95 658ms2026-10-13 UTC: p95 896ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 986ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22
US-Central
918msp95 · 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-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 682ms2026-10-06 UTC: p95 502ms2026-10-07 UTC: p95 437ms2026-10-08 UTC: p95 537ms2026-10-09 UTC: p95 507ms2026-10-10 UTC: p95 496ms2026-10-11 UTC: p95 543ms2026-10-12 UTC: p95 489ms2026-10-13 UTC: p95 519ms2026-10-14 UTC: p95 595ms2026-10-15 UTC: p95 548ms2026-10-16 UTC: p95 728ms2026-10-17 UTC: p95 410ms2026-10-18 UTC: p95 398ms2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 878ms2026-10-22 UTC: p95 918ms
Sep 23Oct 7Oct 22
Canada
934msp95 · 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-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 508ms2026-10-06 UTC: p95 745ms2026-10-07 UTC: p95 546ms2026-10-08 UTC: p95 660ms2026-10-09 UTC: p95 617ms2026-10-10 UTC: p95 647ms2026-10-11 UTC: p95 537ms2026-10-12 UTC: p95 612ms2026-10-13 UTC: p95 498ms2026-10-14 UTC: p95 491ms2026-10-15 UTC: p95 659ms2026-10-16 UTC: p95 650ms2026-10-17 UTC: p95 532ms2026-10-18 UTC: p95 853ms2026-10-19 UTC: p95 846ms2026-10-20 UTC: p95 746ms2026-10-21 UTC: p95 843ms2026-10-22 UTC: p95 934ms
Sep 23Oct 7Oct 22
UK
532msp95 · 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-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 293ms2026-10-06 UTC: p95 394ms2026-10-07 UTC: p95 444ms2026-10-08 UTC: p95 423ms2026-10-09 UTC: p95 406ms2026-10-10 UTC: p95 336ms2026-10-11 UTC: p95 314ms2026-10-12 UTC: p95 377ms2026-10-13 UTC: p95 371ms2026-10-14 UTC: p95 344ms2026-10-15 UTC: p95 278ms2026-10-16 UTC: p95 361ms2026-10-17 UTC: p95 285ms2026-10-18 UTC: p95 403ms2026-10-19 UTC: p95 545ms2026-10-20 UTC: p95 413ms2026-10-21 UTC: p95 360ms2026-10-22 UTC: p95 532ms
Sep 23Oct 7Oct 22
Southeast Asia
1.7sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.2s2026-10-06 UTC: p95 944ms2026-10-07 UTC: p95 995ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22
Australia
1.8sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 862ms2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 926ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 816ms2026-10-12 UTC: p95 927ms2026-10-13 UTC: p95 876ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22
South America
2.1sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 908ms2026-10-06 UTC: p95 916ms2026-10-07 UTC: p95 825ms2026-10-08 UTC: p95 820ms2026-10-09 UTC: p95 994ms2026-10-10 UTC: p95 918ms2026-10-11 UTC: p95 757ms2026-10-12 UTC: p95 810ms2026-10-13 UTC: p95 757ms2026-10-14 UTC: p95 980ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 599ms2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 2.1s
Sep 23Oct 7Oct 22

Check your own site while you wait on Twilio

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • 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

Email me when Twilio reports an incident on its status page, and again when it reports it resolved.

Get an email when Twilio reports an incident

Email me when Twilio reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Twilio's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 197msstatus code: 401checked: Oct 22, 2026, 6:59 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
      Checks passinglatency: 135msstatus code: 401checked: Oct 22, 2026, 6:59 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
      Checks passinglatency: 774msstatus code: 401checked: Oct 22, 2026, 6:50 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
      Checks passinglatency: 793msstatus code: 401checked: Oct 22, 2026, 6:49 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
    Checks passinglatency: 649msstatus code: 401checked: Oct 22, 2026, 6:49 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 1015msstatus code: 401checked: Oct 22, 2026, 7:00 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
      Checks passinglatency: 181msstatus code: 401checked: Oct 22, 2026, 6:49 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1126msstatus code: 401checked: Oct 22, 2026, 6:59 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
      Checks passinglatency: 889msstatus code: 401checked: Oct 22, 2026, 6:50 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
      Checks passinglatency: 823msstatus code: 401checked: Oct 22, 2026, 6:49 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 probe events

Issue with 500 Errors on Porting Request Submissionsdeclared on their status page2026-10-22
Issue with Realtime Transcriptions and Deepgram, 1h 36mdeclared on their status page2026-10-22
Intelligent Alerts Delivery Issues, 26mdeclared on their status page2026-10-22
Hosted Number Verification Calls not Reaching Customersdeclared on their status page2026-10-22
SMS Delivery Delays and Failures from Twilio to Malitel Malideclared on their status page2026-10-22
RCS Inbound Events Delayed, 46mdeclared on their status page2026-10-22
Billing Delays, 56mdeclared on their status page2026-10-22
SMS Delivery Delays from Twilio to MTN Nigeria, 5h 1mdeclared on their status page2026-10-22

check 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 check readings and Twilio's own claim at the time, side by side.

Full check history for Twilio: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![Twilio uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Twilio down?", https://realuptime.io/outages/twilio. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

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

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.twilio.com

RealUptime is not affiliated with Twilio; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.