Today, 9th May, (3 hrs ago) our app started getting a 403 error when accessing data for all authenticated athletes (this is for refreshing access tokens, collecting data - everything). Our code has not changed and we’ve received no communication as to why this might be happening. We are not even remotely close to hitting our agreed rate limits.
Interestingly we are still receiving webhook events, however when we try to collect data associated with the webhook events there’s a 403 error.
Is anyone else experiencing this? https://status.strava.com doesn’t report any issues.
Page 1 / 1
If you try to use something other than your webserver to access the API, do you still get errors? E.g. Postman, or a development machine with a different IP? My API calls are all working as expected so I wonder if it’s some type of CloudFront issue or something related to your webserver’s IP. If nothing else it would provide another data point to help figure out the issue.
This started happening today for us as well. Calling from our AWS Lambda, we were getting HTTP 403 with the cloudfront HTML response in a lot of our calls. Attempting the call from my local machine resulted in a normal response.
This seems to have started sometime today around `2025-05-09T17:20:35.640Z`, and this lambda has been running consistently for the last 2-3 years without seeing this error.
Reply
Login to the community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.