Strava Bug | Strava Outage Server Status

Current Server Status

Official Status: Operational. The official status page reports that all systems (API, Uploads, Web) are currently stable.
Recent Stability: There was a confirmed Degraded Site Performance incident on March 5, 2026 (yesterday), which lasted about 45 minutes and caused “Server not responding” errors.
User Reports: A small volume of users continue to report “Network Error” on Android and intermittent syncing delays from Garmin devices, though these are no longer categorized as a “Major Outage.”

Strava has officially begun phasing out Facebook login support as of March 2026.

The Bug: Users attempting to log in via Facebook may encounter authentication errors or be locked out.
The Fix: You must link an email address or switch to Google/Apple ID in your account settings immediately.

Garmin/Fitbit Delays: There is a known intermittent delay where activities take 30+ minutes to appear.
Elevation Bug: A recent issue (reported March 6) shows 0 elevation on uploads from specific devices like the Fitbit Charge 6.
- Workaround: Use the “Correct Elevation” tool on the Strava desktop website to force a recalculation.

Some Android users are seeing a persistent “Network Error” message despite having a stable internet connection.

Quick Fix: Clearing the app cache or performing a fresh reinstall typically resolves this “phantom” server error.

Check the Official Status: Visit status.strava.com for real-time technical logs.
Verify Login: If you use Facebook, switch to an email-based login.
Manual Sync: If a ride/run isn’t showing up, try exporting the .FIT file from your watch’s portal and uploading it manually to the Strava web dashboard.