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
Beams dashboard Operational
Marketing Website ? Operational
Payment API ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 18, 2021

No incidents reported today.

Jan 17, 2021

No incidents reported.

Jan 16, 2021

No incidents reported.

Jan 15, 2021

No incidents reported.

Jan 14, 2021

No incidents reported.

Jan 13, 2021

No incidents reported.

Jan 12, 2021

No incidents reported.

Jan 11, 2021

No incidents reported.

Jan 10, 2021

No incidents reported.

Jan 9, 2021

No incidents reported.

Jan 8, 2021

No incidents reported.

Jan 7, 2021

No incidents reported.

Jan 6, 2021

No incidents reported.

Jan 5, 2021

No incidents reported.

Jan 4, 2021
Resolved - This incident has been resolved.
Jan 4, 12:15 UTC
Update - We are continuing to monitor for any further issues.
Jan 4, 09:51 UTC
Update - The database upgrade is complete.
Jan 4, 09:38 UTC
Update - We need to perform an upgrade to the database. There will be a period period of a few minutes where write operations will fail.
Jan 4, 09:12 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 4, 08:26 UTC
Investigating - We are investigating an issue with the database that is causing high latency for some requests. Requests that take longer than 30 seconds will be failed with a 503 error.
Jan 4, 07:48 UTC