Skip to main content

Is Yubico Down?

No — Yubico is up

Reachable from all 8 checked regions

Average response time: 18ms

Last checked · checks run every 6 hours

Official status page: https://status.yubico.com

Yubico uptime

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

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

30-day history

10-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: 100.00% uptime, 16 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 31 checks
Aug 18: 100.00% uptime, 40 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 24 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
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
19ms
DNS 0ms TCP 1ms TLS 3ms TTFB 10ms
arn
13ms
DNS 0ms TCP 1ms TLS 3ms TTFB 6ms
bom
43ms
DNS 0ms TCP 4ms TLS 7ms TTFB 18ms
cdg
15ms
DNS 0ms TCP 1ms TLS 4ms TTFB 8ms
dfw
12ms
DNS 0ms TCP 0ms TLS 4ms TTFB 8ms
sin
20ms
DNS 0ms TCP 1ms TLS 8ms TTFB 13ms
sjc
20ms
DNS 0ms TCP 1ms TLS 3ms TTFB 9ms
syd
13ms
DNS 0ms TCP 0ms TLS 4ms TTFB 7ms
yyz
16ms
DNS 0ms TCP 0ms TLS 3ms TTFB 8ms

What Yubico does

Yubico makes the YubiKey, a hardware security key used as a second factor or as a passwordless credential. Its online services are separate from the key itself: YubiCloud verifies Yubico OTP codes over the network, while the website and store handle purchases and support. Enterprises also buy YubiKey as a Service, a subscription for distributing keys.

What an outage looks like

Logins that use Yubico OTP fail even though the key lights up and emits a code, because the site verifying that code cannot reach YubiCloud. The failure reads as a rejected credential rather than as a service error, so people assume the key itself has broken. The Yubico store and website can fail separately, affecting purchases rather than authentication.

What to do about it

Check status.yubico.com, which separates YubiCloud OTP verification from the website and the store, since only the first affects logging in. If a site offers another second factor, use it: FIDO2 and WebAuthn sign-in happens between your browser, the key and that site's own server without contacting Yubico, so those logins keep working when YubiCloud does not.

Is it down for everyone, or just you?

If this page says Yubico 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

Yubico outage FAQ

Does a Yubico outage stop my YubiKey from working?
Only for sites using Yubico OTP, which is verified over the network by YubiCloud. FIDO2 and WebAuthn logins are handled between the browser, the key and the site's own server, with no Yubico service involved, so those keep working. Most modern passwordless and second-factor sign-ins use WebAuthn, which makes the practical impact narrower than it first appears.
Why does my key look rejected rather than unavailable?
A site that cannot reach YubiCloud usually cannot tell an unverifiable code apart from a wrong one, so it reports a failed login. The key is fine and is still generating valid codes. This is worth knowing before resetting a key or removing it from an account, since both create far more work than waiting out the incident.
Can I still buy or activate keys during an outage?
Yubico lists its store and its website as components separate from OTP verification, so purchasing can fail while authentication is healthy, and the reverse. Enterprise distribution through YubiKey as a Service is tracked separately again. Read the component that matches what you are trying to do rather than assuming one failure implies the others.
Is it Yubico or the site I am logging into?
If one site rejects the key while others accept it, the fault lies with that site or its identity provider rather than with Yubico. If every OTP-based login fails at once while WebAuthn logins succeed, YubiCloud is the likelier cause. The measurements here and the component list on status.yubico.com separate the two.

How we measure this

  • We request Yubico'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 Yubico 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 Yubico 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