Skip to main content
Twilio

Delayed Account Reactivations

Degraded Lasted 13h 20m · started · Twilio's page

Level
confirmed
Worst impact
Degraded
Components
Billing
Down Index
23of 100

What to do

  • Check whether you use Twilio Billing. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 13h 20m it lasted.

    Anything that failed between 2026-03-25 22:17 UTC and 2026-03-26 11:37 UTC may need a replay.
  • Subscribe to Twilio's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Twilio 11

  1. investigating

    Twilio users who have a positive account balance are not being automatically reactivated and are reporting to Support.

    provider

  2. investigating

    We are investigating reports of customer accounts not automatically reactivating after a successful payment. We will provide another update in 1 hour or as soon as more information is available.

    provider

  3. investigating

    We continue investigating reports of customer accounts not automatically reactivating after a successful payment. We will provide another update in 2 hours or as soon as more information is available.

    provider

  4. investigating

    We continue investigating reports of customer accounts not automatically reactivating after a successful payment. We will provide another update in 4 hours or as soon as more information is available.

    provider

  5. identified

    The issue causing the customer accounts to not automatically reactivate after a successful payment has been identified. We are actively working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.

    provider

  6. identified

    The issue causing the customer accounts to not automatically reactivate after a successful payment has been identified. We are actively working to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.

    provider

  7. identified

    The issue causing the customer accounts to not automatically reactivate after a successful payment has been identified. We are actively working to resolve the issue. We expect to provide another update in 4 hours or as soon as more information becomes available.

    provider

  8. identified

    The issue causing the customer accounts to not automatically reactivate after a successful payment has been identified. We are actively working to resolve the issue. We expect to provide another update in 8 hours or as soon as more information becomes available.

    provider

  9. monitoring

    We have observed a recovery in the issue where customer accounts were not automatically reactivating after a successful payment. We are now monitoring service stability to ensure a full recovery. We will provide another update in 30 minutes or as soon as more information becomes available.

    provider

  10. monitoring

    We have observed a recovery in the issue where customer accounts were not automatically reactivating after a successful payment. We are now monitoring service stability to ensure a full recovery. We will provide another update in 30 minutes or as soon as more information becomes available.

    provider

  11. resolved

    We are no longer experiencing issues with Automatic Account Reactivations following successful payments. This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-9381272f69

Is Twilio still down?

No, this incident was resolved 2026-03-26 11:37 UTC. For Twilio's live state, see https://down.guide/twilio.

How long did it last?

13h 20m, from 2026-03-25 22:17 UTC to 2026-03-26 11:37 UTC, by the times Twilio posted.

What was affected?

Twilio named Billing.

What caused it?

Twilio hasn't published a root cause. If it does, it shows here.

Where does this come from?

Twilio's official status page, https://status.twilio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.