Nitro status history
Current state: operational — “All Systems Operational” per https://status.gonitro.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Nitro incidents last?
From 51 incidents with a vendor-posted start and resolve time. Longest on record: Investigating Issue — 93 min (2026-06-14 09:25 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 (51)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-08 10:25 UTC | Investigating Issue | resolved | none | 1 min |
| 2026-08-30 20:46 UTC | Investigating Issue | resolved | none | 8 min |
| 2026-08-19 08:16 UTC | Investigating Issue | resolved | none | 1 min |
| 2026-07-31 20:59 UTC | Investigating Issue | resolved | none | 5 min |
| 2026-07-31 20:37 UTC | Investigating Issue | resolved | none | 19 min |
| 2026-07-31 11:48 UTC | Investigating Issue | resolved | none | 46 min |
| 2026-07-28 14:34 UTC | Investigating Issue | resolved | none | 3 min |
| 2026-07-20 15:24 UTC | Investigating Issue | resolved | none | 12 min |
| 2026-07-20 13:57 UTC | Investigating Issue | resolved | none | 12 min |
| 2026-07-20 13:47 UTC | Investigating Issue | resolved | none | 2 min |
| 2026-07-20 13:37 UTC | Investigating Issue | resolved | none | 2 min |
| 2026-07-20 13:27 UTC | Investigating Issue | resolved | none | 2 min |
| 2026-07-20 12:57 UTC | Investigating Issue | resolved | none | 2 min |
| 2026-07-14 15:09 UTC | Investigating Issue | resolved | none | 6 min |
| 2026-07-01 05:11 UTC | Investigating Issue | resolved | none | 5 min |
| 2026-06-30 10:44 UTC | Investigating Issue | resolved | none | 29 min |
| 2026-06-29 15:11 UTC | Investigating Issue | resolved | none | 1 h 06 min |
| 2026-06-25 15:42 UTC | Investigating Issue | resolved | none | 1 min |
| 2026-06-25 15:19 UTC | Investigating Issue | resolved | none | 0 min |
| 2026-06-25 15:17 UTC | Investigating Issue | resolved | none | 0 min |
| 2026-06-25 15:15 UTC | Investigating Issue | resolved | none | 0 min |
| 2026-06-25 15:13 UTC | Investigating Issue | resolved | none | 0 min |
| 2026-06-25 15:11 UTC | Investigating Issue | resolved | none | 0 min |
| 2026-06-25 15:09 UTC | Investigating Issue | resolved | none | 0 min |
| 2026-06-25 15:07 UTC | Investigating Issue | resolved | none | 0 min |
| 2026-06-25 15:05 UTC | Investigating Issue | resolved | none | 0 min |
| 2026-06-25 14:59 UTC | Investigating Issue | resolved | none | 4 min |
| 2026-06-14 11:47 UTC | Investigating Issue | resolved | none | 5 min |
| 2026-06-14 11:01 UTC | Investigating Issue | resolved | none | 9 min |
| 2026-06-14 09:25 UTC | Investigating Issue | resolved | none | 1 h 33 min |
| 2026-06-01 15:29 UTC | Investigating Issue | resolved | none | 28 min |
| 2026-06-01 14:47 UTC | Investigating Issue | resolved | none | 30 min |
| 2026-05-28 09:36 UTC | Investigating Issue | resolved | none | 23 min |
| 2026-05-24 11:28 UTC | Investigating Issue | resolved | none | 0 min |
| 2026-05-24 11:17 UTC | Investigating Issue | resolved | none | 9 min |
| 2026-05-24 10:55 UTC | Investigating Issue | resolved | none | 1 min |
| 2026-05-24 10:47 UTC | Investigating Issue | resolved | none | 2 min |
| 2026-05-24 09:54 UTC | Investigating Issue | resolved | none | 52 min |
| 2026-05-24 09:09 UTC | Investigating Issue | resolved | none | 40 min |
| 2026-05-06 16:20 UTC | Investigating Issue | resolved | none | 2 min |
| 2026-04-24 00:29 UTC | Investigating Issue | resolved | none | 14 min |
| 2026-04-23 03:38 UTC | Investigating Issue | resolved | none | 0 min |
| 2026-04-22 18:53 UTC | Investigating Issue | resolved | none | 10 min |
| 2026-04-22 18:36 UTC | Investigating Issue | resolved | none | 13 min |
| 2026-04-19 08:31 UTC | Investigating Issue | resolved | none | 10 min |
| 2026-04-19 08:16 UTC | Investigating Issue | resolved | none | 14 min |
| 2026-04-16 11:14 UTC | Investigating Issue | resolved | none | 17 min |
| 2026-03-31 16:40 UTC | Investigating Issue | resolved | none | 3 min |
| 2026-03-31 14:24 UTC | Investigating Issue | resolved | none | 5 min |
| 2026-03-30 19:10 UTC | Investigating Issue | resolved | none | 1 min |
| 2026-03-26 12:52 UTC | Investigating Issue | resolved | none | 27 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 Nitro with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"nitro"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}