Skip to main content
FusionAuth logo

Is FusionAuth Down?

No — FusionAuth is up

Reachable from all 8 checked regions

Average response time: 111ms

Last checked · checks run every 6 hours

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

FusionAuth uptime

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

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

30-day history

22-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: 100.00% uptime, 16 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 30 checks
Sep 3: 100.00% uptime, 30 checks
Sep 4: 100.00% uptime, 31 checks
Sep 5: 100.00% uptime, 32 checks
Sep 6: 100.00% uptime, 28 checks
Sep 7: 100.00% uptime, 14 checks
Sep 8: 100.00% uptime, 30 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, 31 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, 31 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 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.

lax
90ms
DNS 72ms TCP 2ms TLS 4ms TTFB 85ms
lhr
37ms
DNS 18ms TCP 2ms TLS 4ms TTFB 31ms
nrt
83ms
DNS 60ms TCP 2ms TLS 7ms TTFB 77ms
ord
121ms
DNS 106ms TCP 1ms TLS 4ms TTFB 116ms
sin
44ms
DNS 22ms TCP 2ms TLS 7ms TTFB 38ms
sjc
136ms
DNS 121ms TCP 1ms TLS 3ms TTFB 131ms
syd
140ms
DNS 121ms TCP 1ms TLS 6ms TTFB 137ms
yyz
240ms
DNS 153ms TCP 8ms TLS 15ms TTFB 219ms

What FusionAuth does

FusionAuth is an authentication and user management platform. It handles login, registration, multi-factor authentication, OAuth and OIDC flows, SAML and user data storage, and can run either as a hosted cloud tenant or on infrastructure you operate yourself. Applications route their whole sign-in path through it, so it sits in front of everything a logged-in user does.

What an outage looks like

Users cannot sign in or register. Existing sessions usually survive until their tokens expire, so anything that refreshes a token fails first and the impact grows over the following minutes rather than arriving all at once. Because FusionAuth can be self-hosted, an incident affecting the hosted service does not necessarily touch a deployment you run yourself.

What to do about it

Check status.fusionauth.io, which reports FusionAuth Cloud and FusionAuth Reactor as separate components. If you self-host, confirm the problem is yours before blaming the vendor, because your own instance, database and network are the more likely cause and are not covered by the Cloud row. Avoid forcing a mass sign-out during an incident, since every affected user then needs the login path that is failing.

Is it down for everyone, or just you?

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

FusionAuth outage FAQ

I self-host FusionAuth. Does a FusionAuth outage affect me?
Often not. The Cloud component on status.fusionauth.io covers FusionAuth's hosted service, not an instance running on your own servers. If your self-hosted deployment is failing while the status page is green, look at your instance, its database and the network in front of it first. That is where self-hosted failures almost always originate.
Our users are still logged in. Is FusionAuth really down?
Both can be true at once. Issued tokens stay valid until they expire, so people already signed in keep working while nobody new can authenticate. The visible impact grows as tokens age out and refresh attempts start failing. Judge by whether new sign-ins succeed, not by whether current sessions are still active.
Can new registrations fail while existing logins work?
Yes. Registration, login and token refresh exercise different paths, so a partial incident can block account creation while returning users authenticate normally. If sign-up is failing in particular, check status.fusionauth.io and then test a login with an existing account to establish how wide the problem actually is before escalating.
Is user data lost during a FusionAuth outage?
An authentication outage is normally an availability problem rather than a data one, and stored user records are not expected to be affected. The safest approach is still to pause bulk user imports or migrations until the incident is resolved, then verify counts. Registrations attempted while sign-up was failing should be treated as unconfirmed until checked.
How do I tell whether it is FusionAuth or my application?
Check status.fusionauth.io first, then call the authentication endpoint directly rather than going through your app. If the endpoint responds and your application still fails, the fault is in your integration, your redirect configuration or your network path. This is a useful test for self-hosted deployments, where the status page cannot tell you anything about your own instance.

How we measure this

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