Number Portability Checker Incident

What to do

• Check whether you use Bandwidth Number Porting in us. 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 33m it lasted.

  Anything that failed between 2026-10-29 15:09 UTC and 2026-10-29 17:42 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

Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue.

Updates from Bandwidth 3

1. investigatingOct 29, 2026, 3:09 PM UTC

   Bandwidth teams are investigating the Number Portability Checker for both UI and API requests. These requests may return unexpected results or fail to complete.

   provider

2. resolvedOct 29, 2026, 5:42 PM UTC

   This incident has been resolved.

   provider

3. postmortemOct 30, 2026, 9:15 AM UTC

   Bandwidth has concluded its investigation of this issue and determined that between 16:59 UTC on October 28 and 17:19 UTC on October 29, requests to the Number Portability Checker API that asked for a JSON response returned an empty response instead of the portability information. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. 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.