- Level
- confirmed
- Worst impact
- Degraded
What to do
Check whether your product depends on Bandwidth. 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 0m it lasted.
Anything that failed between 2026-04-18 00:30 UTC and 2026-04-18 00:30 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.
Updates from Bandwidth 1
- resolved
For a brief period of time, SMS and MMS messages with AT&T destinations were either delayed in delivery or failed to deliver as expected. Teams are observing expected network behavior at this time and consider this incident resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-cf85c2e680
Is Bandwidth still down?
No, this incident was resolved 2026-04-18 00:30 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
0m, from 2026-04-18 00:30 UTC to 2026-04-18 00:30 UTC, by the times Bandwidth posted.
What caused it?
Bandwidth hasn't published a root cause. If it does, it shows here.
Where does this come from?
Bandwidth's official status page, https://status.bandwidth.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.