Live / Strava / Incident
Strava: Investigating site performance and availability issues
Strava · strava.comMinor incidentResolved2026-10-25 16:03 UTC
Public — what happened
Summary
Strava said it was looking into a problem affecting how well its site performed and whether it was available, which it rated as minor. The company first reported the issue at 13:20 UTC on 2026-10-25 and posted a short update at 13:54 UTC saying its investigation was still going. Strava did not name a cause in the text provided, and it marked the incident resolved at 16:03 UTC the same day.
Affected
Mobile applications, Strava.com, API, Upload, MCP Connector
Timeline
- Started — 2026-10-25 13:20 UTC
- Investigating — 2026-10-25 13:20 UTC (2 updates)
- Resolved — 2026-10-25 16:03 UTC · 2h 43m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Strava against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Strava: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Strava report →
More from Strava
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.