outages.live
Live
PusherMaintenance ·

Beams maintenance

MaintenanceOfficial update

We will be upgrading the database that powers Pusher Beams to improve performance and reliability. During this window, the Beams API and the Beams section of the dashboard may be briefly unavailable. Requests made during an interruption may fail and should be retried. Channels is not affected.

The latest update from Pusher.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Pusher

Scheduled

We will be upgrading the database that powers Pusher Beams to improve performance and reliability. During this window, the Beams API and the Beams section of the dashboard may be briefly unavailable. Requests made during an interruption may fail and should be retried. Channels is not affected.

Affected components

2
BeamsBeams dashboard

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

Not comparable

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.

Resolved

Pusher·Elevated errors on us2 cluster

This incident has been resolved.

Resolved

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.live/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.live/feed.xml?providers=pusher
Slack
/feed subscribe https://outages.live/feed.xml?providers=pusher

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane