Skip to main content

Twilio outage on October 18, 2026: SMS Delivery Delays from a Subset of Twilio Short Codes to Brisanet Brazil

Twilio reported an incident affecting Twilio for 1 day 21 hours on 18 October 2026, from 22:41 to 20:14 UTC.

www.twilio.com All times UTC

Resolved

Official incident reported by Twilio

Started
22:41
18 Oct 2026 UTC
Resolved
20:14
20 Oct 2026 UTC
Duration
1d 21h
1 day 21 hours
Impact
Minor
as rated by Twilio
Updates
14
posted by Twilio

Timeline

All times UTC.

Official incident from Twilio

SMS Delivery Delays from a Subset of Twilio Short Codes to Brisanet Brazil

Resolved Minor impact 18 Oct 2026 22:41 UTC View on Twilio's status page
  1. Official
    Investigating

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. Official
    Investigating

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available.

  3. Official
    Investigating

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil. Our team is actively investigating this issue. We will provide another update in 4 hours or as soon as more information becomes available.

  4. Official
    Monitoring

    We have observed a recovery in SMS delivery from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  5. Official
    Monitoring

    We have observed a recovery in SMS delivery from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

  6. Official
    Monitoring

    We have observed a recovery in SMS delivery from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil and are monitoring service stability. We will provide another update in 8 hours or as soon as more information becomes available.

  7. Official
    Identified

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil. 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.

  8. Official
    Identified

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil. 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.

  9. Official
    Identified

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil. 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.

  10. Official
    Identified

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil. 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.

  11. Official
    Identified

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil. 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.

  12. Official
    Monitoring

    We have observed a recovery in SMS delivery from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  13. Official
    Monitoring

    We have observed a recovery in SMS delivery from a subset of Twilio Short Codes to Brisanet network subscribers in Brazil and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

  14. Official
    Resolved

    We have completed our investigation. This event did not cause performance degradation beyond the expected behavior for this Brazilian carrier, which may retry delivery attempts for up to 24 hours before setting a final status. All systems are operating normally.

"Official" rows are quoted from Twilio's public status page, status.twilio.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test www.twilio.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Twilio status shows what our checks see right now.

Does your product depend on Twilio?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Independent measurement by HostTracker. Not affiliated with Twilio. Official updates are quoted from Twilio's public status page and remain Twilio's own words.