Pusher System Status
All Systems Operational

About This Site

Pusher monitors all of its critical services both internally and through 3rd party services. If there is a disruption in service, incident notes will be updated here.

Below, you’ll find the current status of the Pusher infrastructure, as well as any recent issues or incidents we may have had.

If you think that something is not working with the service, please get in touch with us by submitting a ticket through http://dashboard.pusher.com/support

Channels REST API ? Operational
Channels WebSocket client API ? Operational
Channels Dashboard ? Operational
Channels Stats Integrations ? Operational
Channels presence channels Operational
Channels Webhooks Operational
Channels Pusher.js CDN ? Operational
Beams Operational
Chatkit Operational
Marketing Website ? Operational
Payment API ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 23, 2020

No incidents reported today.

Jan 22, 2020

No incidents reported.

Jan 21, 2020

No incidents reported.

Jan 20, 2020

No incidents reported.

Jan 19, 2020

No incidents reported.

Jan 18, 2020

No incidents reported.

Jan 17, 2020

No incidents reported.

Jan 16, 2020

No incidents reported.

Jan 15, 2020

No incidents reported.

Jan 14, 2020
Resolved - A postmortem will follow.
Jan 14, 19:38 UTC
Monitoring - All HTTP API traffic on mt1 is being directed to working instances.

We are still receiving a small number of requests to faulty instances. We believe this is due to clients not respecting the 60s TTL. Please clear your DNS cache.

We are monitoring our 4xx and 5xx rates on this cluster, and our traffic rates.

A postmortem will follow.
Jan 14, 19:07 UTC
Update - All DNS traffic is now being directed at working instances. Around ~10% of requests are still being received by faulty instances. We believe some of these are due to Keep-Alive; we are closing those connections to prompt clients to move over to working instances.

(Some other requests may be due to clients not respecting the 60s TTL; in this case users may need to clear their DNS caches.)
Jan 14, 18:48 UTC
Update - No users should be experiencing bad 5XX responses. Some users may still be experiencing 4XX responses. We are continuing to migrate traffic away from bad instances. We expect all traffic to be migrated within 60 minutes.
Jan 14, 18:34 UTC
Update - We are continuing to move traffic back to instances unaffected by the 4XX and 5XX issues.
Jan 14, 18:09 UTC
Identified - We have identified the cause of 4xx and 5xx responses. We are rolling back a failed deployment. We expect to see reduced error rates as traffic migrates.

We'll update this with more details soon.
Jan 14, 17:47 UTC
Update - We are continuing to investigate this issue.
Jan 14, 17:21 UTC
Investigating - We're seeing an increase in 5XX and 4XX errors on mt1 cluster and we're currently investigating the cause.
Jan 14, 15:22 UTC
Jan 13, 2020

No incidents reported.

Jan 12, 2020

No incidents reported.

Jan 11, 2020

No incidents reported.

Jan 10, 2020

No incidents reported.

Jan 9, 2020

No incidents reported.