Skip to main content
Frontegg

Service Outage

Major outage Lasted 5h 36m · started · Frontegg's page

Level
confirmed
Worst impact
Major outage
Components
Authentication APIs, Authentication APIs, Authentication APIs, Authentication APIs, Authentication APIs, Management APIs, Management APIs, Management APIs, Management APIs, Management APIs, Management Portal, Management Portal, Management Portal, Management Portal, Management Portal
Regions
au, ca, eu, us
Down Index
63of 100

What to do

  • Check whether you use Frontegg Authentication APIs, Authentication APIs, Authentication APIs, Authentication APIs and 11 more in au, ca, eu, us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 5h 36m it lasted.

    Anything that failed between 2026-07-16 08:06 UTC and 2026-07-16 13:42 UTC may need a replay.
  • Subscribe to Frontegg's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=frontegg works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Frontegg 9

  1. identified

    We're currently investigating a service disruption affecting authentication and login across our platform. Our team is actively looking into the cause and working to restore service as quickly as possible. We'll keep you posted.

    provider

  2. investigating

    We are currently investigating this issue.

    provider

  3. identified

    We've identified the cause of the disruption as an ongoing issue with our upstream cloud provider (AWS CloudFront). We are actively working internally as well to try and mitigate this until their service fully restored.

    provider

  4. identified

    Due to the global Cloudfront issue, some of our customers that are using custom domains v2 are still impacted. We are actively working to bypass Cloudfront service and bring those back to normal. We'll keep you posted.

    provider

  5. identified

    Hi all, The Cloudfront issue still persists. However, we have implemented a workaround on our side. We are rolling it out by region. EU and US should be up and running now. We will keep you posted.

    provider

  6. identified

    We are continuing to work on a fix for this issue.

    provider

  7. identified

    Hi all, The Cloudfront issue still persists. However, we have implemented a workaround on our side. We are rolling it out by region. Australia, Canada, and the UK should be up and running now.

    provider

  8. monitoring

    Update on the AWS incident from earlier: Amazon is still experiencing a global operational issue with CloudFront on their end, but we've implemented a workaround to bypass the affected component. All regions are now back up and working normally. We proactively rerouted to avoid the impacted path, so you shouldn't need to do anything on your side. We'll keep an eye on AWS's recovery and let you know if the situation changes. If you notice anything still off, please flag it on our Slack — happy to help.

    provider

  9. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-e622b4fc96

Is Frontegg still down?

No, this incident was resolved 2026-07-16 13:42 UTC. For Frontegg's live state, see https://down.guide/frontegg.

How long did it last?

5h 36m, from 2026-07-16 08:06 UTC to 2026-07-16 13:42 UTC, by the times Frontegg posted.

What was affected?

Frontegg named Authentication APIs, Authentication APIs, Authentication APIs, Authentication APIs and 11 more in au, ca, eu, us.

What caused it?

Frontegg hasn't published a root cause. If it does, it shows here.

Where does this come from?

Frontegg's official status page, https://status.frontegg.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.