Pusher: Incorrect subscription changes affecting some accounts

What to do

Check whether you use Pusher Channels REST API, Channels Webhooks in us. 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 19h 20m it lasted.
Anything that failed between 2026-01-22 16:38 UTC and 2026-01-23 11:58 UTC may need a replay.
Subscribe to Pusher's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=pusher works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

identifiedJan 22, 2026, 4:38 PM UTC
We’ve been made aware of an issue caused by our billing provider, Maxio, where a limited number of our customer accounts were incorrectly downgraded due to an incident on their side. We are actively working with Maxio to restore all affected accounts to their correct subscription levels.
provider
resolvedJan 23, 2026, 11:58 AM UTC
All affected accounts have been restored to their correct subscription levels. We sent an email yesterday to all impacted customers. If you notice any issues with your subscription, please contact us.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Pusher still down?

No, this incident was resolved 2026-01-23 11:58 UTC. For Pusher's live state, see https://down.guide/pusher.

How long did it last?

19h 20m, from 2026-01-22 16:38 UTC to 2026-01-23 11:58 UTC, by the times Pusher posted.

What was affected?

Pusher named Channels REST API, Channels Webhooks in us.

What caused it?

Pusher hasn't published a root cause. If it does, it shows here.

Where does this come from?

Pusher's official status page, https://status.pusher.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.