rewindex

CompaniesTwilioIncidents

Twilio: MMS Delivery Delays from a Subset of Twilio Long Codes to C-Spire United States

MinorStatus: identifiededitedStarted Not resolved5 updatesstatus.twilio.com (opens in new tab)

Affected components: CARRIER NETWORK - MMS Long Code, North AmericaMMS Long Code, North AmericaMMS Long Code, North AmericaZIPWHIP MESSAGING - MMS Long Code, North America

Timeline of updates

  1. investigating

    Twilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to C-Spire network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified

    Twilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to C-Spire network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  3. identified

    Twilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to C-Spire network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.

  4. identified

    Twilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to C-Spire network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.

  5. identified

    Twilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to C-Spire network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 8 hours or as soon as more information becomes available.

Changes Rewindex caught on this incident

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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured a newer version after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).

Twilio profileRecent Twilio incidentsMarkdownJSON