- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Number Porting
- Down Index
- 29of 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 2h 7m it lasted.
Anything that failed between 2026-06-17 15:27 UTC and 2026-06-17 17:34 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
- identified
Bandwidth teams have identified an incident impacting both Port In and Port Out Orders. These orders are delayed in completing, due to an industry provider incident.
provider
- monitoring
Teams are observing expected port order behavior and will monitor for stability.
provider
- 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-4fbaa9fe05
Is Bandwidth still down?
No, this incident was resolved 2026-06-17 17:34 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
2h 7m, from 2026-06-17 15:27 UTC to 2026-06-17 17:34 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.