- Level
- confirmed
- Worst impact
- Degraded
- Components
- Analytics
- Regions
- us, us-west-2
- Down Index
- 25of 100
What to do
Check whether you use Front Analytics in us, us-west-2. 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 54m it lasted.
Anything that failed between 2025-06-05 06:45 UTC and 2025-06-05 07:39 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 2
- identified
We are currently processing a backlog of analytics data. This may cause delays in data availability and temporarily skewed metrics. Our team is actively working to resolve the issue.
provider
- resolved
The backlog of analytics data has been fully processed, and metrics are now up to date.
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-f075b81f6c
Is Front still down?
No, this incident was resolved 2025-06-05 07:39 UTC. For Front's live state, see https://down.guide/front.
How long did it last?
54m, from 2025-06-05 06:45 UTC to 2025-06-05 07:39 UTC, by the times Front posted.
What was affected?
Front named Analytics in us, us-west-2.
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.