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

As listed on Strava’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Strava status & history page.

Related: Strava status & history. SquidGrid is not affiliated with Strava.