NordLayer status history
Current state: operational — “All Systems Operational” per https://status.nordlayer.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do NordLayer incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: Elevated levels of sign-in errors (MFA) — 4.0 h (2026-06-08 15:57 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 (4)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-06-08 15:57 UTC | Elevated levels of sign-in errors (MFA) | resolved | major | 3 h 58 min |
| 2026-05-08 01:19 UTC | NordLayer CP and SMP, authentication flow outage | resolved | major | 3 h 10 min |
| 2025-11-18 11:39 UTC | Website, Control Panel, SMP and authentication flow being inaccessible | resolved | major | 3 h 21 min |
| 2025-10-27 12:54 UTC | Elevated login and private gateway(s) visibility issues | resolved | major | 2 h 36 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 NordLayer with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"nordlayer"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
