Minor impactResolvedCommunication

Twilio incident: SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Beeline Kazakhstan

Twilio reported this minor-impact incident on its official status page on Oct 13, 2026, 16:14 UTC. It was resolved after 7 min.

Right now Twilio is operational. Live Twilio status →

🔔 Get alerted when Twilio has issuesFree · email alerts · no credit card
Oct 13, 2026, 16:14 UTC
started
Oct 13, 2026, 16:21 UTC
resolved
7 min
duration
Minor
impact

Affected components

  • SMS, APAC
  1. resolvedOct 13, 2026, 16:21 UTC

    The incident has been resolved and SMS delivery from Twilio to Beeline network subscribers in Kazakhstan is operating normally.

  2. investigatingOct 13, 2026, 16:14 UTC

    Twilio customers may be experiencing SMS delivery delays and failures from a subset of Twilio Alphanumeric Sender IDs to Beeline network subscribers in Kazakhstan. 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

Our 5-minute checks didn't record a change in Twilio's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Twilio have incidents?

Twilio reported 496 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 5h 54m. See Twilio's uptime and incident history