Live / Strava / Incident
Strava: Beacon API Failures
Strava · strava.comMinor incidentResolved2026-10-23 21:38 UTC
Public — what happened
Summary
Strava reported a minor incident titled Beacon API Failures, saying it began at 20:50 UTC on 2026-10-23. The company said it was looking into connection problems and errors affecting its Beacon features. Its posted text did not name a cause or say who was affected, and the incident was marked resolved at 21:38 UTC the same day.
Affected
Mobile applications, Strava.com
Timeline
- Started — 2026-10-23 20:50 UTC
- Investigating — 2026-10-23 20:50 UTC
- Resolved — 2026-10-23 21:38 UTC · 48 min 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.