Is Pusher Down?

No — Pusher is up

Reachable from all 8 checked regions

Average response time: 250ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://status.pusher.com

Pusher uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

333ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 53 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

53-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

dfw

162ms

DNS 84ms TCP 1ms TLS 3ms TTFB 157ms

ewr

53ms

DNS 22ms TCP 2ms TLS 4ms TTFB 45ms

fra

308ms

DNS 10ms TCP 1ms TLS 4ms TTFB 301ms

gru

385ms

DNS 25ms TCP 1ms TLS 3ms TTFB 380ms

iad

136ms

DNS 114ms TCP 2ms TLS 4ms TTFB 128ms

jnb

461ms

DNS 39ms TCP 0ms TLS 5ms TTFB 458ms

lax

226ms

DNS 16ms TCP 1ms TLS 4ms TTFB 220ms

lhr

273ms

DNS 18ms TCP 3ms TLS 5ms TTFB 265ms

What Pusher does

Pusher provides hosted realtime infrastructure. Channels delivers WebSocket messages so applications can push live updates to browsers and mobile clients without running their own socket servers, and Beams sends mobile push notifications. Products embed it for chat, live dashboards, collaborative editing and notification badges, which means an outage shows up inside someone else's app rather than on a page of Pusher's.

What an outage looks like

Live updates stop arriving while the rest of the page works, so a dashboard shows stale numbers and a chat window accepts typing but delivers nothing. The pusher-js client reports its connection state as unavailable and retries every 15 seconds. Server-side publishes fail if the REST API is affected, and webhooks that notify your backend of channel events stop firing.

What to do about it

Check status.pusher.com and read the component rather than the headline: Channels REST API, the WebSocket client API, presence channels, webhooks and the Pusher.js CDN each fail on their own, and Beams is a separate product again. Clients reconnect automatically, so there is usually nothing to restart. If publishes are failing, queue them on your own server rather than dropping the events.

Is it down for everyone, or just you?

If this page says Pusher is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Pusher outage FAQ

Are messages queued while Pusher is down?

Assume not. Channels is a delivery pipe rather than a durable queue, so an event published during an outage is not waiting for clients when the connection returns. Applications that need the missed state usually re-fetch it over HTTP on reconnect rather than relying on replay. Buffering publishes on your own server is the part of this you control.

My app loads but nothing updates. Is that a Pusher outage?

It fits the pattern. Channels carries only the realtime layer, so the page, its API calls and its data all keep working while pushed updates stop. Check the connection state in the browser console: pusher-js moves to unavailable and retries every 15 seconds during a disconnect. If it reports connected and updates still do not arrive, the problem is more likely your channel or event names.

Does a Channels outage affect Beams push notifications?

Not necessarily. The status page lists Beams and the Beams dashboard as their own components, separate from every Channels row, so mobile push can keep working while WebSocket delivery is down. They also depend on different downstreams, since Beams hands notifications to Apple and Google gateways that fail independently of Pusher.

Why does the Pusher.js CDN have its own status row?

Because many applications load the client library from Pusher's CDN rather than bundling it. If that row is affected, the script tag fails and the realtime layer never initialises, which looks like a total outage from the browser even when Channels itself is healthy. Bundling pusher-js with your own assets removes that dependency.

How we measure this

We request Pusher's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Pusher publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Pusher goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required