Off-Net Port Activations

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 6h 51m it lasted.

  Anything that failed between 2026-10-22 14:57 UTC and 2026-10-22 21:48 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.

Root cause

Bandwidth teams have identified that due to a vendor condition some off net port orders are not activating as expected.

Category: Upstream dependency

Updates from Bandwidth 4

1. identifiedOct 22, 2026, 2:57 PM UTC

   Bandwidth teams have identified that due to a vendor condition some off net port orders are not activating as expected.

   provider

2. monitoringOct 22, 2026, 4:18 PM UTC

   Teams are observing expected port activation times and will monitor for stability.

   provider

3. resolvedOct 22, 2026, 9:48 PM UTC

   This incident has been resolved.

   provider

4. postmortemOct 23, 2026, 9:34 AM UTC

   Between 12:40 UTC and 21:27 UTC on October 22, 2026, some off net port orders were not activating as expected due to a vendor condition. Bandwidth is continuing to investigate this issue to identify all actions necessary to prevent this from recurring and will update this post with an Incident Report after investigations have concluded. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

   provider

Corrections

None so far.

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