SSL certificate renewal for our legacy telemetry endpoint

What to do

• Check whether your product depends on Pusher. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2024-04-22 09:22 UTC and 2024-04-22 06:00 UTC may need a replay.

• Subscribe to Pusher's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=pusher works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Pusher 1

1. resolvedApr 22, 2024, 6:00 AM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.