TLS certificate mismatch

Incident Report for Pusher

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.

Posted Dec 01, 2015 - 13:45 UTC