Twilio: RateQueue Host Down Did Not Recover
Affected components: PROGRAMMABLE MESSAGING - SMSSMS
Timeline of updates
- investigating
We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available
- identified
Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available
- identified
Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available
- identified
Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available.
- identified
Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available.
- identified
The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 8 hours or as soon as new information is available.
- identified
The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 16 hours or as soon as new information is available.
- monitoring
Messaging is operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.
Changes Rewindex caught on this incident
- Incident updated: RateQueue Host Down Did Not Recover
- Incident updated: RateQueue Host Down Did Not Recover
- Incident updated: RateQueue Host Down Did Not Recover
- Incident updated: RateQueue Host Down Did Not Recover
- Incident updated: RateQueue Host Down Did Not Recover
- Incident updated: RateQueue Host Down Did Not Recover
- Incident updated: RateQueue Host Down Did Not Recover
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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-03 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a044ed01fae282a8…Version 2 captured
In the 2026-11-03 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
deaad47d40e74b16…Version 3 captured
In the 2026-11-03 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
5dfaf026251493c4…Version 4 captured
In the 2026-11-03 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
fc6e51a2072b82a7…Version 5 captured
In the 2026-11-03 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
41dfb229a533c7ad…Version 6 captured
In the 2026-11-03 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
831f7cb714f42cfa…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
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-11-03 02:14 UTC, not resolved, 8 update(s); edited after publishing.
- Title
- RateQueue Host Down Did Not Recover
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/x3f55q1rkbqv
Twilio profileRecent Twilio incidentsAll outages on November 3, 2026Twilio in November 2026MarkdownJSON