- Level
- confirmed
- Worst impact
- Degraded
- Components
- App
- Regions
- us, us-west-1
- Down Index
- 25of 100
What to do
Check whether you use Front App in us, us-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 41m it lasted.
Anything that failed between 2024-10-29 12:34 UTC and 2024-10-29 13:15 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 are receiving reports of elevated loading times for some customers in the us-west-1 region. We're currently investigating the root cause.
provider
- monitoring
We have put in place mitigations and are seeing a return to normal performance. We're continuing to monitor.
provider
- resolved
This incident has been resolved.
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-5d4c01f548
Is Front still down?
No, this incident was resolved 2024-10-29 13:15 UTC. For Front's live state, see https://down.guide/front.
How long did it last?
41m, from 2024-10-29 12:34 UTC to 2024-10-29 13:15 UTC, by the times Front posted.
What was affected?
Front named App in us, us-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.