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
Presence channels Operational
Webhooks Operational
Pusher.js CDN ? Operational
[BETA] Push notifications service Operational
Marketing Website ? Operational
Payment API ? Operational
Stats Integrations ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Feb 25, 2017

No incidents reported today.

Feb 24, 2017

No incidents reported.

Feb 23, 2017

No incidents reported.

Feb 22, 2017

No incidents reported.

Feb 21, 2017

No incidents reported.

Feb 20, 2017

No incidents reported.

Feb 19, 2017

No incidents reported.

Feb 18, 2017

No incidents reported.

Feb 17, 2017
Resolved - The historical data was propagated to Datadog.

The system is now sending stats in realtime.
Feb 17, 19:17 UTC
Monitoring - The component responsible for triggering the Datadog requests was inactive since yesterday around 18:00 UTC.

We have identified and fixed the underlying issue. An alarm was added to our monitoring system to catch this type of issue earlier.

Stats are now being caught up to on and should reach realtime status in a couple of hours. We'll be monitoring this issue and we will update as soon all the historical metrics have reached Datadog.
Feb 17, 18:18 UTC
Feb 16, 2017

No incidents reported.

Feb 15, 2017
Resolved - Timeouts have subsided and the service has returned to acceptable performance. We also tweaked some parameters that will allow the service to deal with increased loads. We also deployed a new version with better logging and metrics to allow us to react more quickly and devise a fix, if future incidents do occur.
Feb 15, 10:18 UTC
Investigating - At 09:50 UTC the Push Notifications service was restarted and returned to acceptable performance. We are deploying additional metrics to understand the issue and determine a fix.
Feb 14, 11:32 UTC
Identified - The problem has been narrowed down to a load issue caused when a very large batch of APNS publishes are requested within a small timeframe. We are improving our metric collection to better understand the issue.
Feb 13, 14:33 UTC
Investigating - There appear to be intermittent request timeouts on our Push Notifications Service. We're actively investigating the cause.
Feb 13, 11:07 UTC
Feb 12, 2017

No incidents reported.

Feb 11, 2017

No incidents reported.