Hey, everyone from our team is getting this error when logging into our GoodData cloud, which was working fine earlier today. Are there any known errors on the GoodData side?

The error in your screenshot — a 404 "The requested endpoint does not exist or you do not have permission to access it" — is a known type of error that has appeared in similar GoodData Cloud cases. Based on past community reports, I cannot confirm whether there is a current, active outage right now, as my knowledge sources only cover past, already-resolved incidents. However, here's what you should do immediately: 1. Check the GoodData Status Page Visit support.gooddata.com to see if there is an active incident in your region (IAD1/us-east-1 or DUB1/eu-west-1). 2. Use the traceId You Already Have Your screenshot contains a `traceId`:

2dd19729dfdb8eb4d41d386e0f8eb008

. This is critical — share it with GoodData Support so they can look up the exact cause in their backend logs. [Unknown Error cases] 3. Try Basic Troubleshooting • Clear browser cache and try an incognito/private window. • Try a different browser or machine. • Wait a few minutes and retry — some past incidents recovered quickly. [short outage] 4. Contact GoodData Support If this is production-impacting, open a Severity 1 support ticket at support.gooddata.com and include: • Your organization URL • Your login email(s) • When the issue started • The `traceId`:

2dd19729dfdb8eb4d41d386e0f8eb008

In past similar cases, 404 errors affecting all users were caused either by a temporary platform issue (resolved by GoodData engineering) or a misconfiguration on GoodData's side — both of which required Support to investigate and fix. [platform issue] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.

Hi Emir. It's related to our new OAuth functionality. We have disabled it for now. It should start working in a few minutes. Sorry for any inconvenience. Try it and let us know if it's okay.

it's back now, thanks Shamil!