Rewindex

CompaniesFusionAuthIncidents

FusionAuth: Investigating outage affecting multiple regions

CriticalStatus: resolvedStarted Resolved (1.4 h)3 updatesstspg.io (opens in new tab)
Part of an outage event

AWS outage, Jul 16, 2026 · 27 vendors, 29 incidents

FusionAuth’s incident blames AWS as the cause. (hop 1, posted −14 min vs AWS’s own post)

“…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…”

Swipe sideways to see the whole diagram.

blamed AnthropicAWSposted 08:44 UTCPosted before AWS did2 vendors, 1 blamed AWSFusionAuth, UpstashWithin an hour2 vendors, 2 blamed AWSCoda, GrammarlyAnthropicposted −5 min, did not name AWSGitHub, GitHub Copilot+12 h 21 minFusionAuth (this incident)posted −14 min
blamed AnthropicAWSposted 08:44 UTCPosted before AWS did2 vendors, 1 blamed AWSFusionAuth, UpstashWithin an hour2 vendors, 2 blamed AWSCoda, GrammarlyAnthropicposted −5 min, did not nameAWSGitHub, GitHub Copilot+12 h 21 minFusionAuth (this incident)posted −14 min
FusionAuth is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>posted 08:44 UTC"]:::root
  before["Posted before AWS did<br/>2 vendors, 1 blamed AWS<br/>FusionAuth, Upstash"]:::blames
  root --> before
  h1["Within an hour<br/>2 vendors, 2 blamed AWS<br/>Coda, Grammarly"]:::blames
  root --> h1
  p0["Anthropic<br/>posted −5 min, did not name AWS"]:::timing
  root -.-> p0
  k0["GitHub, GitHub Copilot<br/>+12 h 21 min"]:::hop2
  p0 -->|"blamed Anthropic"| k0
  me["FusionAuth (this incident)<br/>posted −14 min"]:::me
  before --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: FusionAuth Cloud

Timeline of updates

  1. investigating

    We are currently investigating this issue.

  2. investigating

    There is a major operational issue with our cloud provider (AWS). We are looking into workarounds.

  3. resolved

    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 be operating normally.

Changes Rewindex caught on this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

FusionAuth profileRecent FusionAuth incidentsMarkdownJSON