rewindex

CompaniesTwilioIncidents

Twilio: Issue with 500 errors for certain parts of our APIs

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.twilio.com (opens in new tab)

Timeline of updates

  1. resolved

    For a brief period we saw that: - Voice users may not have seen debugger alerts for failed calls - Video customers may not see call logs - Console users would not see “pinned products” on sidebar, but could still go to individual product pages through the menus But we have now recovered and should be operating as normal.

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 2020-11-06 12:06 UTC, resolved after 0 min, 1 update(s).

Title
Issue with 500 errors for certain parts of our APIs
Vendor
Twilio
Date
URL
https://rewindex.com/company/twilio/incidents/dgbb0lcjhn1w

Twilio profileRecent Twilio incidentsAll outages on November 6, 2020Twilio in November 2020MarkdownJSON