- Level
- confirmed
- Worst impact
- Degraded
- Components
- US
- Regions
- us
- Down Index
- 21of 100
What to do
Check whether you use Affirm 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 48m it lasted.
Anything that failed between 2026-08-12 21:12 UTC and 2026-08-12 22:00 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
- identified
We are currently experiencing degraded performance across Affirm services. Our engineering team has identified the root cause and is actively working to implement a fix. We will provide another update as soon as the issue is resolved or more information becomes available.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
A fix has been implemented and we are currently seeing recovery and will continue to monitor system performance closely to ensure full stability.
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-8d932d1bd0
Is Affirm still down?
No, this incident was resolved 2026-08-12 22:00 UTC. For Affirm's live state, see https://down.guide/affirm.
How long did it last?
48m, from 2026-08-12 21:12 UTC to 2026-08-12 22:00 UTC, by the times Affirm posted.
What was affected?
Affirm named 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.