rewindex

CompaniesTwilioIncidents

Twilio: Unable to Sign New Numbers for Stir/Shaken

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

Timeline of updates

  1. resolved

    From 14:11 PM to 14:24 PM PST we experienced a brief outage when attempting to attest numbers for the STIR/SHAKEN protocol; numbers were displayed without attestation. This error has 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 2020-10-26 09:00 UTC, resolved after 0 min, 1 update(s).

Title
Unable to Sign New Numbers for Stir/Shaken
Vendor
Twilio
Date
URL
https://rewindex.com/company/twilio/incidents/y4y5k8dvdmct

Twilio profileRecent Twilio incidentsAll outages on October 26, 2020Twilio in October 2020MarkdownJSON