- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Frontegg. 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 45m it lasted.
Anything that failed between 2023-08-22 09:30 UTC and 2023-08-22 10: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 6
- identified
A maintenance procedure on our DB may result a intermittent 500s in identity flows. We applied a caching mechanism to make sure that no data during the flow will be lost in case of an error. * Note: the issue should not effect active refresh tokens
provider
- identified
The maintenance is still in progress
provider
- identified
The maintenance is still in progress
provider
- identified
The maintenance is still in progress
provider
- monitoring
The maintenance was completed and we are monitoring the results.
provider
- resolved
The maintenance has been successfully completed
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-0aebea9a4c
Is Frontegg still down?
No, this incident was resolved 2023-08-22 10:15 UTC. For Frontegg's live state, see https://down.guide/frontegg.
How long did it last?
45m, from 2023-08-22 09:30 UTC to 2023-08-22 10:15 UTC, by the times Frontegg posted.
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.