- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API and integrations
- Regions
- us, us-west-2
- Down Index
- 37of 100
What to do
Check whether you use Front API and integrations 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 2h 16m it lasted.
Anything that failed between 2024-11-18 20:03 UTC and 2024-11-18 22:18 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 seeing an increase in 5xx errors on our public API in us-west-2 region, which may also affect the ability to send/receive messages on some channels.
provider
- monitoring
The increased rate of errors has subsided as of approximately 10 minutes ago, but we are still determining the root cause.
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-83d2eaae1f
Is Front still down?
No, this incident was resolved 2024-11-18 22:18 UTC. For Front's live state, see https://down.guide/front.
How long did it last?
2h 16m, from 2024-11-18 20:03 UTC to 2024-11-18 22:18 UTC, by the times Front posted.
What was affected?
Front named API and integrations 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.