Vendor Status Watch

← all vendors

Hypernode status history

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

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

How long do Hypernode incidents last?

2.4 hmedian incident duration18 measured
15.6 h90th percentile1 in 10 ran longer
3.5 hmedian, major/critical only9 incidents

From 18 incidents with a vendor-posted start and resolve time. Longest on record: Partial service disruption for Brancher, Xgrade, and order processes. — 25.5 h (2026-03-24 10:45 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 (18)

StartedIncidentStatusImpactDuration
2026-08-01 10:05 UTCDNS Service (*.hypernode.io) is showing degraded performanceresolvedminor3 h 00 min
2026-07-09 09:40 UTCDegraded performance when applying changes to Hypernodesresolvedminor57 min
2026-04-14 12:18 UTCInvestigating: DNS Resolution Issues Affecting *.hypernode.ioresolvedminor57 min
2026-04-13 09:26 UTCDegraded performance on our cloud provider location R405resolvedmajor3 h 26 min
2026-03-24 10:45 UTCPartial service disruption for Brancher, Xgrade, and order processes.resolvedmajor25 h 32 min
2026-02-24 09:59 UTCControl Panel Performance Degradationresolvedminor22 h 15 min
2026-02-01 22:09 UTCDegraded reachability with Object Storageresolvedminor37 min
2025-12-16 03:00 UTCBrief Network Instability in Datacenterresolvednone15 min
2025-12-15 07:57 UTCControl Panel (my.hypernode.com) – Degraded Functionalityresolvedmajor9 h 21 min
2025-12-12 12:00 UTCControl Panel (my.hypernode.com) Not Loading Hypernodesresolvedmajor3 h 27 min
2025-12-05 09:06 UTCIdentified Issue – Impact from Cloudflare Outageresolvedmajor12 min
2025-11-18 12:05 UTCCloudflare - Internal server errorresolvedminor2 h 40 min
2025-11-16 16:57 UTCProblems with resolving .hypernode.ioresolvedmajor15 h 37 min
2025-11-05 17:17 UTCDegraded performanceresolvedminor2 h 06 min
2025-10-23 08:35 UTCCloud platform is experiencing degraded performanceresolvedmajor38 min
2025-09-15 14:18 UTCIssue at the Cloud datacenterresolvedmajor1 h 09 min
2025-09-10 11:06 UTCDNS Issues Due to DDoS Attackresolvedmajor4 h 56 min
2025-08-12 16:20 UTCHypernode Emergency Page is down (https://emergency.hypernode.com/)resolvednone13 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 Hypernode with the template

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

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