Is Bandwidth Down?

No — Bandwidth is up

Reachable from all 8 checked regions

Average response time: 599ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://status.bandwidth.com

Bandwidth uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

623ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 54 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

54-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

650ms

DNS 71ms TCP 2ms TLS 20ms TTFB 644ms

arn

696ms

DNS 57ms TCP 1ms TLS 12ms TTFB 691ms

cdg

308ms

DNS 61ms TCP 2ms TLS 14ms TTFB 302ms

ord

356ms

DNS 99ms TCP 1ms TLS 12ms TTFB 351ms

sin

1383ms

DNS 118ms TCP 1ms TLS 13ms TTFB 1377ms

sjc

399ms

DNS 165ms TCP 14ms TLS 27ms TTFB 367ms

syd

621ms

DNS 180ms TCP 1ms TLS 11ms TTFB 616ms

yyz

380ms

DNS 69ms TCP 1ms TLS 12ms TTFB 371ms

What Bandwidth does

Bandwidth is a communications provider that owns its own network, selling voice, messaging, phone number management and emergency calling through APIs. It sits underneath other communications products as well as serving companies directly, so a Bandwidth incident can surface as a failure in a product whose users have never heard the name.

What an outage looks like

Outbound SMS is accepted by the API but never delivered, or arrives hours late in a burst. Inbound calls to your numbers fail to connect or reach the wrong destination. Number ordering and porting requests stall in a pending state. Call recordings do not appear after calls that otherwise completed normally. Emergency calling registration changes fail to take effect.

What to do about it

status.bandwidth.com is unusually granular, with 455 components covering United States inbound and outbound calling, messaging, international A2P messaging by region, number management, 911 services, portals and support. Find the specific service and country rather than the headline. Messaging and voice fail independently, so confirm which one is affected before rerouting. If 9-1-1 Services is degraded, treat that as the priority regardless of what else is happening.

Is it down for everyone, or just you?

If this page says Bandwidth is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Bandwidth outage FAQ

The API accepted my message but it never arrived. Is that an outage?

Possibly. Acceptance means Bandwidth queued the message, not that a carrier delivered it. During an incident the queue drains slowly and messages land late in a batch rather than never. Check the messaging component for the relevant country before resending, because resending duplicates anything that is merely delayed.

Is my problem with voice or with messaging?

They are separate services on separate components, and Bandwidth reports United States inbound calling, outbound calling and messaging as distinct groups. One can be entirely healthy while the other is not. Confirm which before making changes, because rerouting voice traffic will do nothing for a messaging incident and adds risk of its own.

What happens to number porting during an incident?

Porting and new number ordering are tracked under Number Management Services and stall rather than fail outright. A request left pending will normally continue once the component recovers. Submitting it again creates a duplicate order that has to be unpicked afterwards, so let the original request stand.

Does a Bandwidth outage affect emergency calling?

Bandwidth tracks 9-1-1 Services as its own component group, separate from ordinary voice, so emergency calling can be healthy during a general voice incident or affected on its own. If that group is degraded, it takes precedence over every other symptom, and any documented fallback path for emergency calls should be activated immediately.

Why does my provider blame Bandwidth when I am not their customer?

Because many communications platforms buy underlying voice and messaging capacity wholesale. An incident on Bandwidth's network therefore shows up inside products that never mention it, which is why an outage can look like a fault in a tool you use daily. Checking the upstream status page explains a symptom the immediate vendor's own page does not.

How we measure this

We request Bandwidth's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Bandwidth publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Bandwidth goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required