Skip to main content
The Strava API had an incident lasting ~1 hour starting at roughly 10am PST today where the streams endpoints & activities/{:id}/laps endpoint were being blocked and returning 403 “forbidden” status codes. 


 


The incident is now resolved. 


 


Apologies for any interruption in service. 

I believe I started seeing 403 codes from the streams today around 1pm MST but now I'm seeing 401 codes from them after weeks of fetching them without an issue. Am I the only one? Is there a chance athletes need to re-authenticate as a result of today's hiccup?

Edit: Nevermind. I messed something up when troubleshooting the 403 error earlier today. Carry on...


Reply