Skip to main content
down.guideby Sazabi
Providers
Is Bandwidth down? · Messaging and comms

Bandwidth is degraded

DegradedSince : Toll-Free Port Activation Delays

99.99% uptime, 90 days · 99.99% over 12 monthsLast incident Checked Official status pageHistory

Reports count in aggregate against normal levels; one alone never makes a claim.

Now

Open incidents

What Bandwidth has posted and not resolved.

  1. BandwidthDegradedOngoing
    Toll-Free Port Activation Delays

    Bandwidth says toll-free port orders are delayed in activation due to an off-network industry provider's network condition. Bandwidth teams are working with the impacted provider to restore expected port activation times. The incident is currently investigating.

    ongoing for 11h 4mNumber Porting
Minor

Minor or regional issues (1)

Open issues confined to one country, region, site, carrier route, asset or slice of customers. Bandwidth's state, uptime and the Down Index leave them out.

  1. BandwidthMajor outageMonitoring
    Bandwidth Local Market Impairment - 536 - Oklahoma City, OK

    Bandwidth says an impairment on its network in Oklahoma City, OK may affect a portion of calls. The provider says the issue has been identified, a fix has been implemented, and it is now monitoring the results.

    monitoring a fix, open 7h 57m536 - Oklahoma City, OK
90 days

Daily history

Worst impact each day, from the provider's own incidents.

  1. 2026-08-14: 3 incidents, worst degraded
  2. 2026-08-15: no incidents
  3. 2026-08-16: 1 incident, worst degraded
  4. 2026-08-17: 2 incidents, worst partial outage
  5. 2026-08-18: 1 incident, worst degraded
  6. 2026-08-19: 1 incident, worst degraded
  7. 2026-08-20: 2 incidents, worst partial outage
  8. 2026-08-21: no incidents
  9. 2026-08-22: no incidents
  10. 2026-08-23: no incidents
  11. 2026-08-24: 1 incident, worst degraded
  12. 2026-08-25: 1 incident, worst major outage
  13. 2026-08-26: 1 incident, worst degraded
  14. 2026-08-27: no incidents
  15. 2026-08-28: 1 incident, worst degraded
  16. 2026-08-29: no incidents
  17. 2026-08-30: no incidents
  18. 2026-08-31: 1 incident, worst degraded
  19. 2026-09-01: 2 incidents, worst major outage
  20. 2026-09-02: 2 incidents, worst degraded
  21. 2026-09-03: 1 incident, worst degraded
  22. 2026-09-04: 1 incident, worst degraded
  23. 2026-09-05: no incidents
  24. 2026-09-06: no incidents
  25. 2026-09-07: no incidents
  26. 2026-09-08: 1 incident, worst major outage
  27. 2026-09-09: no incidents
  28. 2026-09-10: no incidents
  29. 2026-09-11: 1 incident, worst degraded
  30. 2026-09-12: no incidents
  31. 2026-09-13: no incidents
  32. 2026-09-14: 2 incidents, worst degraded
  33. 2026-09-15: 2 incidents, worst degraded
  34. 2026-09-16: no incidents
  35. 2026-09-17: no incidents
  36. 2026-09-18: 1 incident, worst degraded
  37. 2026-09-19: no incidents
  38. 2026-09-20: no incidents
  39. 2026-09-21: 1 incident, worst degraded
  40. 2026-09-22: no incidents
  41. 2026-09-23: 1 incident, worst degraded
  42. 2026-09-24: no incidents
  43. 2026-09-25: 2 incidents, worst degraded
  44. 2026-09-26: no incidents
  45. 2026-09-27: no incidents
  46. 2026-09-28: no incidents
  47. 2026-09-29: no incidents
  48. 2026-09-30: no incidents
  49. 2026-10-01: 1 incident, worst degraded
  50. 2026-10-02: 2 incidents, worst partial outage
  51. 2026-10-03: no incidents
  52. 2026-10-04: no incidents
  53. 2026-10-05: no incidents
  54. 2026-10-06: 2 incidents, worst partial outage
  55. 2026-10-07: 5 incidents, worst degraded
  56. 2026-10-08: 2 incidents, worst degraded
  57. 2026-10-09: no incidents
  58. 2026-10-10: no incidents
  59. 2026-10-11: no incidents
  60. 2026-10-12: no incidents
  61. 2026-10-13: no incidents
  62. 2026-10-14: 1 incident, worst degraded
  63. 2026-10-15: no incidents
  64. 2026-10-16: 1 incident, worst degraded
  65. 2026-10-17: 1 incident, worst degraded
  66. 2026-10-18: 1 incident, worst degraded
  67. 2026-10-19: 1 incident, worst degraded
  68. 2026-10-20: 1 incident, worst partial outage
  69. 2026-10-21: 1 incident, worst degraded
  70. 2026-10-22: 3 incidents, worst partial outage
  71. 2026-10-23: 1 incident, worst degraded
  72. 2026-10-24: no incidents
  73. 2026-10-25: no incidents
  74. 2026-10-26: 1 incident, worst degraded
  75. 2026-10-27: no incidents
  76. 2026-10-28: no incidents
  77. 2026-10-29: 1 incident, worst partial outage
  78. 2026-10-30: no incidents
  79. 2026-10-31: no incidents
  80. 2026-11-01: no incidents
  81. 2026-11-02: 1 incident, worst degraded
  82. 2026-11-03: 2 incidents, worst partial outage
  83. 2026-11-04: 1 incident, worst partial outage
  84. 2026-11-05: no incidents
  85. 2026-11-06: no incidents
  86. 2026-11-07: no incidents
  87. 2026-11-08: no incidents
  88. 2026-11-09: no incidents
  89. 2026-11-10: 1 incident, worst degraded
  90. 2026-11-11: 1 incident, worst degraded
90 days agoToday

Daily history for the 12 components with the most incident days. Every component's current state is in the Markdown copy.

Reliability

Last 90 days in numbers

From the provider's own posts, including history read from its archive.

Uptime
99.99%12 months
Incidents
186on 44 days
Median duration
4h 51m
Longest
4d 18h
Postmortem rate
0%partial and major outages
Reports

People reporting problems

Hourly counts, last 24 hours.

No reports in the last 24 hours.

Follow Bandwidth incidents

Following several providers? Check your stack to get one feed for all of them.

https://down.guide/feed?provider=bandwidth
Open feed

In Slack, install the RSS app and run /feed subscribe https://down.guide/feed?provider=bandwidth in a channel. In Discord, add a feed bot such as MonitoRSS and give it this URL. Or paste it into Feedly or any RSS reader.

https://down.guide/feed?provider=bandwidth&format=atom
Open feed

The same entries as Atom, for readers that prefer it.

https://down.guide/feed?provider=bandwidth&format=json
Open feed

The same entries as JSON Feed 1.1, each with the full incident under _down_guide, for scripts.

https://down.guide/api/v1/incidents?provider=bandwidth
Open feed

Pages of 30 incidents, newest first. Pass the response's next_cursor as cursor for the next page.

History

Recent incidents

The last 90 days.

All history
  1. BandwidthOperational
    Bandwidth Local Market Impairment - 532 - Wichita, KS
    lasted 2h 50m532 - Wichita, KS
  2. BandwidthMaintenance
    Messaging Maintenance - Toll-Free MMS/SMS

    Bandwidth says its downstream vendor's maintenance is in progress and may cause brief periods of latency for inbound and outbound Toll-Free MMS/SMS messaging. The provider will post updates as necessary.

    lasted 5h 1mToll-Free SMS - Inbound, Toll-Free SMS - Outbound, Toll Free MMS - Inbound +1
  3. BandwidthMaintenance
    Messaging Maintenance - MMS/SMS

    Bandwidth says its downstream vendor is performing maintenance that may affect its MMS/SMS messaging platform. Customers may see delays in inbound and outbound MMS/SMS delivery. The provider says the maintenance is currently in progress and it will post updates as necessary.

    lasted 8h 1mSMS Messaging (SMPP), MMS Messaging (MM4), REST APIs - HTTP SMS Messaging +1
  4. BandwidthOperational
    Bandwidth Local Market Impairment - Grand Island, NE
    lasted 4h 33m646 - Grand Island, NE
  5. BandwidthMajor outage
    Bandwidth Local Market Impairment - 256 Clarksburg WV

    Bandwidth says an impairment on its network affected a portion of calls in the Clarksburg, WV local market (256). The provider says its carrier completed all necessary repairs and all services are restored. The incident is resolved.

    lasted 2h 16m256 - Clarksburg, WV
  6. BandwidthOperational
    Bandwidth Local Market Impairment - 248 - Richmond, VA
    lasted 5h 42m248 - Richmond, VA
  7. BandwidthPartial outage
    Voice Authentication Incident - Pindrop
    lasted 5h 8mInbound Calling (SIP) - United Statesus
  8. BandwidthPartial outage
    Outbound 10DLC MMS Delivery Incident - T-Mobile, Verizon, AT&T
    lasted 11h 40mMMS Messaging (MM4)
  9. BandwidthOperational
    Bandwidth Local Market Impairment - 246 - Culpeper, VA
    lasted 4h 55m246 - Culpeper, VA
  10. BandwidthDegraded
    Brussels (BRU) data center incident
    lasted 0m
  11. BandwidthDegraded
    Outbound 10DLC MMS Delivery Incident
    lasted 16h 29mMMS Messaging (MM4)
  12. BandwidthPartial outage
    Non-North American Emergency Address Validation Incident
    lasted 7h 54mBandwidth App, Bandwidth International (fka Voxbone) Portal
  13. BandwidthOperational
    Bandwidth Local Market Impairment - 130 - Providence, RI
    lasted 5h 29m130 - Providence, RI
  14. BandwidthOperational
    Outbound 10DLC MMS Delivery Delays - T-Mobile & Verizon
    lasted 2h 42mMMS Messaging (MM4)us
  15. BandwidthOperational
    Bandwidth Local Market Impairment - 246 - Culpeper, VA
    lasted 10h 25m246 - Culpeper, VA

Bandwidth status: questions

Is Bandwidth down right now?

Bandwidth reports degraded performance (checked 2026-11-11 01:20 UTC from Bandwidth's official status page). Open: Toll-Free Port Activation Delays.

What is Bandwidth's uptime?

99.99% over the last 90 days and 99.99% over 12 months, from the incidents Bandwidth posted on its own status page. A major outage counts in full and a partial outage as 30% of its time, per component.

When was Bandwidth's last outage?

Bandwidth Local Market Impairment - 536 - Oklahoma City, OK, starting 2026-11-10 17:24 UTC and still open: https://down.guide/DWN-41e30b337d

How do I get alerts when Bandwidth goes down?

Subscribe to https://down.guide/feed?provider=bandwidth (RSS; add format=atom or format=json). In Slack, install the RSS app and run /feed subscribe with that URL; in Discord, give it to a feed bot such as MonitoRSS. No account needed.

Where does down.guide get Bandwidth's status?

From Bandwidth's official status page, https://status.bandwidth.com, read every minute. Bandwidth's words are quoted verbatim and linked.