- Level
- confirmed
- Worst impact
- Degraded
- Components
- App
- Regions
- eu, eu-west-1
- Down Index
- 24of 100
What to do
Check whether you use Front App in eu, eu-west-1. 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 30m it lasted.
Anything that failed between 2024-09-23 11:00 UTC and 2024-09-23 11:30 UTC may need a replay.Subscribe to Front's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=front works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Front 3
- investigating
We're receiving some reports of customers having difficulties accessing Front, or delays in sending and receiving messages, in our eu-west-1 region. We're currently investigating.
provider
- identified
We believe we've identified the problem which caused a temporary spike in API errors. We're seeing a return to normal levels, and are working on a root-cause fix.
provider
- resolved
Application performance has appeared to return to normal for eu-west-1 users.
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-e58019e823
Is Front still down?
No, this incident was resolved 2024-09-23 11:30 UTC. For Front's live state, see https://down.guide/front.
How long did it last?
30m, from 2024-09-23 11:00 UTC to 2024-09-23 11:30 UTC, by the times Front posted.
What was affected?
Front named App in eu, eu-west-1.
What caused it?
Front hasn't published a root cause. If it does, it shows here.
Where does this come from?
Front's official status page, https://www.frontstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.