Skip to main content
Bandwidth

10DLC Provisioning Incident - Delays

Degraded Lasted 1h 26m · started · Bandwidth's page

Level
confirmed
Worst impact
Degraded
Components
Line Feature Management
Down Index
18of 100

What to do

  • Check whether you use Bandwidth Line Feature Management. 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 1h 26m it lasted.

    Anything that failed between 2026-03-03 03:02 UTC and 2026-03-03 04:28 UTC may need a replay.
  • Subscribe to Bandwidth's feed to hear about the next one first. RSS feed

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

Updates from Bandwidth 3

  1. investigating

    Teams are investigating a delay in 10DLC provisioning orders.

    provider

  2. monitoring

    Teams are observing expected processing times. And will continue to monitor for prolonged stability.

    provider

  3. resolved

    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-5de16c5477

Is Bandwidth still down?

No, this incident was resolved 2026-03-03 04:28 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.

How long did it last?

1h 26m, from 2026-03-03 03:02 UTC to 2026-03-03 04:28 UTC, by the times Bandwidth posted.

What was affected?

Bandwidth named Line Feature Management.

What caused it?

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

Where does this come from?

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