Pusher: Intermittent request failures on EU cluster
Timeline of updates
- resolved
Between the hours of 02:30 and 09:30 this morning a node in our EU cluster became degraded and automated health-checking failed to remove it from service correctly. This resulted in a proportion of client requests to both the HTTP API and the WS API to receive authentication errors for valid requests to the EU cluster. Only customers of the EU cluster were affected. We are investigating the failure of the health-checkers to route around the failed node and apologise for any inconvenience caused.
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 2016-01-11 10:26 UTC, resolved after 0 min, 1 update(s).
- Title
- Intermittent request failures on EU cluster
- Vendor
- Pusher
- Date
- URL
- https://rewindex.com/company/pusher/incidents/bjcpcmbdkpgn
Pusher profileRecent Pusher incidentsAll outages on January 11, 2016Pusher in January 2016MarkdownJSON