Live status & reliability report

Keeper status, outages & reliability

Keeper is a password manager and privileged access management platform from Keeper Security, headquartered in Chicago, Illinois.

Data updated Nov 1, 2026 · score recalculated

Over the last 90 days Keeper had 99.97% effective uptime across 1 status page incident, resolving them in 3h 11m on average.

93.6/100Reliability scoreVisit Keeper ↗

Is Keeper down right now?

No, Keeper is up and running.

  • Keeper's status page reports all systems operational. Checked .
  • All 3 Keeper pages we check are responding. Checked .

Official Keeper status page ↗

Uptime (90d)99.97%29m weighted downtime
Incidents (90d)10.2 per 30 days
Major / partial outages0
Avg time to resolve3h 11m
Outages we detected0by our independent probes

90-day uptime

Aug 4, 2026 – Sep 8, 2026: no incidentsSep 9, 2026: 98.00% uptime, 1 incident (Degraded performance)Sep 10, 2026 – Nov 1, 2026: no incidents
90 days ago99.977% average daily uptimeToday
  • No incidents
  • Degraded
  • Partial outage
  • Major outage
  • No data

Key facts about Keeper's reliability

  • Over the past 12 months, Keeper published 9 incidents on its status page, 4 of them partial or major outages.
  • Its longest outage on record in that time was “Resolved: KeeperPAM Connection Errors in US Data Center” on Mar 23, 2026, which lasted 4h 38m.
  • The part of Keeper most often affected was Keeper Web Vault (US) (4 of 9 incidents).
  • Keeper reported 1 incident in the last 90 days, down from 3 in the 90 days before.
  • Incidents most often began on a Wednesday (3 of 9, UTC).
  • Keeper's 90-day uptime of 99.97% is above the average for password managers (99.66%).

Score breakdown

Uptime · 40% weight
98
99.978% effective uptime
Incident frequency · 20% weight
96
0.17 weighted incidents per 30 days
Time to resolve · 20% weight
77
3h 11m average
Transparency · 20% weight
100
No unreported outages detected

How the score is calculated →

Incidents per month

012341 degraded performance incident1DecJan ’261 informational incident1Feb2 partial outage incidents2Mar1 partial outage incident1AprMay1 degraded performance incident1Jun1 partial outage incident1 informational incident2JulAug1 degraded performance incident1SepOctNov
  • Major outage
  • Partial outage
  • Degraded
  • Informational

Response time

Daily average response time of Keeper's public pages, measured by our probes.

Not enough data yet — this chart fills in as our monitoring runs.

Score trend

Daily reliability score (rolling 90-day window).

Not enough data yet — this chart fills in as our monitoring runs.

Keeper incident history (last 90 days)

  • Degraded performanceSep 9, 2026 · resolved in 3h 11m

    SMS 2FA issues with AWS aggregator

    Affected: Keeper iOS, Keeper Web Vault (US), Keeper Android, Keeper Desktop App, Keeper Browser Extensions

Source: Keeper status page · last checked · Subscribe via RSS

Our independent monitoring

We check these public Keeper pages every 5 minutes. An outage is recorded after two consecutive failed checks.

PageLast checkUptime (30d)Avg response
Web vaultUp 100%707 ms
Admin consoleUp 100%403 ms
API pingUp 100%357 ms

How Keeper compares

Most reliable Keeper alternatives →

Keeper status FAQ

Is Keeper down right now?

No, Keeper is up and running. Keeper's status page currently reports all systems operational, and all 3 of the Keeper pages we check every five minutes are responding. This page updates automatically when that changes.

How reliable is Keeper?

Keeper has a reliability score of 93.6 out of 100, ranking #2 of 9 password managers. Over the last 90 days it had 99.97% effective uptime.

How often does Keeper have outages?

Keeper published 1 incident on its status page in the last 90 days (0 partial or major outages) and 9 in the past 12 months.

How long do Keeper outages last?

Keeper resolves incidents in 3h 11m on average. Its longest outage in the past year lasted 4h 38m, on Mar 23, 2026.

Does Keeper have a status page?

Yes. Keeper's official status page is statuspage.keeper.io. We read it every five minutes and keep its full incident history.