Skip to content
Twilio · Apps and SaaSSep 22, 2026, 18:20 UTC

Phone Number APIs and Console Were Returning Incorrect 404 Responses

InformationalConfig changeUpdated 38h ago
Sep 22, 18:20 UTCSep 22, 18:20 UTC
Duration
0m
Impact
Informational
Root cause
Config change
Twilio, 90 days
554 incidents
Affected
Not listed by the vendor.
Status page

Final update

Due to an incorrect configuration, customers experienced a burst of invalid 404 Not Found response when communicating with Phone Number APIs: AvailablePhoneNumbers and IncomingPhoneNumbers. They might have also experienced degraded console behavior relating to Phone Number operations.

Timeline

  1. Resolved · Sep 22, 18:20 UTC
    Due to an incorrect configuration, customers experienced a burst of invalid 404 Not Found response when communicating with Phone Number APIs: AvailablePhoneNumbers and IncomingPhoneNumbers. They might have also experienced degraded console behavior relating to Phone Number operations.

More from Twilio

Full history

Also caused by configuration change

All
StartedIncidentDuration
Sep 2423:36 UTCKey Value service restartsRender0m
Sep 2414:08 UTCThe Salesforce integration is unavailable for some customersHubSpot7h 18m
Sep 1622:30 UTCHyperdrive Elevated Origin Connection Failure RatesCloudflare0m
Sep 1211:04 UTCSome customers experiencing blurry image previews and download issuesSlack8h 56m
Sep 1107:18 UTCINC20000213Snowflake6h 1m
Sep 407:34 UTCINC20000199Snowflake2h 36m

Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Outages by email

Saturday mornings: the week's major outages, new postmortems and disclosed breaches, only in weeks that had some.

Double opt-in. Unsubscribe any time.