Skip to main content
Bandwidth

Toll Free Porting Incident

Degraded Lasted 3h 41m · started · Bandwidth's page

Level
confirmed
Worst impact
Degraded
Components
Number Porting
Down Index
20of 100

What to do

  • Check whether you use Bandwidth Number Porting. 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 3h 41m it lasted.

    Anything that failed between 2026-09-21 14:15 UTC and 2026-09-21 17:56 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 2

  1. identified

    Bandwidth teams have identified select Toll Free Port Orders that remain in Pending status longer than expected. Teams are working to restore expected order activations.

    provider

  2. 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-48338d89c2

Is Bandwidth still down?

No, this incident was resolved 2026-09-21 17:56 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.

How long did it last?

3h 41m, from 2026-09-21 14:15 UTC to 2026-09-21 17:56 UTC, by the times Bandwidth posted.

What was affected?

Bandwidth named Number Porting.

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.