Strava: vendor-reported critical incident on September 27 (tracked 3h 0m)
Sep 27, 03:55 PM → Sep 27, 06:56 PM · 3h 0m · high
Strava reported a critical-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 3h 0m, from Sun, 27 Sep 2026 15:55:58 GMT to Sun, 27 Sep 2026 18:56:23 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.
Impact
During the 3-hour incident, Strava experienced a high-severity disruption. This period of instability may have affected user access to the service. No user-reported data was collected for this incident.
Incident timeline
- Sep 27, 03:55 PM
The vendor reported a critical-impact incident on its own status page; PulseWatch began tracking it
- Sep 27, 03:55 PM
Status updated: possible issue
- Sep 27, 06:56 PM
PulseWatch closed the incident
Official updates
- Sep 27, 03:55 PM
Strava reported the incident on its status page.
View official source