Skip to content

Outage tracker

NordPass: incident history

The last 24 hours in detail, NordPass's declared incident record, and our regional check results beside it.

← Back to NordPass's check readings

We started checking NordPass on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when NordPass reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is NordPass's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what NordPass's own status page declared. Below it, any public chatter we saw about NordPass and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what NordPass's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about NordPass in the last 24 hours, which is not evidence that nothing is wrong.
NordPass's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is NordPass's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention NordPass next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East92.17%447
US-West91.86%344
Europe90.76%314
Asia-Pacific91.15%192

Their declared record

NordPass's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

NordPass website connection issuesAll systems operational
Oct 27, 2026, 1:07 PM UTC to Oct 27, 2026, 3:33 PM UTC (2h 27m)resolved
their latest update (Oct 27, 2026, 3:33 PM UTC): This incident has been resolved and NordPass should be operating as usual.
Temporary service disruptionAll systems operational
Oct 21, 2026, 12:45 PM UTC to Oct 22, 2026, 9:47 AM UTC (21h 2m)resolved
their latest update (Oct 22, 2026, 9:47 AM UTC): The issue has been resolved and NordPass is operating as usual.
Reduced vault performanceMinor incident
Sep 16, 2026, 6:11 PM UTC to Sep 17, 2026, 5:03 AM UTC (10h 52m)resolved
their latest update (Sep 17, 2026, 5:03 AM UTC): Resolved.
Degraded authorization servers performanceMinor incident
Aug 31, 2026, 11:14 AM UTC to Aug 31, 2026, 11:32 AM UTC (18 min)resolved
their latest update (Aug 31, 2026, 11:32 AM UTC): This issue has been resolved.
Temporary login issuesMinor incident
Aug 27, 2026, 5:31 PM UTC to Aug 27, 2026, 6:41 PM UTC (1h 10m)resolved
their latest update (Aug 27, 2026, 6:41 PM UTC): This issue has been resolved. We apologize for any inconvenience.
Users may be having issues logging inAll systems operational
Jun 17, 2026, 1:22 PM UTC to Jun 17, 2026, 1:38 PM UTC (16 min)resolved
their latest update (Jun 17, 2026, 1:38 PM UTC): This incident has been resolved.
Login issue under investigationMinor incident
Jun 15, 2026, 10:03 AM UTC to Jun 15, 2026, 1:46 PM UTC (3h 43m)resolved
their latest update (Jun 15, 2026, 1:46 PM UTC): This incident has been resolved.
Users may be having issues logging inMinor incident
Apr 28, 2026, 1:41 PM UTC to Apr 28, 2026, 2:55 PM UTC (1h 14m)resolved
their latest update (Apr 28, 2026, 2:55 PM UTC): We’ve implemented the fix and the issue has been resolved.
Android users may be unable to log in at this timeMinor incident
Apr 28, 2026, 7:20 AM UTC to Apr 28, 2026, 8:30 AM UTC (1h 10m)resolved
their latest update (Apr 28, 2026, 8:30 AM UTC): This incident has been resolved.
Degraded performance affecting admin functionality and public APIsMinor incident
Apr 16, 2026, 6:21 AM UTC to Apr 16, 2026, 8:03 AM UTC (1h 42m)resolved
their latest update (Apr 16, 2026, 8:03 AM UTC): This incident has been resolved.

Showing the 10 most recent of 21 incidents NordPass has declared in the history we hold.

These entries are NordPass's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

NordPass's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.