Twilio: Increased read REST API 404s
Timeline of updates
- resolved
We experienced an incident earlier this morning that affected our API. GET API calls reading from the Calls resource were affected. Customers may have experienced increased 404s accessing valid Call resources. The incident began at 6:53 am and ended at 8:19 am.
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 2017-08-03 16:47 UTC, resolved after 0 min, 1 update(s).
- Title
- Increased read REST API 404s
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/4c601j2ypx8v
Twilio profileRecent Twilio incidentsAll outages on August 3, 2017Twilio in August 2017MarkdownJSON