Aviator status history
Current state: operational — “All Systems Operational” per https://status.aviator.co (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Aviator incidents last?
From 3 incidents with a vendor-posted start and resolve time. Longest on record: Web app requests and APIs are degraded — 7.8 h (2026-07-14 18:26 UTC). Excluded, never estimated: nothing. 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 (3)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-11 20:43 UTC | Queue backed up | resolved | critical | 1 h 06 min |
| 2026-07-14 18:26 UTC | Web app requests and APIs are degraded | resolved | minor | 7 h 51 min |
| 2026-05-01 15:30 UTC | Queues backed up | resolved | none | 0 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 Aviator with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"aviator"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}