Minor impactResolvedCommunication

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

SendGrid reported this minor-impact incident on its official status page on Oct 27, 2026, 21:31 UTC. It was resolved after 8d 1h.

Right now SendGrid is operational. Live SendGrid status →

🔔 Get alerted when SendGrid has issuesFree · email alerts · no credit card
Oct 27, 2026, 21:31 UTC
started
Nov 4, 2026, 22:57 UTC
resolved
8d 1h
duration
Minor
impact

Affected components

  • MMS Long Code, North America
  1. resolvedNov 4, 2026, 22:57 UTC

    The incident has been resolved and MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States is operating normally.

  2. monitoringNov 4, 2026, 04:52 UTC

    We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States and are monitoring service stability. We will provide another update in 24 hours or as soon as more information becomes available.

  3. monitoringNov 3, 2026, 04:51 UTC

    We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States and are monitoring service stability. We will provide another update in 24 hours or as soon as more information becomes available.

  4. monitoringNov 2, 2026, 04:45 UTC

    We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States and are monitoring service stability. We will provide another update in 24 hours or as soon as more information becomes available.

  5. monitoringNov 1, 2026, 04:44 UTC

    We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States and are monitoring service stability. We will provide another update in 24 hours or as soon as more information becomes available.

  6. monitoringOct 31, 2026, 04:39 UTC

    We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States and are monitoring service stability. We will provide another update in 24 hours or as soon as more information becomes available.

  7. monitoringOct 30, 2026, 12:38 UTC

    We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States and are monitoring service stability. We will provide another update in 16 hours or as soon as more information becomes available.

  8. monitoringOct 30, 2026, 04:37 UTC

    We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States and are monitoring service stability. We will provide another update in 8 hours or as soon as more information becomes available.

  9. monitoringOct 30, 2026, 00:37 UTC

    We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

  10. monitoringOct 29, 2026, 22:36 UTC

    We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  11. identifiedOct 29, 2026, 05:01 UTC

    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 24 hours or as soon as more information becomes available.

  12. identifiedOct 28, 2026, 13:01 UTC

    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 16 hours or as soon as more information becomes available.

  13. identifiedOct 28, 2026, 04:49 UTC

    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.

  14. identifiedOct 28, 2026, 00:48 UTC

    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.

  15. identifiedOct 27, 2026, 22:48 UTC

    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.

  16. identifiedOct 27, 2026, 21:47 UTC

    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.

  17. investigatingOct 27, 2026, 21:31 UTC

    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.

What APIStatus.watch saw

  • Oct 28, 2026, 11:20 UTCoperational → unknown
  • Oct 28, 2026, 11:25 UTCunknown → operational
  • Oct 28, 2026, 13:45 UTCoperational → unknown
  • Oct 28, 2026, 13:50 UTCunknown → operational
  • Oct 28, 2026, 18:10 UTCoperational → unknown
  • Oct 28, 2026, 18:15 UTCunknown → operational
  • Oct 28, 2026, 20:50 UTCoperational → unknown
  • Oct 28, 2026, 20:55 UTCunknown → operational
  • Oct 29, 2026, 01:35 UTCoperational → unknown
  • Oct 29, 2026, 01:49 UTCunknown → operational
  • Oct 29, 2026, 02:15 UTCoperational → unknown
  • Oct 29, 2026, 02:20 UTCunknown → operational
  • Oct 29, 2026, 02:30 UTCoperational → unknown
  • Oct 29, 2026, 02:40 UTCunknown → operational
  • Oct 29, 2026, 02:45 UTCoperational → unknown
  • Oct 29, 2026, 02:55 UTCunknown → operational
  • Oct 29, 2026, 03:00 UTCoperational → unknown
  • Oct 29, 2026, 03:10 UTCunknown → operational
  • Oct 29, 2026, 03:20 UTCoperational → unknown
  • Oct 29, 2026, 03:44 UTCunknown → operational
  • Oct 29, 2026, 07:35 UTCoperational → unknown
  • Oct 29, 2026, 07:40 UTCunknown → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does SendGrid have incidents?

SendGrid reported 506 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 6h 11m. See SendGrid's uptime and incident history