Live

Pusher

Pusher is operational

Checked 22 s ago Operational

History

90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

2 h 38 min

Longest incident

3 h 45 min

Components

11
Channels REST API Operational
90 days ago1 day with an incidentToday
Channels WebSocket client API Operational
90 days ago1 day with an incidentToday
Channels Dashboard Operational
90 days agoNo incidentsToday
Channels Stats Integrations Operational
90 days agoNo incidentsToday
Channels presence channels Operational
90 days ago1 day with an incidentToday
Channels Webhooks Operational
90 days agoNo incidentsToday
Channels Pusher.js CDN Operational
90 days agoNo incidentsToday
Beams Operational
90 days agoNo incidentsToday
Beams dashboard Operational
90 days agoNo incidentsToday
Marketing Website Operational
90 days agoNo incidentsToday
Payment API Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane