Skip to content
OutageDeck

Incident detail

Service Outage

Resolved incidentCritical3 affected services

Timeline window

to

Outage alerts

Get alerted the next time Frontegg breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Frontegg alerts work

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  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.

  2. Investigating

    We are currently investigating this issue.

  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.

  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.

  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.

  6. Identified

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

  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.

  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.

  9. Resolved

    This incident has been resolved.