FusionAuth

fusionauth.io (opens in new tab)Status page (opens in new tab)

Status page says: Operational since Oct 19
Last 90 days: 0 incidents
Rewrites caught: None so far
Next deprecation: None announced

FusionAuth incidents per day, last 90 days

Select a day to jump to its incidents below.

How FusionAuth reports incidents

Not enough incidents to compare FusionAuth with other vendors yet: a vendor needs 20 incidents in a year and 10 with full update detail (FusionAuth has 3 and 4).

Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors

Dependencies

What FusionAuth relies on and who relies on FusionAuth, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.

FusionAuth depends on

Provider	Evidence	Signal
AWS (eu-central-1)	blamed in 2 incidents; named as hosting in 1; together in 1 outage event “…Investigating outage affecting multiple regions The AWS issue is still ongoing, but we have restored traffic by modifying our routing to avoid the impacted AWS services. All FusionAuth services should…” incident	Strong

Runs in (named in its incidents): AWS eu-central-1 (1).

Outage events: AWS, Jul 16.

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.