StatOSS

Twilio API uptime

Twilio API, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.

api.twilio.com/2010-04-01/Accounts.jsonEvery 5 minutes

Twilio API is up.

Up for 51 d 10 h. Last checked 2026-11-20 18:51 UTC from Sydney, Australia: 401 in 1,151 ms.

Last 24 hours

Up for 51 d 10 h100% passed

287 checks, median 130 ms from Falkenstein, all passed

95% under 138 ms

Response time by region
EuropeEurope130 ms
N. AmericaNorth America217 ms
AsiaAsia655 ms
OceaniaOceania467 ms

Medians over this range, on one scale up to 800 ms.

Last 90 days

Up for 51 d 10 h100% passed

14,804 checks, median 132 ms from Falkenstein, all passed

95% under 320 ms

Response time by region
EuropeEurope132 ms
N. AmericaNorth America214 ms
AsiaAsia584 ms
OceaniaOceania478 ms

Medians over this range, on one scale up to 800 ms. Europe's places are scaled to Falkenstein, its fastest shared place.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:56 UTC.

In the last 30 days Twilio API passed 8,862 of 8,862 checks, 100%.

No outage since checks began on 30 Sep 2026.

Availability

The share of checks that passed, and the outages that began, in each window up to now.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,014 of 2,0140
30 days100%8,862 of 8,8620
90 daysNot enough history yet: checks began on 30 Sep 2026

A year of checks is kept; the year's figure appears here once there is a year of them.

Response time by location

Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.

FromMedian95th percentileMeanChecks
Falkenstein, Germany132 ms141 ms134 ms421
Helsinki, Finland135 ms152 ms138 ms42
Ashburn, USA220 ms361 ms223 ms502
Copenhagen, Denmark148 ms331 ms185 ms42
Singapore636 ms918 ms653 ms503
Sydney, Australia451 ms940 ms534 ms505

Outages

None detected since checks began on 30 Sep 2026.

What is checked

APIs for SMS, voice calls, WhatsApp and phone verification.

StatOSS sends GET https://api.twilio.com/2010-04-01/Accounts.json and counts the check as passed on status 401 within 10 seconds. The REST API's list of accounts, under the API version every SMS and call request still uses. Without credentials it answers 401.

The API taking a request is not the message arriving: carriers and delivery are not checked.

Twilio API reports its own incidents at status.twilio.com. The figures here are measured from outside and can differ from it in both directions.

How it is measured

  • One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
  • A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 401.
  • A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
  • Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
  • Availability is the share of checks that passed. There are no maintenance windows: every check counts.

It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.