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
[BETA] Push notifications service   Operational
Marketing Website   ? Operational
Payment API   ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jun 24, 2018

No incidents reported today.

Jun 23, 2018

No incidents reported.

Jun 22, 2018

No incidents reported.

Jun 21, 2018

No incidents reported.

Jun 20, 2018
Resolved - Everything is back to normal. Let us know if you see anything a bit awry! 🚀
Jun 20, 20:28 UTC
Monitoring - We have fixed the underlying issue and data is now being sent in realtime. We have also added more monitoring to the system in question. We're sorry for any inconvenience!
Jun 20, 18:52 UTC
Identified - We have identified an issue where customers were not receiving metrics through their Datadog or Librato accounts. We have found the cause and are working to restore service.
Jun 20, 15:53 UTC
Jun 19, 2018

No incidents reported.

Jun 18, 2018

No incidents reported.

Jun 17, 2018

No incidents reported.

Jun 16, 2018

No incidents reported.

Jun 15, 2018

No incidents reported.

Jun 14, 2018

No incidents reported.

Jun 13, 2018

No incidents reported.

Jun 12, 2018
Resolved - We have restarted the read-only database and it's now healthy.

We will be looking at the possible mitigations to reduce the odds of this happening again. Sorry for the disruption caused.
Jun 12, 14:21 UTC
Identified - We have identified the issue: the read-only database is unreachable.

In the meantime, we are using the primary database for all queries.
Jun 12, 14:02 UTC
Investigating - We are experiencing some issues with the Publish API. We are looking into the cause of this.
Jun 12, 13:43 UTC
Jun 11, 2018

No incidents reported.

Jun 10, 2018

No incidents reported.