Is Keeper Down?

No — Keeper is up

Reachable from all 8 checked regions

Average response time: 641ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://statuspage.keeper.io

Keeper uptime

99.46%

Last 7 days

—

Last 30 days

—

Last 90 days

—

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 6 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

512ms

DNS 0ms TCP 93ms TLS 94ms TTFB 418ms

arn

861ms

DNS 0ms TCP 144ms TLS 143ms TTFB 735ms

lhr

430ms

DNS 0ms TCP 81ms TLS 82ms TTFB 348ms

nrt

859ms

DNS 0ms TCP 165ms TLS 166ms TTFB 694ms

ord

144ms

DNS 0ms TCP 22ms TLS 23ms TTFB 121ms

sin

1151ms

DNS 0ms TCP 226ms TLS 226ms TTFB 925ms

sjc

375ms

DNS 0ms TCP 68ms TLS 69ms TTFB 306ms

syd

1081ms

DNS 0ms TCP 211ms TLS 211ms TTFB 870ms

yyz

149ms

DNS 0ms TCP 19ms TLS 19ms TTFB 111ms

What Keeper does

Keeper Security stores passwords, passkeys and secrets for individuals and enterprises, and extends into privileged access management, secrets management for applications, and remote browser isolation. Administrators provision users through SSO and SCIM. Because credentials sit behind it, a Keeper problem blocks sign-in to everything else a person needs, which is what makes vault availability worth watching.

What an outage looks like

The web vault will not open or hangs after login. Browser extensions and the iOS and Android apps stop autofilling. SSO Connect fails, so staff cannot authenticate at all. SCIM provisioning with Azure stops creating accounts. The Admin Console will not load for administrators. Keeper reports vaults per region, so EU or AU users can be affected while US users are not.

What to do about it

statuspage.keeper.io separates the web vault by region (US, EU, AU, CA, JP and GovCloud) from the mobile apps, Admin Console, SSO Connect and SCIM provisioning, so check the region your organisation is on. Do not reset master passwords or rotate SSO configuration during an incident; a failed vault load is rarely an account problem, and the change outlives the outage.

Is it down for everyone, or just you?

If this page says Keeper is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Keeper outage FAQ

I cannot open my vault. Is my account locked?

Probably not. A vault that hangs or errors during a platform incident looks identical to an account problem, which is why the first move is the status page rather than the account recovery flow. Resetting a master password or re-enrolling two-factor mid-incident makes a lasting change to fix a temporary fault, and can lock you out further.

Is Keeper down everywhere or just my region?

Often just one region. Keeper runs separate web vaults for the US, EU, AU, CA, JP and GovCloud and reports each as its own component, so European users can be blocked while US colleagues work normally. Check which data centre your organisation was provisioned in; administrators can confirm it, and it explains why colleagues report different experiences.

Can staff sign in to other systems if Keeper SSO Connect fails?

Not through Keeper. SSO Connect sits in the authentication path, so when it fails users cannot complete sign-in to anything routed through it, even though those applications are themselves healthy. This is the argument for keeping a small number of break-glass credentials outside the password manager, stored securely offline and tested before they are needed.

Does an outage affect the browser extension and mobile apps too?

They are reported separately. Keeper lists Keeper iOS, Keeper Android, the Admin Console and the regional web vaults as distinct components, so the mobile app can work while the web vault does not, or the reverse. If autofill stops in the browser, check the web vault directly before assuming the whole service is unavailable.

How we measure this

We request Keeper's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Keeper publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Keeper goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required