rewindex

CompaniesTwilioIncidents

Twilio: Delay in fetching new calls.

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

Timeline of updates

  1. resolved

    Between 9:00 AM and 10:04 AM Pacific Time, the REST API may have returned 404 responses or taken longer than usual to respond to GET requests for Call instance resources. This only impacted calls created after 9:00 AM Pacific Time, and only impacted a subset of customer accounts. The incident is now 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 2017-09-06 17:31 UTC, resolved after 31 min, 1 update(s).

Title
Delay in fetching new calls.
Vendor
Twilio
Date
URL
https://rewindex.com/company/twilio/incidents/ls79kx27d1wc

Twilio profileRecent Twilio incidentsAll outages on September 6, 2017Twilio in September 2017MarkdownJSON