outages.live
Live
PusherIncident · 2026-08-23 01:27 UTC

Elevated Errors on us2

ResolvedOfficial update

This incident has been resolved.

The latest update from Pusher.

State

Resolved

Started

71 d ago

2026-08-23 01:27 UTC

Lasted

3 h 45 min

until 2026-08-23 05:12 UTC

Worst impact

Notice

Timeline

3 updates
01:2702:2303:2004:1605:12
NoticeUpdate postedTimes in UTC

Investigating

3 h 45 min 100%

Updates

Times in UTC

As posted by Pusher

Resolved2026-08-23 05:12 UTC

This incident has been resolved.

Investigating2026-08-23 02:03 UTC

We are seeing short but frequent spikes in errors affecting a small subset of traffic on the us2 cluster. The impact is intermittent and varies across customers, with the vast majority of customers experiencing no impact. Our systems have automatically scaled capacity in response to the unusual traffic bursts, and we are continuing to monitor the situation closely.

Investigating2026-08-23 01:27 UTC

We are seeing unusual traffic on the us2 cluster that is affecting a subset of traffic. The impact is limited to certain requests, while the majority of traffic continues to operate normally. We are actively investigating the cause and working to mitigate the impact.

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

1.4× 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 cluster

This incident has been resolved.

Resolvedresolved 72 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