outages.live
Live
PusherIncident · 2026-08-22 03:17 UTC

Elevated errors on us2 cluster

ResolvedOfficial update

This incident has been resolved.

The latest update from Pusher.

State

Resolved

Started

72 d ago

2026-08-22 03:17 UTC

Lasted

1 h 31 min

until 2026-08-22 04:47 UTC

Worst impact

Notice

Timeline

3 updates
03:1703:3904:0204:2504:47
NoticeUpdate postedTimes in UTC

Investigating

15 min 16%

Monitoring

1 h 16 min 84%

Updates

Times in UTC

As posted by Pusher

Resolved2026-08-22 04:47 UTC

This incident has been resolved.

Monitoring2026-08-22 03:32 UTC

A fix has been implemented, and we are monitoring the results. All publish requests are now succeeding.

Investigating2026-08-22 03:17 UTC

We are investigating an increased error rate affecting the us2 cluster. All services remain operational, but a subset of customers may experience intermittent issues.

Affected components

3
Channels REST APIChannels WebSocket client APIChannels presence channels

Pusher in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

2 h 38 min

This incident

42% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 h 45 min
median 2 h 38 min
90 days agoToday

Other Pusher incidents

All incidents

Pusher·Elevated Errors on us2

This incident has been resolved.

Resolvedresolved 71 d ago

Follow Pusher

Your coding agent knows when Pusher is down, and tells you when a failure is theirs, not yours. You can also get Pusher incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "pusher" and tell me if Pusher has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=pusher
Slack
/feed subscribe https://outages.cc/feed.xml?providers=pusher

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane