Skip to main content
Hanko logo

Is Hanko Down?

No — Hanko is up

Reachable from all 8 checked regions

Average response time: 191ms

Last checked · checks run every 6 hours

Official status page: https://status.hanko.io

Hanko uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
131ms
Avg response, 30 days

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

30-day history

13-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: 100.00% uptime, 16 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 47 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 24 checks
Aug 22 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.

fra
91ms
DNS 35ms TCP 1ms TLS 10ms TTFB 80ms
gru
479ms
DNS 434ms TCP 2ms TLS 8ms TTFB 471ms
iad
142ms
DNS 100ms TCP 1ms TLS 8ms TTFB 135ms
jnb
147ms
DNS 92ms TCP 1ms TLS 13ms TTFB 143ms
lax
177ms
DNS 139ms TCP 2ms TLS 7ms TTFB 171ms
lhr
80ms
DNS 26ms TCP 2ms TLS 14ms TTFB 72ms
nrt
322ms
DNS 235ms TCP 1ms TLS 17ms TTFB 315ms
ord
94ms
DNS 42ms TCP 1ms TLS 11ms TTFB 87ms

What Hanko does

Hanko is an authentication platform built around passkeys, offering hosted sign-in and user management that applications integrate instead of building their own. It provides a Passkey API alongside Hanko Cloud, and is also available as open-source components teams can run themselves. Applications that adopt it depend on it for every sign-in, so its availability is the availability of their front door.

What an outage looks like

New sign-ins fail while people already holding a valid session carry on unaffected, so the problem looks like it only affects some users and grows as sessions expire. Passkey registration and authentication calls time out or return errors, and the hosted sign-in interface fails to load. Applications that gate everything behind authentication appear completely down to anyone signing in fresh.

What to do about it

Read status.hanko.io, which reports Hanko Cloud, Passkey API, Hanko Cloud Login and Hanko Docs as separate components and lists open incidents with their own updates. If only Hanko Cloud Login is affected you have lost the administration console rather than end-user authentication. Do not invalidate existing sessions during an incident, since users holding them are the only ones still working, and avoid forcing re-authentication until the Passkey API row recovers.

Is it down for everyone, or just you?

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

Test it yourself

Related services

Auth0 (Okta)
Auth0 (Okta)
Clerk
Clerk
FusionAuth
FusionAuth
Kinde
Kinde

Hanko outage FAQ

Some users can use my app and others cannot. Is Hanko down?
That pattern fits an authentication incident precisely. People who signed in before it started hold a valid session and keep working, while anyone signing in fresh fails. The proportion affected grows as existing sessions expire, so an incident that begins small gets worse without changing. Check the Passkey API row on status.hanko.io rather than looking for something the working users have in common.
I run Hanko myself. Does an incident on the status page affect me?
No. status.hanko.io covers Hanko Cloud and the hosted Passkey API. Hanko is also available as open-source components you can run on your own infrastructure, and such a deployment has its own database, network and hosting to investigate first. An all-clear on the hosted service does not mean a self-hosted instance is healthy.
The Hanko dashboard will not load. Are my users still able to sign in?
Probably, and the two are reported separately. Hanko lists Hanko Cloud Login as a component apart from the Passkey API, so the administration console can be unreachable while end-user authentication continues normally. Treat it as lost administration rather than an outage, and avoid making configuration changes you cannot verify.
Do passkeys still work if Hanko is down?
The passkey stored on a device remains valid, but it has to be verified by the Passkey API for a sign-in to complete, so an incident on that component blocks authentication regardless. Nothing is lost on the user's side and no credential needs recreating. Wait for the component to recover rather than asking users to re-register passkeys, which creates duplicates for no benefit.
How do I tell a Hanko outage from a bug in my integration?
Compare scope and timing. An integration fault usually follows a deploy and affects one environment or one SDK version, while a Hanko incident affects every sign-in at once with no change on your side. status.hanko.io lists open incidents with identified and resolved updates, so an active entry naming the Passkey API confirms the platform side.

How we measure this

  • We request Hanko's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • 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 Hanko 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 Hanko goes down

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

Start Free Monitoring
Free plan available No credit card required