# Service Outage

- Provider: [Frontegg](https://down.guide/frontegg)
- Level: confirmed
- Impact: Major outage
- lasted 5h 36m
- started 2026-07-16 08:06 UTC
- Authentication APIs, Authentication APIs, Authentication APIs +12
- au, ca, eu, us
- id: DWN-e622b4fc96
- Official page: https://stspg.io/z49n4jz68vdv

## Updates from Frontegg
### 2026-07-16 08:06 UTC: 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.

### 2026-07-16 08:06 UTC: investigating
We are currently investigating this issue.

### 2026-07-16 08:56 UTC: 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.

### 2026-07-16 08:58 UTC: 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.

### 2026-07-16 10:08 UTC: 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.

### 2026-07-16 11:33 UTC: identified
We are continuing to work on a fix for this issue.

### 2026-07-16 11:34 UTC: 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.

### 2026-07-16 12:09 UTC: 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.

### 2026-07-16 13:42 UTC: resolved
This incident has been resolved.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).