Is FusionAuth Down?

No — FusionAuth is up

FusionAuth's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 127 ms

Right now

The verdict is the worse of these two. How we decide

FusionAuth's status page

status.fusionauth.io · read 4 minutes ago · checked every 3 minutes

Operational

FusionAuth's components, as its status page reports them
Component	Status
FusionAuth Cloud	Operational
FusionAuth Reactor	Operational

Open their status page

FlareWarden checks

fusionauth.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: 127 ms
Checked: 1 hour ago

By region

Ashburn reachable, 85 ms
Chicago reachable, 75 ms
Frankfurt reachable, 160 ms
Johannesburg reachable, 354 ms
London reachable, 37 ms
Los Angeles reachable, 30 ms
São Paulo reachable, 163 ms
Tokyo reachable, 118 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	64 ms	1 ms	5 ms	80 ms
Chicago	61 ms	1 ms	4 ms	71 ms
Frankfurt	145 ms	2 ms	4 ms	156 ms
Johannesburg	158 ms	1 ms	7 ms	350 ms
London	16 ms	2 ms	5 ms	31 ms
Los Angeles	9 ms	2 ms	5 ms	23 ms
São Paulo	140 ms	2 ms	6 ms	159 ms
Tokyo	104 ms	2 ms	3 ms	114 ms

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

History

Incidents FusionAuth reported

Since Oct 22, 15 days · from status.fusionauth.io

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

FusionAuth website availability

Measured by FlareWarden · fusionauth.io

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

Last 30 days

68-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

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

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 17 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. 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 FusionAuth 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 FusionAuth 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. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when FusionAuth goes down

We check FusionAuth 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