Aqua status history
Current state: operational — “All Systems Operational” per https://status.aquasec.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Aqua incidents last?
From 5 incidents with a vendor-posted start and resolve time. Longest on record: Partial Service Degradation — 10.8 h (2025-10-20 15:01 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (6)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-31 17:18 UTC | Aqua Supply Chain Vulnerability Scanning Service Disruption Notice | resolved | critical | 2 h 12 min |
| 2026-08-31 13:00 UTC | Aqua Supply Chain Vulnerability Scanning Service Disruption Notice | resolved | critical | 0 min |
| 2025-10-20 15:01 UTC | Partial Service Degradation | resolved | minor | 10 h 51 min |
| 2025-10-01 08:00 UTC | Aqua Image Vulnerability Scaning Service Disruption | resolved | minor | 0 min |
| 2025-09-08 08:34 UTC | Login to the system is currently unavailable | resolved | none | 2 h 21 min |
| 2025-09-04 19:30 UTC | CSPM Scanning Maintenance | resolved | maintenance | 7 h 55 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Aqua with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"aqua"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}