I see on strava status there are problems. We are facing problems submitting activities via API. Normally this is very stable for years for us so we are pretty sure strava API has errors. Anyone else seeing this?
Solved
Aug 15th, 2024 - API Issues?
+7Best answer by Elliott
@jaimegil please don't apologize for mentioning me directly!
There were residual issues from the incident yesterday but traffic should be restored for all apps. Sincerest apologies to anyone who experienced this issue and for our API status page not reflecting the behavior some of you were experiencing.
If anyone is still experiencing issues please let me know.
+2Since the outage yesterday I'm getting 403 errors when trying to refresh tokens for all users. It worked fine for a long time before that. Anyone else having the same issue?
+7What is interesting, I did a ride today with my Garmin and that posted correctly to Strava. They must have special API's or they have turned off the service for the smaller guys to help reduce traffic.
+4We're also getting 403 errors on all API calls. It looks like Strava's Cloudfront is blocking API calls for most cases (they work from my personal computer, but not from our servers).
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
+4Hi @Elliott11, sorry to mention you directly. Just wanted to know if there is some info from the team about the API errors. Thanks a lot!
+24I'm getting the same 403 errors others are seeing. My site has been down for ~12 hours now.
Interestingly on my development machine (localhost) everything is working perfectly and has been since late last night when the initial fix was made (~8 hours ago)
+2Hi,
I have been getting that exact same error message from from the Strava API in my live server but works fine from my personal computer!
+3I have the same issue for ClientID 1033 with the error 403
Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.+2I have the exact same issue since last night. Works fine from my local machine but my live server gets the following error:
Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
+24Update: API access appears to be restored for my site as of ~6:30am EST/10:30am GMT
Anyone reading this: It looks like the rate limit headers have changed, be sure to update your code if needed. See https://communityhub.strava.com/t5/developer-discussions/rate-limit-headers-changed/td-p/38327
+3Same problem here. Since `2024/08/15 00:17:05 (GMT+0)` refreshing the access token wont work. On profile page i could see that the access token is expired. Status page says, API where fine 😞
+8Things are still not working for us. Same error.
+2Came here for the same reason. My server is getting a 403 (Forbidden) response when trying to do the token exchange; though it works fine for me locally. I was afraid my server got blacklisted, but it sounds like there's a bigger problem going on.
+24I wonder if they're slowly allowing apps access to avoid overloading the server with the massive request backlog. That seems like it would be a smart thing to do.
+8That wouldn't seem like a bad idea. It would be nice to have some communication about that though if it's the case.
+3I am also seeing the same problem. If I had to guess, its most likely a AWS security rule that has been applied that blocks requests from certain types of servers (like ones in data centers). I manually updated the access token on my server to see if is just a problem with refreshing it, but it still fails to fetch activities returning a status code of 403.
+3Could be that or they simply applied some AWS security rule that broke apps running in datacenters. I think that requests from personal machines still work so that apps like Garmin can upload activities so that most upload apps work. The problem is that obviously the API is still broken for anyone using the Strava API on the server.
+1We have the same problem, is there a way to report this to Strava? - since according to the status page https://status.strava.com/ the API is working fine 😕😕
+10I think the API is working, but not the authorization (token and refresh token requests), although I didn't test it. I also opened a ticket a few hours ago, but I don't expect any reply. I think there is a serious issue because this is already taking more than 12 hours.
- Community Manager
- 132 replies
- Answer
@jaimegil please don't apologize for mentioning me directly!
There were residual issues from the incident yesterday but traffic should be restored for all apps. Sincerest apologies to anyone who experienced this issue and for our API status page not reflecting the behavior some of you were experiencing.
If anyone is still experiencing issues please let me know.
Reply
Most helpful members this week
Login to the community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.