Vendor Status Watch

← all vendors

Aqua status history

Current state: operational — “All Systems Operational” per https://status.aquasec.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
2incidents, last 90 days
6incidents on record
Incidents per week, last 12 weeks:

How long do Aqua incidents last?

2.2 hmedian incident duration5 measured
10.8 h90th percentile1 in 10 ran longer
66 minmedian, major/critical only2 incidents

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)

StartedIncidentStatusImpactDuration
2026-08-31 17:18 UTCAqua Supply Chain Vulnerability Scanning Service Disruption Noticeresolvedcritical2 h 12 min
2026-08-31 13:00 UTCAqua Supply Chain Vulnerability Scanning Service Disruption Noticeresolvedcritical0 min
2025-10-20 15:01 UTCPartial Service Degradationresolvedminor10 h 51 min
2025-10-01 08:00 UTCAqua Image Vulnerability Scaning Service Disruptionresolvedminor0 min
2025-09-08 08:34 UTCLogin to the system is currently unavailableresolvednone2 h 21 min
2025-09-04 19:30 UTCCSPM Scanning Maintenanceresolvedmaintenance7 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
}