Phone Number APIs and Console Were Returning Incorrect 404 Responses
Sep 22, 18:20 UTCSep 22, 18:20 UTC
Duration
0m
Impact
Informational
Root cause
Config change
Twilio, 90 days
548 incidents
Affected
Not listed by the vendor.
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
- 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 historySMS Delivery Receipt Delays from Twilio to Bouygues Telecom Francestill openSMS Delivery Failures from Germany to a Subset of Twilio Long Codesstill openSMS Delivery Failures from Twilio to ETL Laosstill openSMS Delivery Failures from Twilio to MTN Nigerialasted 6h 1mSilent Network Authentication (SNA) Failure Increase and Gateway API (Lookup API) Failure Increase on EnStream in Canadalasted 14h 13mSMS Delivery Receipt Delays from Twilio to Globe Philippineslasted 13h 17m