Vendor Status Watch

← all vendors

Nitro status history

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

3incidents, last 30 days
27incidents, last 90 days
51incidents on record
Incidents per week, last 12 weeks:

How long do Nitro incidents last?

5 minmedian incident duration51 measured
30 min90th percentile1 in 10 ran longer
median, major/critical onlynone posted

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)

StartedIncidentStatusImpactDuration
2026-09-08 10:25 UTCInvestigating Issueresolvednone1 min
2026-08-30 20:46 UTCInvestigating Issueresolvednone8 min
2026-08-19 08:16 UTCInvestigating Issueresolvednone1 min
2026-07-31 20:59 UTCInvestigating Issueresolvednone5 min
2026-07-31 20:37 UTCInvestigating Issueresolvednone19 min
2026-07-31 11:48 UTCInvestigating Issueresolvednone46 min
2026-07-28 14:34 UTCInvestigating Issueresolvednone3 min
2026-07-20 15:24 UTCInvestigating Issueresolvednone12 min
2026-07-20 13:57 UTCInvestigating Issueresolvednone12 min
2026-07-20 13:47 UTCInvestigating Issueresolvednone2 min
2026-07-20 13:37 UTCInvestigating Issueresolvednone2 min
2026-07-20 13:27 UTCInvestigating Issueresolvednone2 min
2026-07-20 12:57 UTCInvestigating Issueresolvednone2 min
2026-07-14 15:09 UTCInvestigating Issueresolvednone6 min
2026-07-01 05:11 UTCInvestigating Issueresolvednone5 min
2026-06-30 10:44 UTCInvestigating Issueresolvednone29 min
2026-06-29 15:11 UTCInvestigating Issueresolvednone1 h 06 min
2026-06-25 15:42 UTCInvestigating Issueresolvednone1 min
2026-06-25 15:19 UTCInvestigating Issueresolvednone0 min
2026-06-25 15:17 UTCInvestigating Issueresolvednone0 min
2026-06-25 15:15 UTCInvestigating Issueresolvednone0 min
2026-06-25 15:13 UTCInvestigating Issueresolvednone0 min
2026-06-25 15:11 UTCInvestigating Issueresolvednone0 min
2026-06-25 15:09 UTCInvestigating Issueresolvednone0 min
2026-06-25 15:07 UTCInvestigating Issueresolvednone0 min
2026-06-25 15:05 UTCInvestigating Issueresolvednone0 min
2026-06-25 14:59 UTCInvestigating Issueresolvednone4 min
2026-06-14 11:47 UTCInvestigating Issueresolvednone5 min
2026-06-14 11:01 UTCInvestigating Issueresolvednone9 min
2026-06-14 09:25 UTCInvestigating Issueresolvednone1 h 33 min
2026-06-01 15:29 UTCInvestigating Issueresolvednone28 min
2026-06-01 14:47 UTCInvestigating Issueresolvednone30 min
2026-05-28 09:36 UTCInvestigating Issueresolvednone23 min
2026-05-24 11:28 UTCInvestigating Issueresolvednone0 min
2026-05-24 11:17 UTCInvestigating Issueresolvednone9 min
2026-05-24 10:55 UTCInvestigating Issueresolvednone1 min
2026-05-24 10:47 UTCInvestigating Issueresolvednone2 min
2026-05-24 09:54 UTCInvestigating Issueresolvednone52 min
2026-05-24 09:09 UTCInvestigating Issueresolvednone40 min
2026-05-06 16:20 UTCInvestigating Issueresolvednone2 min
2026-04-24 00:29 UTCInvestigating Issueresolvednone14 min
2026-04-23 03:38 UTCInvestigating Issueresolvednone0 min
2026-04-22 18:53 UTCInvestigating Issueresolvednone10 min
2026-04-22 18:36 UTCInvestigating Issueresolvednone13 min
2026-04-19 08:31 UTCInvestigating Issueresolvednone10 min
2026-04-19 08:16 UTCInvestigating Issueresolvednone14 min
2026-04-16 11:14 UTCInvestigating Issueresolvednone17 min
2026-03-31 16:40 UTCInvestigating Issueresolvednone3 min
2026-03-31 14:24 UTCInvestigating Issueresolvednone5 min
2026-03-30 19:10 UTCInvestigating Issueresolvednone1 min
2026-03-26 12:52 UTCInvestigating Issueresolvednone27 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
}