Automated Alert: No Customer Impact
Jul 14, 09:44 UTCJul 14, 10:23 UTC
Duration
39m
Impact
Informational
Root cause
Not disclosed
Twilio, 90 days
554 incidents
Affected
Not listed by the vendor.
Final update
We have fully investigated the issue when attempting to add newly purchased phone numbers to their SIP Trunks triggered by our automated alert, and it was determined that there is no noticeable customer impact. All systems are operational.
Timeline
- Resolved · Jul 14, 10:23 UTC
We have fully investigated the issue when attempting to add newly purchased phone numbers to their SIP Trunks triggered by our automated alert, and it was determined that there is no noticeable customer impact. All systems are operational.
More from Twilio
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2503:49 UTC | SMS Delivery Delays from Twilio to Claro Brazil | minor | Ongoing |
| Sep 2502:24 UTC | SMS Delivery Delays from a Subset of Twilio Short Codes to Cellularone NE Arizona United States | minor | Ongoing |
| Sep 2420:40 UTC | Event Streams Service Disruption | minor | 5h 44m |
| Sep 2417:55 UTC | SMS Delivery Receipt Delays from a Subset of Twilio Alphanumeric Sender IDs to Ooredoo Algeria | minor | Ongoing |
| Sep 2417:19 UTC | Some Transfer Calls in Elastic SIP Trunking Failing With Error Code 32204 | minor | 43m |
| Sep 2416:22 UTC | Link Branding Creation Fails with HTTP 500 Internal Server Error (Auto SSL Enabled) | minor | 2h 4m |
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.