Twilio: Programmable Messaging - Service Interruption With Programmable Messaging for a Percentage of Messaging Services
Timeline of updates
- resolved
We are no longer seeing service interruption with Programmable Messaging for a percentage of Messaging Services where messages sent with Messaging Services failed to honor {force-opt-in}. This incident is Resolved.
From Twilio’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2026-04-27 04:28 UTC, resolved after 31 min, 1 update(s).
- Title
- Programmable Messaging - Service Interruption With Programmable Messaging for a Percentage of Messaging Services
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/45y7qj466xmd
Twilio profileRecent Twilio incidentsAll outages on April 27, 2026Twilio in April 2026MarkdownJSON