What do you mean? Did it start working now for you or ...?

Come on, an API without access is for me a not working API and has not earned a green tick on the status dashboard 😄

Without a key you couldn't use the care. The care is working yes, but useless 😄

I see that it started working again for us.

Yes

Working now. Thank u!

Thanks @Elliott11 for sharing the details. Everything seems to be working fine on our side now.

Thanks to everyone involved in fixing the issue, and to everyone here for the help, too.

@Elliott11 it looks like the problem is back again? 

I'm getting a message back when I try to authenticate users saying it was blocked by cloudfront. Any solutions to this issue? 

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.

Unable to authenticate users using the normal authentication method, see my message below, basically getting a response back that it is blocked by cloudfront. 

Having the same issue with the authorization code exchange interface. i.e. 

Yep we are seeing this as well.

Seems the problem is back.

Hi Elliott, looks like the problem is back?

We are getting 401's on reads attempts (causing sessions to logout) and 403's during login attempts, started around 18:51:28 +02.

We're seeing the same thing since 18:05 UTC.. Not the best way to start the weekend.

We're encountering persistent 403 errors (rate limit exceeded) despite utilizing only 10% of our daily API limit. Our usage graph unexpectedly indicates both daily and 15-minute limit breaches. To address this, we've halted API requests, but the graph continues to reflect high traffic.

We suspect a potential DDoS issue is artificially inflating our usage. Has anyone else observed similar behavior? Any insights or assistance in resolving this issue would be greatly appreciated.

Hi all - apologies for this interruption. The team is looking into the issue and I'll keep you posted as soon as an update is available. 

The issue is now resolved - apologies to all of you who were impacted. 

We continue to have this issue and I have emailed support as well.  It's been 4 days since the service has been down.  We would appreciate help to get back our service.  Is anyone else facing this issue? 

It seems you have an other issue, the original problem was not a rate limit issue, but a blocked token request server. I suggest you post a separate new topic in this forum, you probably won't get attention for your issue here. And write support again, explain the problem properly and don't link it to the Strava outage issue with the blocked token requests server.

No, we had the first day, then one more for a couple hours, but other than it's been working fine.