Vendor Status Watch

← all vendors

OpenNode status history

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

0incidents, last 30 days
0incidents, last 90 days
3incidents on record

How long do OpenNode incidents last?

35 minmedian incident duration3 measured
3.1 h90th percentile1 in 10 ran longer
27 minmedian, major/critical only1 incident

From 3 incidents with a vendor-posted start and resolve time. Longest on record: OpenNode WebApp and API are back up — 3.1 h (2025-09-23 13:03 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)

StartedIncidentStatusImpactDuration
2026-04-02 21:28 UTCBTC withdrawals temporarily disabledresolvedmajor27 min
2025-09-23 13:03 UTCOpenNode WebApp and API are back upresolvedminor3 h 09 min
2025-09-06 17:00 UTCEmail Sending Issuesresolvednone35 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 OpenNode with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "opennode"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}