Where does this status come from?

From Twilio's own status page API at https://status.twilio.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Twilio's words.

How can my agent or app check Twilio status?

Fetch https://upbutler.com/status/twilio/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"twilio"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Twilio's?

Add "twilio" to the dependencies of your UpButler workspace. When one of your monitors fails while Twilio has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Twilio down?

Right now

Partly. Twilio is degraded.

SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in New Zealand.

Read from status.twilio.com 2 min ago · every 120s

For agents

proceed

Proceed, expect slow or flaky responses.

GET upbutler.com/status/twilio/status.agent.json

MCP: upstream_status {"service":"twilio"}

SMS, voice, WhatsApp and Verify. Carrier-level incidents are per country and very frequent: depend on the specific component you use.

What Twilio reports

Degraded· 7 open incidents

Taken as is from Twilio's own status page API. Incident titles and component names below are theirs.

Open status.twilio.com

UpButler's independent probe

API edge is answeringHTTP 401 · 170 ms

One request without credentials to api.twilio.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.

Checked 2 min ago · up since 2026-10-10 01:24 UTC

Open at Twilio

Elevated errors affecting Voice APImonitoring · impact none
Since 2026-10-10 05:08 UTC
We are aware of intermittent errors affecting the Voice service, which may impact customer API requests for Voice. From approximately 9:32 PM - 9:47 PM PST, customers may have experienced failed requests. Our team is monitoring system performance. We will provide another update as soon as more information becomes available.
SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in New Zealandidentified · impact minor
Since 2026-10-10 03:43 UTC · SMS, APAC
Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Short Codes to network subscribers on multiple networks in New Zealand. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 1 hour or as soon as more information becomes available.
SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Mobile Chinamonitoring · impact minor
Since 2026-10-09 06:42 UTC · SMS, APAC
We have completed our investigation and determined that this event did not result in any customer impact. All systems are operating normally.
SMS Delivery Delays from Twilio to Brisanet Brazilidentified · impact minor
Since 2026-10-07 14:02 UTC · SMS, Latin America
Twilio customers may be experiencing SMS delivery delays from Twilio to Brisanet network subscribers in Brazil. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.
SMS Delivery Delays and Failures from Twilio to Movistar El Salvadoridentified · impact minor
Since 2026-10-06 20:59 UTC · SMS, Latin America
Twilio customers may be experiencing SMS delivery delays and failures from Twilio to Movistar network subscribers in El Salvador. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.
MMS Delivery Delays from a Subset of Twilio Long Codes to GCI United Statesinvestigating · impact minor
Since 2026-09-26 03:16 UTC · MMS Long Code, North America
Twilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to GCI network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 24 hours or as soon as more information becomes available.
MMS Delivery Failures From A Subset Of Network Subscribers In Australia To Twilio Australia Phone Numbersinvestigating · impact minor
Since 2026-09-11 18:08 UTC · MMS, APAC
Twilio customers may be experiencing MMS delivery failures from a subset of network subscribers in Australia to a subset of Twilio Australia Phone Numbers. Our team is actively investigating this issue. We will provide another update in 24 hours or as soon as more information becomes available.
Marketing Campaigns Template Maintenancescheduled maintenance
Starts 2026-10-10 23:00 UTC · SendGrid Marketing Campaigns
To improve the reliability of our Marketing Campaign email templates, we are performing an emergency maintenance on our infrastructure on October 10, 2026 from 16:00 to 19:00 PDT. We do not expect any customer impact. In the unlikely event of an issue, customers may briefly be unable to save Marketing Campaigns templates. This does not impact mail send. Thank you for your patience during this maintenance.
United Kingdom Account Security Carrier Partner Maintenance - Threescheduled maintenance
Starts 2026-10-10 21:00 UTC · Verify Silent Network Auth, Lookup Identity Match, Lookup SIM Swap, Legacy Identity MatchAndAttributes
Our carrier partner Three United Kingdom is conducting a planned maintenance from 10 October 2026 at 14:00 PDT until 11 October 2026 at 02:00 PDT. During the maintenance window, there could be intermittent API request failures for Three United Kingdom customers. Impacted Products: Verify Silent Network Auth, Lookup SIM Swap, Lookup Identity Match, Legacy Identity MatchAndAttributes
Romania SMS Carrier Maintenance - Orangescheduled maintenance
Starts 2026-10-10 20:30 UTC · SMS, Europe
The Orange network in Romania is conducting a planned maintenance from 10 October 2026 at 13:30 PDT until 10 October 2026 at 13:31 PDT. During the maintenance window, there could be intermittent delays delivering SMS to and from Orange Romania handsets.

Text written by Twilio, shown unchanged.

Twilio components

5 of 80 not operational

ELASTIC SIP TRUNKING US1

Origination US1Operational
Termination US1Operational

DEVELOPER TOOLS

ConsoleOperational
Event StreamsOperational
Debugger & AlarmsOperational
DocumentationOperational
REST APIOperational
Bulk ExportOperational

ACCOUNT SECURITY

Authy 2FAOperational
VerifyOperational
Authy AppOperational
LookupOperational
Verify EventsOperational

PROGRAMMABLE VOICE US1

PSTN US1Operational
SIP Interface US1Operational
Client Web US1Operational
Client Mobile US1Operational
Conference US1Operational
Recording US1Operational

SERVERLESS

StudioOperational
FunctionsOperational
AssetsOperational
TwiML BinsOperational
SyncOperational

CARRIER NETWORK

SMS Long Code, North AmericaOperational
MMS Long Code, North AmericaDegraded
SMS Short Code, North AmericaOperational
MMS Short Code, North AmericaOperational
SMS Toll-Free, North AmericaOperational
MMS Toll-Free, North AmericaOperational
SMS, Latin AmericaDegraded
SMS, APACDegraded
MMS, APACDegraded
Lookup Line Type Intelligence [Legacy API]Degraded

PROGRAMMABLE VIDEO

Group RoomsOperational
Peer-to-Peer RoomsOperational
RecordingsOperational
CompositionsOperational
Network Traversal ServiceOperational
Go RoomsOperational

ZIPWHIP MESSAGING

SMS Long Code, North AmericaOperational
MMS Long Code, North AmericaOperational
SMS Toll-Free, North AmericaOperational
MMS Toll-Free, North AmericaOperational

ZIPWHIP TOOLS

Zipwhip Provisioner Dashboard and APIOperational
Zipwhip Support TicketingOperational
Toll-Free Verification PortalOperational

ELASTIC SIP TRUNKING AU1

Origination AU1Operational
Termination AU1Operational

ELASTIC SIP TRUNKING IE1

Origination IE1Operational
Termination IE1Operational

PROGRAMMABLE VOICE AU1

PSTN AU1Operational
SIP Interface AU1Operational
Client Web AU1Operational
Client Mobile AU1Operational
Conference AU1Operational

PROGRAMMABLE VOICE IE1

PSTN IE1Operational
SIP Interface IE1Operational
Client Web IE1Operational
Client Mobile IE1Operational
Conference IE1Operational

CONVERSATIONS

Conversation OrchestratorOperational
Conversation IntelligenceOperational
Conversation Intelligence (classic)Operational
Conversation MemoryOperational
Enterprise KnowledgeOperational

TWILIO EMAIL

Mailsend: Comms APIOperational
LogsOperational
Dedicated IP AddressOperational

SendGrid Mail Sending

API v3Operational
SMTPOperational
API v2Operational

FLEX

Flex Agent CopilotOperational
Flex Agent DesktopOperational
Flex Application PlatformOperational
Flex InsightsOperational
Flex Queue StatsOperational

SendGrid Webhooks

Event WebhooksOperational
Parse APIOperational

TWILIO PLATFORM

BillingOperational

Twilio incidents, last 90 days

17 finished incidents seen since UpButler started tracking on 2026-10-10. A typical one lasted 4 h 40 min; the longest 14 h 30 min.

Started (UTC)	Incident	Impact	Lasted
2026-10-09 12:59	SMS Delivery Delays from a Subset of Twilio Short Codes to Onvoy Spectrum Mobile United States	minor	2 h 51 min
2026-10-09 12:39	SMS Delivery Delays from Twilio Alphanumeric Sender Type to Telenor Norway	minor	4 h 1 min
2026-10-09 10:46	SMS Delivery Delays from Twilio to TIM and Noverca Italia Srl Italy	minor	4 h 40 min
2026-10-08 21:15	SMS Delivery Failures from a Subset of Twilio Alphanumeric Sender Type to Moov Côte d'Ivoire	minor	2 h 48 min
2026-10-08 19:47	SMS Delivery Delays from Twilio to Verizon United States	minor	8 h 33 min
2026-10-08 15:15	Voice Call Failures from a Subset of Twilio Phone Numbers to Norway	minor	5 h 14 min
2026-10-08 03:08	Twilio SMS Delivery Issues	minor	6 h 27 min
2026-10-07 15:09	SMS and MMS Delivery Receipt Delays from Twilio to AT&T United States	minor	7 h 25 min
2026-10-07 12:04	SMS Delivery Delays from Twilio to Brisanet Brazil	minor	58 min
2026-10-07 06:19	SMS and MMS Delivery Delays and Delivery Receipt Delays between Twilio and AT&T in the United States	minor	5 h 56 min
2026-10-06 20:47	SMS Delivery Delays from Twilio to O! Kyrgyzstan	minor	5 h 6 min
2026-10-06 20:16	Delays Viewing and Receiving Operator Results in Conversation Intelligence and Accessing Conversation Memory	minor	55 min
2026-10-06 13:38	SMS Delivery Delays from Twilio to MTN Nigeria	minor	14 h 30 min
2026-10-06 09:33	SMS Delivery Delays and Delivery Receipt Delays from Twilio to Chunghwa Telecom Taiwan	minor	5 h 29 min
2026-10-06 08:21	SMS Delivery Delays from Twilio to Rain South Africa and Orange Niger	minor	2 h 31 min
2026-10-06 06:28	MMS Delivery Failures from a Subset of Twilio Short Codes to Verizon and T-Mobile United States	minor	3 h 21 min
2026-10-06 02:04	SMS Delivery Failures from Twilio to Orange Guinea	minor	3 h 3 min

Tell your outage from Twilio's

Declare that your project depends on Twilio. When one of your monitors fails while Twilio has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - twilio

Ask before you retry

curl -s https://upbutler.com/status/twilio/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "twilio",
  "verdict": "proceed",
  "status": "degraded",
  "reason": "SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in New Zealand",
  "retryAfterSec": null,
  "incident": {
    "title": "SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in New Zealand",
    "url": "https://status.twilio.com/incidents/0mtly7m1pnq6"
  },
  "probe": {
    "state": "up",
    "statusCode": 401
  }
}

Questions

Is Twilio down right now?: Partly. As of 2026-10-10 05:12 UTC, Twilio is degraded, with an open incident: "SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in New Zealand". This page reads the status again every 2 minutes.
Where does this status come from?: From Twilio's own status page API at https://status.twilio.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Twilio's words.
What does UpButler's own Twilio check prove?: Every two minutes UpButler sends one request without credentials to the Twilio API edge (api.twilio.com). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Twilio reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
How can my agent or app check Twilio status?: Fetch https://upbutler.com/status/twilio/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"twilio"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Twilio's?: Add "twilio" to the dependencies of your UpButler workspace. When one of your monitors fails while Twilio has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in messaging and realtime

UpButler is not affiliated with Twilio. Status and incident text belong to Twilio and are read from their public status source; the probe result is UpButler's own measurement.