Skip to main content
Bandwidth

Australia based SMS Messaging Incident

Degraded Lasted 3h 40m · started · Bandwidth's page

Level
confirmed
Worst impact
Degraded
Components
International A2P Platform (SMPP), International A2P Platform (HTTP)
Regions
au

What to do

  • Check whether you use Bandwidth International A2P Platform (SMPP), International A2P Platform (HTTP) in au. 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 3h 40m it lasted.

    Anything that failed between 2026-10-20 16:22 UTC and 2026-10-20 20:02 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 5

  1. investigating

    Bandwidth teams are investigating an incident impacting Inbound and Outbound SMS messaging to Australia based destinations. Outbound messages may not result delivery receipts, inbound messages may not deliver as expected.

    provider

  2. identified

    Teams have identified the source of this incident as an off-network vendor condition. Teams are working with the impacted vendor to restore expected messaging behaviors.

    provider

  3. monitoring

    Teams are observing expected messaging behavior and are monitoring for stability.

    provider

  4. resolved

    This incident has been resolved.

    provider

  5. postmortem

    Between 14:45 UTC and 17:16 UTC on October 20, 2026, Inbound and Outbound SMS messaging to Australia based destinations experienced missing delivery receipts and failed or timed-out messages. Bandwidth is continuing to investigate this issue to identify all actions necessary to prevent this from recurring and will update this post with an Incident Report after investigations have concluded. 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

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-52fe8be678

Is Bandwidth still down?

No, this incident was resolved 2026-10-20 20:02 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.

How long did it last?

3h 40m, from 2026-10-20 16:22 UTC to 2026-10-20 20:02 UTC, by the times Bandwidth posted.

What was affected?

Bandwidth named International A2P Platform (SMPP), International A2P Platform (HTTP) in au.

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.