Beams SSL Certificate Expired
Incident Report for Pusher


On Sunday, December 5th, 2021 at 00:00:00 UTC, the SSL certificate on the public domain * expired. As a result, all requests for device subscription and notification publishing APIs failed with a “certificate expired” error. Our engineers got paged and started investigating the situation. The issue was promptly identified and the team worked on creating a new certificate. After the new certificate got deployed, the coming requests stopped receiving errors and the system went back to normal which concluded the incident.

That was an internal process failure where we failed to update the SSL certificate on time before it expired. Better monitoring will be applied to this SSL certificate and others. In addition to that, an investigation for using certificate auto-renewal tools is in progress.


  • Device subscription requests using client SDKs failed during the incident. They get automatically retried for Android and iOS SDKs but not for Web or Safari SDK.
  • Notification publishing API requests from the Server SDK failed during the incident.


All times are in UTC on the 5th of December 2021:

  • 00:00 UTC the SSL certificate for * expired
  • 00:25 UTC Our engineering on-call team was paged due to integration tests failing, the team immediately started investigating the situation.
  • 00:35 UTC After analyzing the Pusher Beams monitoring stack and logs of the integration test, the issue was identified and the team started working on creating a new SSL certificate.
  • 02:20 UTC The new certificate was deployed and the system went back to normal.
Posted Dec 06, 2021 - 13:25 UTC

This incident has been resolved.
Posted Dec 05, 2021 - 02:24 UTC
A fix has been implemented and we are monitoring the results.
Posted Dec 05, 2021 - 02:24 UTC
The issue has been identified and a fix is being implemented.
Posted Dec 05, 2021 - 01:13 UTC
We identified the issue and we're working on a solution.
Posted Dec 05, 2021 - 01:13 UTC
This incident affected: Beams.