Pusher: TLS certificate mismatch
Timeline of updates
- resolved
From approx 11:30 GMT yesterday until 11:30 GMT this morning, the endpoint for our realtime fallback servers (which serve the small percentage of clients not capable of websockets) returned the incorrect certificate - *.pusherapp.com was served for the endpoint sockjs.pusher.com. As a result, clients not capable of websocket connections and configured to connect over TLS may have seen a certificate security warning, or may have silently failed to connect to Pusher. An automated alarm should have been raised immediately, but we found this morning that it was not configured to be strict enough. We apologise for this oversight. The certificate choice has been rectified, the alarms have been corrected and we are investigating other procedural improvements would prevent such an error in future.
From Pusher’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.pusher.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Pusher, started 2015-12-01 13:45 UTC, resolved after 0 min, 1 update(s).
- Title
- TLS certificate mismatch
- Vendor
- Pusher
- Date
- URL
- https://rewindex.com/company/pusher/incidents/8346t6rhxdpc
Pusher profileRecent Pusher incidentsAll outages on December 1, 2015Pusher in December 2015MarkdownJSON