Pusher: Network disruption
Timeline of updates
- resolved
Between the hours of 00:00 and 05:00 GMT on the 26th many of our services experienced networking disruptions, mainly manifesting as increased latencies. The nature of the disruptions leads us to believe that our hosting provider (AWS) had some difficulties upstream of the US-EAST region. Our customers may have seen increased latency to our REST API and clients may have seen increased latency connecting to our websocket endpoints, though our monitoring does not indicate a significant rate of failure. We apologise for the late notification on this disruption.
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-02-26 18:29 UTC, resolved after 0 min, 1 update(s).
- Title
- Network disruption
- Vendor
- Pusher
- Date
- URL
- https://rewindex.com/company/pusher/incidents/k5n7tbq90sqs
Pusher profileRecent Pusher incidentsAll outages on February 26, 2015Pusher in February 2015MarkdownJSON