- Service Status
- /
- Aqua Security

Is Aqua Security Down?
- Aqua Security's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 407 ms
Right now
The verdict is the worse of these two. How we decide
Aqua Security's status page
status.aquasec.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Aqua Cloud API Status | Operational |
| Aqua Cloud Console Status | Operational |
| Cloud Account Scanning | Operational |
| Real-Time Events Service | Operational |
| Remediation Service | Operational |
| Vulnerability Scanning | Operational |
| Dynamic Threat Analysis (DTA) Scanning | Operational |
| ESE | Operational |
| Supply Chain | Operational |
FlareWarden checks
cloud.aquasec.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 407 ms
- Checked
By region
- Ashburn reachable, 235 ms
- Frankfurt reachable, 444 ms
- Johannesburg reachable, 639 ms
- London reachable, 99 ms
- Los Angeles reachable, 386 ms
- Newark reachable, 176 ms
- São Paulo reachable, 605 ms
- Tokyo reachable, 675 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 204 ms | 1 ms | 5 ms | 235 ms |
| Frankfurt | 67 ms | 2 ms | 6 ms | 444 ms |
| Johannesburg | 121 ms | 162 ms | 165 ms | 639 ms |
| London | 69 ms | 2 ms | 4 ms | 99 ms |
| Los Angeles | 65 ms | 2 ms | 7 ms | 386 ms |
| Newark | 22 ms | 3 ms | 7 ms | 175 ms |
| São Paulo | 157 ms | 112 ms | 114 ms | 605 ms |
| Tokyo | 184 ms | 151 ms | 155 ms | 671 ms |
History
Incidents Aqua Security reported
Since Nov 2, 17 days · from status.aquasec.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Aqua Security website availability
Measured by FlareWarden · cloud.aquasec.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 435ms
Last 30 days
17-day clean streakMeasured by FlareWarden's own checks of cloud.aquasec.com from multiple regions every 6 hours. Aqua Security's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 17 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Aqua Security does
Aqua Security makes a cloud native application security platform. Security and DevOps teams use it to scan container images and code for vulnerabilities, check cloud accounts for misconfigurations, and enforce policy on running workloads through enforcers deployed in their own environments. The Aqua Cloud SaaS console runs at cloud.aquasec.com, and the status page titled Aqua Cloud covers its console, API and scanning services.
What an outage looks like
Signing in to the Aqua console fails, as in us-east-1 on June 30, 2025, or scans slow down. In the incident posted on August 31, 2026, supply chain vulnerability scanning degraded and CI/CD pipelines and the Supply Chain page timed out. Container image scans were partly affected on October 1, 2025, and a cloud provider incident degraded login and several services for about 11 hours on October 20, 2025.
What to do about it
Check status.aquasec.com, which lists the Aqua Cloud console, the API, cloud account scanning, vulnerability scanning, supply chain, remediation and real-time events as separate components. A console outage does not mean protection has stopped: in the June 2025 login incident Aqua said deployed enforcers stayed operational and workload protection was not affected. If CI scans time out, rerun the pipeline once the Supply Chain row is green.
Is it down for everyone, or just you?
If this page says Aqua Security is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Aqua Security outage FAQ
Does an Aqua console outage stop workload protection?
Why are Aqua scans timing out in my CI/CD pipeline?
Does a cloud provider outage affect Aqua?
What does FlareWarden check for Aqua Security?
How we measure this
- We request Aqua Security's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Aqua Security publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Aqua Security itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Aqua Security goes down
We check Aqua Security every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring


