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

Pusher REST API ? Operational
WebSocket client API ? Operational
Pusher Dashboard ? Operational
Stats Integrations ? Operational
Presence channels Operational
Webhooks Operational
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 23, 2017

No incidents reported today.

Jun 22, 2017

No incidents reported.

Jun 21, 2017

No incidents reported.

Jun 20, 2017

No incidents reported.

Jun 19, 2017

No incidents reported.

Jun 18, 2017

No incidents reported.

Jun 17, 2017

No incidents reported.

Jun 16, 2017

No incidents reported.

Jun 15, 2017

No incidents reported.

Jun 14, 2017

No incidents reported.

Jun 13, 2017
Resolved - Datadog has been caught up with historic stats data and is now running at real-time. Closing the issue as the problem is resolved. We will be investigating further and setting up further precautions to help avoid any future stats integrations outages.
Jun 13, 19:36 UTC
Monitoring - The issue has been fixed and historical stats data is now being uploaded to Datadog. We expect Datadog to be up to date and back to realtime stats monitoring within the next hour (19:30 UTC). We will continue monitoring the situation and update this status page when normal operation has resumed.
Jun 13, 18:13 UTC
Update - We have traced the problem to internal SSL connection failures. We are still investigating the cause of these failures. Stats are not lost and we expect Datadog to catch up when these internal connections are restored.
Jun 13, 16:20 UTC
Investigating - The component responsible for triggering the Datadog requests has been inactive since this morning around 01:15 UTC. We are investigating the issue now, once the system is fixed we expect to catch up Datadog with all historic data.
Jun 13, 10:34 UTC
Jun 12, 2017

No incidents reported.

Jun 11, 2017

No incidents reported.

Jun 10, 2017

No incidents reported.

Jun 9, 2017

No incidents reported.