Is Hanko Down?

No — Hanko is up

Hanko's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 229 ms

Right now

We could not read Hanko's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

hanko.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 229 ms
Checked: 5 hours ago

By region

Chicago reachable, 222 ms
London reachable, 117 ms
Los Angeles reachable, 262 ms
San Jose reachable, 198 ms
Singapore reachable, 152 ms
Sydney reachable, 303 ms
Tokyo reachable, 210 ms
Toronto reachable, 375 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Chicago	117 ms	1 ms	13 ms	219 ms
London	45 ms	3 ms	14 ms	110 ms
Los Angeles	165 ms	2 ms	15 ms	255 ms
San Jose	107 ms	4 ms	17 ms	195 ms
Singapore	82 ms	1 ms	9 ms	148 ms
Sydney	271 ms	1 ms	6 ms	301 ms
Tokyo	173 ms	1 ms	13 ms	208 ms
Toronto	216 ms	1 ms	14 ms	370 ms

We check that hanko.io loads, not every feature behind it. Test it yourself

History

Hanko website availability

Measured by FlareWarden · hanko.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 216ms

Last 30 days

59-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of hanko.io from multiple regions every 6 hours. Hanko's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 59 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Hanko itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Hanko goes down

We check Hanko every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required