Blank screen when accessing the platform

Update timeline

1. identified Jun 25, 2025, 11:11 PM UTC

   A white screen appears with no visible content when attempting to access the platform, preventing normal usage.

2. resolved Jun 25, 2025, 11:12 PM UTC

   The incident has been resolved, and the platform now loads correctly.

3. postmortem Jun 27, 2025, 12:34 AM UTC

   **Impact** At least one user experienced issues accessing the platform. The issue started on UTC-5 25-06-24 15:47 and was proactively discovered 28.8 minutes \(TTD\) later by a staff member who reported through our help desk [\[1\]](https://help.fluidattacks.com/agent/fluid4ttacks/fluid-attacks/tickets/details/944043000039346792) that, upon accessing the platform, only a blank screen was displayed. The problem was resolved in 1.6 hours \(TTF\), resulting in a total window of exposure of 2.1 hours \(WOE\) [\[2\]](https://gitlab.com/fluidattacks/universe/-/issues/16283). **Cause** During the implementation of **Datadog** as a monitoring system, the previous **Coralogix** configurations were retained to avoid gaps in observability. However, both tools were running simultaneously with tracing enabled, which caused a conflict and ultimately corrupted the headers of requests made to the API [\[3\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/79804). **Solution** A rollback of the changes was performed to restore the platform’s stability [\[4\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/79826). **Conclusion** This incident highlighted the lack of manual testing that treats the local environment as production. Since both services operate only in production, the development environment remained unaffected, and the issue was not detected beforehand. Developers need to exercise caution and manually test integrations that are exclusive to the production environment, treating their machines as production when necessary. **INFRASTRUCTURE\_ERROR < INCOMPLETE\_PERSPECTIVE**