rewindex

CompaniesPusherIncidents

Pusher: SSL certificate renewal for our legacy telemetry endpoint

No impact listedStatus: resolvedStarted Resolved (-203 min)1 updatestspg.io (opens in new tab)

Timeline of updates

  1. resolved

    The SSL certificate for our client stats endpoint expired at 00:00 UTC, but the issue was resolved at 8:49 AM UTC.
    During this period, clients who opted to send client stats using older versions of the JavaScript SDK for web (PusherJS) encountered some errors and were unable to send telemetry data to our servers.

    This does not impact any functionalities of our SDK, even in older versions. However, it's worth mentioning that we are unable to verify this on much older versions of our SDKs, as our team no longer monitors them.

    We have replaced the certificate on this endpoint with an auto-renewable certificate to prevent this issue from happening. The client stats endpoint is a legacy endpoint and is not being used in newer versions of our SDKs.

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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Pusher, started 2024-04-22 09:22 UTC, resolved after -203 min, 1 update(s).

Title
SSL certificate renewal for our legacy telemetry endpoint
Vendor
Pusher
Date
URL
https://rewindex.com/company/pusher/incidents/37l3q354d001

Pusher profileRecent Pusher incidentsAll outages on April 22, 2024Pusher in April 2024MarkdownJSON