- Level
- confirmed
- Worst impact
- Degraded
- Components
- US, US
- Regions
- us
- Down Index
- 20of 100
What to do
Check whether you use Affirm US, US in us. 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 36m it lasted.
Anything that failed between 2024-08-30 21:34 UTC and 2024-08-30 22:11 UTC may need a replay.Subscribe to Affirm's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=affirm works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Affirm 4
- investigating
We are currently experiencing elevated level of errors that are affecting our Checkout Services in the US and we are investigating the issue. We will provide additional updates as we know more.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
We have seen the affected services recover. We will continue to monitor the situation to ensure that degradation does not resume.
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-1d7ebe1345
Is Affirm still down?
No, this incident was resolved 2024-08-30 22:11 UTC. For Affirm's live state, see https://down.guide/affirm.
How long did it last?
36m, from 2024-08-30 21:34 UTC to 2024-08-30 22:11 UTC, by the times Affirm posted.
What was affected?
Affirm named US, US in us.
What caused it?
Affirm hasn't published a root cause. If it does, it shows here.
Where does this come from?
Affirm's official status page, https://status.affirm.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.