Skip to main content
Aqua Security logo

Is Aqua Security Down?

No — Aqua Security is up
Aqua Security's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 518 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

Operational
Aqua Security's components, as its status page reports them
ComponentStatus
Aqua Cloud API StatusOperational
Aqua Cloud Console StatusOperational
Cloud Account ScanningOperational
Real-Time Events ServiceOperational
Remediation ServiceOperational
Vulnerability ScanningOperational
Dynamic Threat Analysis (DTA) ScanningOperational
ESEOperational
Supply ChainOperational

FlareWarden checks

cloud.aquasec.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
518 ms
Checked

By region

  • Ashburn reachable, 258 ms
  • Chicago reachable, 133 ms
  • Frankfurt reachable, 286 ms
  • Johannesburg reachable, 1626 ms
  • London reachable, 208 ms
  • Los Angeles reachable, 397 ms
  • São Paulo reachable, 720 ms
  • Tokyo reachable, 522 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn159 ms1 ms6 ms258 ms
Chicago67 ms1 ms6 ms132 ms
Frankfurt22 ms1 ms7 ms285 ms
Johannesburg1000 ms161 ms163 ms1622 ms
London35 ms2 ms6 ms208 ms
Los Angeles73 ms2 ms6 ms397 ms
São Paulo274 ms107 ms113 ms719 ms
Tokyo188 ms100 ms103 ms519 ms
We check that cloud.aquasec.com loads, not every feature behind it. Test it yourself

History

Incidents Aqua Security reported

Since Nov 2, 21 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

21-day clean streak
Oct 24: no data
Oct 25: no data
Oct 26: no data
Oct 27: no data
Oct 28: no data
Oct 29: no data
Oct 30: no data
Oct 31: no data
Nov 1: no data
Nov 2: 100.00% uptime, 16 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Nov 6: 100.00% uptime, 32 checks
Nov 7: 100.00% uptime, 32 checks
Nov 8: 100.00% uptime, 32 checks
Nov 9: 100.00% uptime, 32 checks
Nov 10: 100.00% uptime, 31 checks
Nov 11: 100.00% uptime, 32 checks
Nov 12: 100.00% uptime, 32 checks
Nov 13: 100.00% uptime, 32 checks
Nov 14: 100.00% uptime, 32 checks
Nov 15: 100.00% uptime, 32 checks
Nov 16: 100.00% uptime, 32 checks
Nov 17: 100.00% uptime, 32 checks
Nov 18: 100.00% uptime, 32 checks
Nov 19: 100.00% uptime, 32 checks
Nov 20: 100.00% uptime, 32 checks
Nov 21: 100.00% uptime, 32 checks
Nov 22: 100.00% uptime, 32 checks
Oct 24 Today
No downtime Partial Downtime Not measurable No data

Measured 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 — 21 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.

Test it yourself

Related services

Aqua Security outage FAQ

Does an Aqua console outage stop workload protection?
Not in the incidents Aqua has posted. During the June 30, 2025 sign-in failure in us-east-1, Aqua said the console might be inaccessible but deployed enforcers remained operational and workload protection was not impacted. Watch the Aqua Cloud Console Status row on status.aquasec.com to see when the console is back.
Why are Aqua scans timing out in my CI/CD pipeline?
Check the Supply Chain and Vulnerability Scanning rows first. In the incident Aqua posted on August 31, 2026, a degradation in supply chain vulnerability scanning caused CI/CD pipeline timeouts and timeouts on the Supply Chain page for about two hours until a fix was confirmed. Pipelines that failed in that window need to be run again.
Does a cloud provider outage affect Aqua?
Yes. On October 20, 2025 Aqua reported that an ongoing incident with its public cloud provider made some services unavailable or slower, and login performance was degraded for about 11 hours. Aqua did not name the provider in that incident; its earlier login incidents named the us-east-1 region of its production platform.
What does FlareWarden check for Aqua Security?
It requests cloud.aquasec.com, the Aqua Cloud console, from several regions. That shows whether the console's front end answers. It does not sign in or run a scan, so a scanning or supply chain fault can show on status.aquasec.com while this check stays up. Read both together.

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 403 or 429 means 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
Free plan available No credit card required