is gooddata cloud down? Our workspace will not load - getting just a white screen with spinning wheel on the browser tab

Thanks for checking in. We can’t confirm a current, ongoing outage from the provided sources alone. There have been occasional incidents where dashboards or login temporarily failed, but they were resolved quickly and usually tied to specific regions or components. If you’re seeing a white screen with a spinner, it may be either a transient incident or a workspace-specific issue. [[June 26 issue](https://support.gooddata.com/hc/en-us/articles/42486336068371-Thu-June-26th-2025-Unexpected-GoodData-Cloud-Issue); [White screen cases](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1722460116204409?thread_ts=1722460116.204409&cid=C04S1MSLEAW)] Quick steps to move forward: - Check the GoodData announcements/status for any active incident, especially for your region (IAD1 us-east-1 or DUB1 eu-west-1). [[June 26 issue](https://support.gooddata.com/hc/en-us/articles/42486336068371-Thu-June-26th-2025-Unexpected-GoodData-Cloud-Issue); [EU incident](https://support.gooddata.com/hc/en-us/articles/38288731795987-Thu-Feb-6th-2025-Unexpected-GoodData-Cloud-Issue-on-DUB1-Datacenter-eu-west-1)] - Open your browser dev tools and capture: - Any TraceID/ErrorID from failing requests (Network tab). - A HAR file if possible. [[Workspace won’t load](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1732108399136049?thread_ts=1732108399.136049&cid=C04S1MSLEAW); [HAR guidance](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1756895551232889?thread_ts=1756895551.232889&cid=C04S1MSLEAW)] - Try an alternate browser or private window, and clear cache. [[Access issue steps](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1741771902585219?thread_ts=1741771902.585219&cid=C04S1MSLEAW)] - If this started “just now,” allow a few minutes and retry—some incidents recover quickly. [[Short hiccup](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1747922987520129?thread_ts=1747922987.520129&cid=C04S1MSLEAW); [Intermittent outages](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1739817622391179?thread_ts=1739817622.391179&cid=C04S1MSLEAW)] If the white screen persists (especially after LDM changes), it can be a broken dashboard definition. As a temporary workaround you can delete the affected dashboard via API while we investigate: DELETE /api/v1/entities/workspaces/{workspaceId}/analyticalDashboards/{dashboardId}. [[White page workaround](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1722460116204409?thread_ts=1722460116.204409&cid=C04S1MSLEAW)] Please share: - Your organization URL and region. - Whether it’s UI only or also embedded. - One failing dashboard/workspace URL and a TraceID/HAR. With that, we can quickly check backend logs and confirm if this is a localized issue or part of a wider incident. [[Targeted triage](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1732108399136049?thread_ts=1732108399.136049&cid=C04S1MSLEAW)]

Hello Max, Thank you for reaching out to us. We are investigating it right now. Will update you here as soon as possible. Thank you for your cooperation.

We are seeing the same issue.

Can you please try and access the platform once again? If you’re still seeing any issue, please let us know

working thx!

Working also. please post the cause. Our industry is highly regulated and time critical. All issues of why our reporting is down are documented.

We are still seeing response times of 1 to 2 seconds on some requests, is this still ongoing?

Hello @Greg Lindstrom, Once we have more information, we will share it with you here. Thank you for your patience.

Hello, I work with Aaron Gunn, we're seeing generally longer than expected times for API call resolutions, especially from the attribute calls.

Hello Steve, It seems like the issue you are having is different than the one that is described here. To give better service, we can continue the conversation in the thread that you opened yesterday. Thank you.

How is it different? Apologies, but sounds like they were not able to load data from their workspaces, and we saw the same thing

I am sorry if my explanation was not clear. The issue that is described here is directly connected to service disruption rather than slowness issues as you have explained in this thread and the other one. Since you are on the same namespace, you might have experienced service disruption today. As far as I understand we are talking about 2 different problems here. 1. Service disruption that happened today 2. Slowness in your domain. First problem is resolved right now and your domain should be accessible. Since second problem is about platform being slow rather than accessibility issues, i propose discussing it further in the previous thread. Thank you for your understanding.

For 1, • a service disruption would have been seen as "general" slowness, so that would have elevated the issue for someone coming through • was there a notice/notification about that on the status pages/subscriptions? For 2 • agreed we can work on the other thread, since our users use an embedded model, "everything" is related -> especially if things don't return, it looks the same to someone who spins/weights for 30s for things to load on the page.

Thank you for your message. Since we agreed to continue the conversation in the previous thread for number 2, we can focus here on the 1st issue. My colleague from technical support will respond here as soon as possible regarding the outage. Thank you for your understanding and cooperation.

Hello all, This is Jan from the Technical Support team. I’d like to share more details regarding the recent incident. Following our standard release and delivery process, a component responsible for handling metadata calls and managing connections to the metadata database became unresponsive. This resulted in issues with loading GoodData Cloud environments. We are currently conducting a thorough investigation to identify the exact root cause. While we don’t have additional details to share at this moment, please be assured that we take platform stability very seriously. This incident will be addressed in our regular post-incident retrospective to ensure we implement measures that prevent similar issues in the future. Thank you for your understanding, and please don’t hesitate to reach out if you have any further questions.

@Jan Kos can you confirm if the metadata issues result in delays in attribute calls from the analytical model? I'm reading this as the LDM or Analytialmodel data results are impacted by this, which generally makes everything slower since loading the metadata is necessary before we target the end-source system for the data to load.

Hi @Steve Fox this is correct. If there is a problem or service degradation with metadata component, generally majority api calls are slower or unavailable (depending on the nature of the problem) including attribute calls from model.