Pusher Status

Official pageUpdated
Operational
All systems are operating normally. No issues detected.

System status

View historical uptime →
Channels REST API
Channels WebSocket client API
Channels Dashboard
Channels Stats Integrations
Channels presence channels
Channels Webhooks
Channels Pusher.js CDN
Beams
Beams dashboard
Marketing Website
Payment API

Incident overview

Total incidents

2

Active now

0

Resolved

2

Avg. resolution

2h 38m

Recent incidents

View all →

Elevated Errors on us2

none

Elevated errors on us2 cluster

none

Related Streaming services

All Streaming →

Confluent Cloud

Operational

Ably

Operational
100.00%

Frequently asked questions

Is Pusher down right now?

Pusher is currently operational. DevHelm monitors Pusher's official status page continuously and updates this page every 5 minutes.

What is Pusher's current uptime?

Uptime data for Pusher is still being collected. DevHelm needs sufficient monitoring data before reporting uptime percentages. Check back soon.

How many incidents has Pusher had recently?

Pusher has experienced 2 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 2h 38m. All incidents are currently resolved.

What components does Pusher monitor?

DevHelm tracks 11 individual components for Pusher, including Channels REST API, Channels WebSocket client API, Channels Dashboard, Channels Stats Integrations, Channels presence channels, and 6 more. Each component has its own status and 90-day uptime history shown above.

How can I get notified about Pusher outages?

You can subscribe to Pusher's incident feed via Atom/RSS at devhelm.io/status/pusher/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Pusher as a dependency in your DevHelm workspace.

About Pusher status monitoring

This page provides real-time operational status for Pusher, powered by DevHelm's continuous monitoring infrastructure. We track Pusher's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.

Pusher status data is refreshed every 5 minutes. We currently track 11 individual components, each with its own operational status and 90-day uptime history.

Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.

Track Pusher in your stack

Get alerted when Pusher has issues — before your users notice. Set up in 30 seconds.

Start Free →