Twilio: On Call Engineers are Investigating 500 Errors from Studio's Fetch Step Context and Fetch Execution
Timeline of updates
- resolved
We have fully investigated the 500 errors from Studio's fetch step context and fetch execution issue triggered by our automated alert. It was determined that the errors are currently related to the service outage in our US East data center.
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 2021-12-07 22:03 UTC, resolved after 24 min, 1 update(s).
- Title
- On Call Engineers are Investigating 500 Errors from Studio's Fetch Step Context and Fetch Execution
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/jdjnkxzc33hg
Twilio profileRecent Twilio incidentsAll outages on December 7, 2021Twilio in December 2021MarkdownJSON