Fluid Attacks experienced a notice incident on May 20, 2026 affecting Docs, lasting 1h 17m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 20, 2026, 01:37 PM UTC
An issue was found in DOCS. Click for details: https://availability.fluidattacks.com
- identified May 20, 2026, 02:32 PM UTC
We are continuing to work on a fix for this issue.
- resolved May 20, 2026, 02:54 PM UTC
This incident has been resolved.
- postmortem May 21, 2026, 04:40 AM UTC
## Impact On May 20, 2026, users visiting [docs.fluidattacks.com](http://docs.fluidattacks.com/) may have encountered a "Server failed to respond" error for approximately 1.3 hours. The issue was detected internally by our team and resolved within the same window. ## What happened During a routine deployment operation, an outdated version of the documentation service was accidentally restored to production. This older version was missing a configuration component required for the service to start up correctly, which caused the site to become unavailable. Think of it like accidentally restoring an old backup that was missing a key setting the service came back up in an incomplete state and was unable to respond to requests. ## What we changed Service was restored by redeploying the latest stable version of the documentation site, bringing `docs.fluidattacks.com` back online. We then applied a permanent fix to ensure the required configuration is always present and correctly loaded when the service starts, preventing the same failure mode from recurring. ## Going forward We have updated our deployment process to prevent outdated versions from being restored to production. Safeguards are now in place to ensure that only verified, fully configured versions of the service can be deployed. **COMMUNICATION\_FAILURE < INCOMPLETE\_PERSPECTIVE.**