Skip to main content
Question

All API requests return HTTP 500 after upgrade to Standard Tier

  • June 1, 2026
  • 12 replies
  • 228 views

abrego
Forum|alt.badge.img+1

Hi,

Since I upgraded (today) my app to the new Standard Tier, every API call returns HTTP 500 with body {"message":"error"} across all endpoints, all athletes, and even the "Your Access Token" from my developer dashboard.

Reproduced with curl directly (no intermediary code):

bash

curl -i https://www.strava.com/api/v3/athlete \
-H "Authorization: Bearer <dashboard token>"

 

HTTP/2 500
{"message":"error"}
x-envoy-upstream-service-time: 42
x-request-id: e180229a-1c45-4773-9f0d-4ad558b0cacd

Endpoints tested: /athlete, /athlete/routes, /athlete/activities. Same result on all of them.

The OAuth flow completes fine, tokens are issued with sensible expires_at, so it looks like the backend is rejecting every call from this client_id post-upgrade.

App: MoguWind client_id: 236823

Has anyone else hit this after the tier migration today? Is there a propagation delay, or an extra step I might be missing, terms acceptance, billing, something else?

Thanks, Javi

12 replies

Forum|alt.badge.img
  • Hub Starter
  • June 1, 2026

I just migrated and I am experiencing the same issue. I’ll let you know if I figure out a solution


Forum|alt.badge.img
  • Hub Starter
  • June 1, 2026

+1, same here.
App ID: 143381 (- personal use)
Upgraded to Standard Tier today, exact same
  symptoms:
- HTTP 500 {"message":"error"} on ALL endpoints
  (/athlete, /athlete/activities, /athlete/zones,
  /segments/*)
- Both OAuth-issued tokens AND dashboard "Your 
Access Token" return 500
- Reproduced with raw curl, no intermediary
- OAuth /oauth/token still works fine

Started right after the tier upgrade.


Forum|alt.badge.img
  • Hub Starter
  • June 1, 2026

+1, Mawida (client_id: 187129), upgraded to Standard Tier ~2026-06-01. Same symptoms: HTTP 500 {"message":"error"} on all endpoints (/athlete,
  /athlete/routes, /athlete/activities), with envoy upstream service time but no rate-limit headers. OAuth still issues fresh tokens normally.


dlandre
Forum|alt.badge.img+4
  • Hub Rookie
  • June 1, 2026

+1 same issue.  Warning to other developers don’t upgrade until this is resolved.  I’ll post if I can figure anything else out.


Forum|alt.badge.img
  • Hub Starter
  • June 1, 2026

Hi, I'm experiencing the exact same issue. Posting to confirm this is not isolated.


Forum|alt.badge.img

I'm also facing the same issue. It was working fine until around 8 PM IST today; by 10 PM IST it had stopped.


Forum|alt.badge.img

Im getting the same exact issue as well. 


Forum|alt.badge.img

Same. Classic given the whole “we’re raising the requirements” stance.


Forum|alt.badge.img
  • Hub Starter
  • June 1, 2026

Same


Forum|alt.badge.img
  • Hub Starter
  • June 1, 2026

exact same issue


dlandre
Forum|alt.badge.img+4
  • Hub Rookie
  • June 1, 2026

I confirmed by testing with another, un-upgraded Client ID:  The 500’s only occur if you self-upgrade.  If you use a non-upgraded account everything continues working fine (with the single-user limit of course).

Moral:  DON’T SELF-UPGRADE UNTIL THIS IS VERIFIED FIXED.


Forum|alt.badge.img

Same. Classic given the whole “we’re raising the requirements” stance.

Just had a success. Unclear if I got lucky or if the issue is resolved.