Is Fluid Attacks down?
Last checked 1m agoNo incidents right now.
Fluid Attacks is operational right now. Last checked 1m ago; the most recent incident resolved 6d ago.
Real-time Fluid Attacks status, recent outages, and incident history: pulled directly from Fluid Attacks's official status page at status.fluidattacks.com every 5 minutes. Pingoru tracks 79 Fluid Attacks services and has captured 18 incidents in the last 90 days (99.94% uptime). Get email, Slack, Discord, or webhook alerts the moment Fluid Attacks reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- API
Timeline · 3 updates
- identified · Oct 26, 2026, 11:01 PM UTC
Since 11:35 GMT-05:00, several AI-powered services on our platform are unavailable: the AI agent chat fails with "Failed to connect to chat service", connections to the Fluid Attacks MCP server (https://app.fluidattacks.com/mcp/messages/) from MCP clients such as Claude Desktop, Claude Code and other AI assistants fail with the error "Unexpected content type: text/html", and pull request reviews from the PR Assistant may not complete.
- resolved · Oct 27, 2026, 01:29 AM UTC
This incident has been resolved.
- postmortem · Oct 27, 2026, 08:55 PM UTC
### Postmortem #### Impact Some users experienced an outage of the AI-powered services on our platform: the AI agent chat failed with "Failed to connect to chat service", sessions from external MCP clients could not start, and some pull request reviews from the PR Assistant did not finish processing. The issue started on UTC-5 26-10-26 11:35 and was reactively discovered 5.8 hours \(TTD\) later by a staff member who noticed that the AI agent had stopped responding. The problem was resolved in 1.2 hours \(TTF\), resulting in a total window of exposure of 7 hours \(WOE\). * **AI Agent**: users who opened the AI agent on the platform did not get an answer. * **MCP server**: connections from MCP clients such as Claude Desktop, Claude Code and IDEs failed with "Unexpected content type: text/html". * **PR Assistant**: some pull request review runs never finished processing. * **Scope**: the API, vulnerability management, reports and scans kept working normally, and no data was lost or exposed. #### Cause The services inside our infrastructure locate each other through an internal name resolution service. A change that enabled a new network security layer on some groups of servers modified how name resolution works on those servers[.](https://gitlab.com/fluidattacks/universe/-/merge_requests/118341) On those servers the internal name resolution service ended up forwarding requests to itself, detected the loop, and stopped. Nothing restricted this service to the servers where it works correctly, and since servers are replaced every day, one of its two instances landed on an affected server on October 19 and stopped working. The service kept running on a single instance for a week without any alert. On October 26, an unrelated infrastructure change automatically updated this service to a newer version[.](https://gitlab.com/fluidattacks/universe/-/merge_requests/119719) The restart moved the last healthy instance onto an affected server, leaving no instances available, so every AI service that depends on internal name resolution stopped responding. The new version itself was not the cause; both versions behave the same way on the affected servers. #### Solution The service was restored by restricting the internal name resolution service to servers without the new network layer, after which both instances started correctly. The permanent fix keeps this service on a dedicated group of base servers, the same placement already used by other core components, and raises that group to a minimum of two servers[.](https://gitlab.com/fluidattacks/universe/-/merge_requests/120043) A complementary change fixes the versions of the base components of our infrastructure, so updates are deliberate and reviewed instead of a side effect of unrelated changes[.](https://gitlab.com/fluidattacks/universe/-/merge_requests/120037) The team will also add an alert on the availability of this service. #### Conclusion This incident showed that the change to the network configuration of our servers was validated for the services it targeted but not for the base components of our infrastructure that could run on those servers, so the defect stayed hidden until the daily server rotation exposed it. Without an alert on the availability of name resolution and with component versions not fixed, a routine infrastructure update turned a silent degradation into an outage. Placing base components on dedicated servers, fixing their versions and monitoring their availability would have prevented any user from being affected. **INFRASTRUCTURE\_ERROR < MISSING\_ALERT < INCOMPLETE\_PERSPECTIVE**
Latest: ### Postmortem #### Impact Some users experienced an outage of the AI-powered services on our platform: the AI agent chat failed with "Failed to connect to chat service", sessions …
-
- Platform
Timeline · 2 updates
- identified · Oct 01, 2026, 05:25 AM UTC
An issue was found in PLATFORM. Click for details: https://availability.fluidattacks.tech
- resolved · Oct 01, 2026, 03:58 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Agent
Timeline · 2 updates
- identified · Oct 01, 2026, 05:24 AM UTC
An issue was found in AGENT. Click for details: https://availability.fluidattacks.tech
- resolved · Oct 01, 2026, 03:59 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- API
Timeline · 2 updates
- identified · Oct 01, 2026, 05:23 AM UTC
An issue was found in API. Click for details: https://availability.fluidattacks.tech
- resolved · Oct 01, 2026, 04:00 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- API
Timeline · 2 updates
- identified · Oct 01, 2026, 05:10 AM UTC
An issue was found in API. Click for details: https://availability.fluidattacks.tech
- resolved · Oct 01, 2026, 04:01 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Fluid Attacks outage history
18 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Fluid Attacks outage history →Or sign up free to get alerts when Fluid Attacks breaks · 10 free monitors · No credit card
Incident record
Since April 2026 · Statuspage by Atlassian · 79 components checked every 5 minutesThe longest incident in the last year, Invalid token error in IntelliJ plugin on March 4, 2026, ran for 9 days.
Most affected components, last 12 months
- Platform18
- Agent12
- API7
- Docs5
- Criteria3
Latest incidents
- MCP Server, AI Chat and PR Assistant Unavailable
Since 11:35 GMT-05:00, several AI-powered services on our platform are unavailable: the AI agent chat fails with "Failed to connect to chat service"…
- PLATFORM has failed
An issue was found in PLATFORM. Click for details: https://availability.fluidattacks.tech
- AGENT has failed
An issue was found in AGENT. Click for details: https://availability.fluidattacks.tech
- Started Oct 26, 2026, 11:01 PM UTC · Resolved Oct 27, 2026, 01:29 AM UTC · 2h 28m
- PLATFORM has failed ResolvedStarted Oct 01, 2026, 05:25 AM UTC · Resolved Oct 01, 2026, 03:58 PM UTC · 10h 33m
- AGENT has failed ResolvedStarted Oct 01, 2026, 05:24 AM UTC · Resolved Oct 01, 2026, 03:59 PM UTC · 10h 34m
- API has failed ResolvedStarted Oct 01, 2026, 05:23 AM UTC · Resolved Oct 01, 2026, 04:00 PM UTC · 10h 37m
- API has failed ResolvedStarted Oct 01, 2026, 05:10 AM UTC · Resolved Oct 01, 2026, 04:01 PM UTC · 10h 50m
- AGENT has failed ResolvedStarted Oct 01, 2026, 05:08 AM UTC · Resolved Oct 01, 2026, 04:01 PM UTC · 10h 53m
- API has degraded ResolvedStarted Sep 15, 2026, 04:19 AM UTC · Resolved Sep 15, 2026, 05:03 AM UTC · 44m
- API has degraded ResolvedStarted Sep 15, 2026, 03:49 AM UTC · Resolved Sep 15, 2026, 04:10 AM UTC · 21m