Skip to main content
Question

Production outage from rate limits — Athlete & rate limit increase

  • April 27, 2026
  • 0 replies
  • 8 views

Forum|alt.badge.img

Posting here as a last resort, developers@strava.com has not responded after multiple attempts over weeks.

This is currently a production incident. On April 27 we saturated the 300 / 15 min app rate limit. Activity imports and history backfills are failing with HTTP 429 in a re-enqueue loop; we had to manually drain ~250 queued tasks to disk to stop the runaway and pause replay until the daily window resets at 00:00 UTC. Until then, paying customers' Strava syncs are degraded.

App: EndoGusto — https://endogusto.com
Client ID: 127630
Use case: SaaS platform for endurance coaches. Coaches build structured training plans (running, cycling, multisport); athletes connect Strava so completed workouts sync to the coach for review of pace, HR, power, and plan adjustment. Strava is a core, daily-use integration for our paying customers.

Current limits:
- Athletes: 585 / 999 (climbing weekly — we will hit the hard cap within weeks at current growth)
- Rate: 300 / 15 min, 3,000 / day

Requested:
- Athletes: 5,000
- Rate: 1,000 / 15 min reads, 10,000 / day reads

Engineering compliance:
- Honor X-RateLimit-Usage headers, exponential backoff on 429.
- Use webhooks for activity events (no polling).
- Operate under the API Agreement and brand guidelines.
 

Thanks,
EndoGusto engineering