rewindex

ChangesTwilioSubset of API Requests Blocked with 403 Response

Twilio: Incident updated: Subset of API Requests Blocked with 403 Response

Incident updateNot classified yetChanged status.twilio.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Twilio removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: monitoring
AddedUpdatemonitoring#2
Before: not present
After: We are observing a recovery in API requests blocked with 403 response. We will continue to monitor to ensure full service recovery. We expect to provide another update in 30 minutes or as soon as more information becomes available.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

TodayFriday, November 20Fri, Nov 20

1 rewrite, 2 incident changes

Cite this

Incident updated: Subset of API Requests Blocked with 403 Response on Twilio’s status page, changed 2026-11-20 17:43 UTC (change 2 of 3).

Title
Incident updated: Subset of API Requests Blocked with 403 Response
Vendor
Twilio
Date
URL
https://rewindex.com/change/ref7560cbcc8c6d

All Twilio changesTwilio profileMarkdownJSON