Bandwidth outages and problems
In the past 24 hours, 145 user reports came in for Bandwidth. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 98.96% uptime for the day.
The most recent spike big enough to count as an outage was 18 hours ago. The busiest 15-minute window of the day had 13 reports, about 18 hours ago.
-
Outage
Ended 18 h agoLasted 15 min13peak reports
Bandwidth in October 2026
- Problem reports in October (since 27 October)
- 152
Monthly report for October 2026
What people said was wrong in recent problem reports for Bandwidth, as a share of those reports:
- 100% Internet
Where Bandwidth problem reports come from
Recent reports came from 18 areas. The most came from around Oklahoma City, OK, San Diego, CA and Wichita, KS. Share of recent reports by area, named after its biggest town:
- 35% Oklahoma City, OK
- 7% San Diego, CA
- 4% Wichita, KS
- 4% Tulsa, OK
- 3% Chicago, IL
- 3% Dallas, TX
From 144 recent problem reports. Big cities always send the most, so reports from many places point to a widespread problem, and one area far ahead of the rest can mean a regional one. Town names: GeoNames.
Bandwidth problem spikes, last 30 days
Since 27 October, Bandwidth had 1 outage spike.
-
Outage
Wed 28 Oct, 02:33–02:48Lasted 15 min13peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 27 October 2026. Monthly reports for all services
How to fix Bandwidth not working
Bandwidth is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach bandwidth.com over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not Bandwidth.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
While Bandwidth is down: what to use instead
- Twilio Send urgent voice or SMS traffic through a second provider when your main API calls fail and the queue starts backing up.
- Vonage Use its SMS and voice APIs as a backup path for critical notifications if your integration can point at another endpoint.
- Plivo Route time-sensitive messages through this API when you need a separate delivery path and your code already supports more than one provider.
- Official status page Open the official status page first to see whether the service has confirmed a wider incident before you switch traffic.
Problems at the same time as Bandwidth
Since 27 October, Bandwidth's only spike in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
During the latest spike
Bandwidth: Wed 28 Oct, 02:33 to 02:48
- ESPN Fantasy Football, outage,27 Oct 19:50 to 21:03
- Astound, outage,27 Oct 19:50 to 08:26
- Brightspeed, outage,27 Oct 20:35 to 03:12
- AT&T, outage,00:03 to 04:03
- TDS Telecom, outage,00:18 to 03:18
- Disney+, outage,01:03 to 03:03
- PUBG Battlegrounds, outage,01:03 to 05:18
- Smite, outage,01:03 to 02:48
12 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report Bandwidth problems
The busiest hour for reports about Bandwidth is 02:00 to 03:00 Central European time, and the busiest day is Wednesday.
By hour of the day
- 00:00 to 01:00: 0.74 reports on an average day
- 01:00 to 02:00: 0.99 reports on an average day
- 02:00 to 03:00: 1 report on an average day
- 03:00 to 04:00: 0.57 reports on an average day
- 04:00 to 05:00: 0.13 reports on an average day
- 05:00 to 06:00: 0.1 reports on an average day
- 06:00 to 07:00: 0.1 reports on an average day
- 07:00 to 08:00: 0.13 reports on an average day
- 08:00 to 09:00: 0.07 reports on an average day
- 09:00 to 10:00: 0 reports on an average day
- 10:00 to 11:00: 0 reports on an average day
- 11:00 to 12:00: 0 reports on an average day
- 12:00 to 13:00: 0.05 reports on an average day
- 13:00 to 14:00: 0.08 reports on an average day
- 14:00 to 15:00: 0.16 reports on an average day
- 15:00 to 16:00: 0 reports on an average day
- 16:00 to 17:00: 0.07 reports on an average day
- 17:00 to 18:00: 0.15 reports on an average day
- 18:00 to 19:00: 0.07 reports on an average day
- 19:00 to 20:00: 0.1 reports on an average day
- 20:00 to 21:00: 0.34 reports on an average day
- 21:00 to 22:00: 0.55 reports on an average day
- 22:00 to 23:00: 0.68 reports on an average day
- 23:00 to 00:00: 0.49 reports on an average day
By day of the week
- Monday: 0 reports on an average Monday
- Tuesday: 11 reports on an average Tuesday
- Wednesday: 34 reports on an average Wednesday
- Thursday: 0 reports on an average Thursday
- Friday: 0 reports on an average Friday
- Saturday: 0 reports on an average Saturday
- Sunday: 0 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 21 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
Bandwidth IP address, servers and network
Checking bandwidth.com from our server…
Service updates from @bandwidth
No posts about problems from @bandwidth in the last 14 days. The latest is from .
How we track Bandwidth
The status on this page comes from user-submitted problem reports for Bandwidth, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Bandwidth, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Bandwidth's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.