Twilio: Twilio Flex / TaskRouter Voice Orchestrator Affected
Timeline of updates
- resolved
Twilio Flex / TaskRouter Voice Orchestrator was degraded for 2 minutes between 14:01 and 14:03 Pacific Time on 04/03/2024. During this period of time High latency in Voice Orchestrator caused 5xxs in downstreams resulting in some impact to inbound and outbound meetings Customer Impact: Some inbound and outbound meetings would have failed, more impact to be provided after assessment. Likely 35 meetings impacted. The issue has now been resolved.Twilio Flex / Task Router Voice Orchestrator was degraded for 2 minutes between 14:01 and 14:03 Pacific Time on 04/03/2024. During this period of time High latency in Voice Orchestrator caused 5xxs in downstreams resulting in some impact to inbound and outbound meetings Customer Impact: Some inbound and outbound meetings would have failed, more impact to be provided after assessment. Likely less than 100 meetings impacted. The issue has now been 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: none) posted by Twilio, started 2024-04-03 21:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Twilio Flex / TaskRouter Voice Orchestrator Affected
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/frlcrplfxbpm
Twilio profileRecent Twilio incidentsAll outages on April 3, 2024Twilio in April 2024MarkdownJSON