- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use Frontegg in 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 0m it lasted.
Anything that failed between 2026-06-07 12:39 UTC and 2026-05-31 06:15 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 1
- resolved
During a planned Data Layer Upgrade, an issue occurred that affected a subset of users in the US region for approximately 35 minutes. Affected customers may have experienced degraded performance and errors when performing requests or actions that rely on the Data Layer. All other regions were unaffected.
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-f7f04a8be0
Is Frontegg still down?
No, this incident was resolved 2026-05-31 06:15 UTC. For Frontegg's live state, see https://down.guide/frontegg.
How long did it last?
0m, from 2026-06-07 12:39 UTC to 2026-05-31 06:15 UTC, by the times Frontegg posted.
What was affected?
Frontegg named in 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.