Twilio: vendor-reported minor incident on September 25 (tracked 3d 0h)
Sep 25, 01:01 AM → Sep 28, 01:05 AM · 3d 0h · medium
Twilio reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 3d 0h, from Fri, 25 Sep 2026 01:01:02 GMT to Mon, 28 Sep 2026 01:05:32 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.
Impact
PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.
Incident timeline
- Sep 25, 01:01 AM
The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it
- Sep 27, 02:05 PM
Status updated: major issue
- Sep 27, 02:40 PM
Status updated: possible issue
- Sep 27, 02:50 PM
Status updated: major issue
- Sep 27, 04:10 PM
Status updated: possible issue
- Sep 27, 04:20 PM
Status updated: major issue
- Sep 27, 05:05 PM
Status updated: possible issue
- Sep 27, 05:20 PM
Status updated: major issue
- Sep 27, 05:40 PM
Status updated: possible issue
- Sep 27, 05:50 PM
Status updated: major issue
- Sep 27, 06:40 PM
Status updated: possible issue
- Sep 27, 06:50 PM
Status updated: major issue
- Sep 27, 06:55 PM
Status updated: possible issue
- Sep 27, 07:05 PM
Status updated: major issue
- Sep 27, 07:10 PM
Status updated: possible issue
- Sep 27, 07:20 PM
Status updated: major issue
- Sep 28, 01:05 AM
PulseWatch closed the incident
Official updates
- Sep 25, 01:01 AM
Twilio reported the incident on its status page.
View official source