- Level
- confirmed
- Worst impact
- Partial outage
- Components
- US, Canada
- Regions
- ca, us
- Down Index
- 37of 100
What to do
Check whether you use Affirm US, Canada in ca, 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 1h 49m it lasted.
Anything that failed between 2026-06-03 19:00 UTC and 2026-06-03 20:49 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 have identified the cause of the disruption to our Sandbox APIs and we are currently attempting to fix the issue.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
We have implemented a fix and have seen a recovery in the availability of our Sandbox APIs. We will continue to monitor the situation to ensure that our systems are fully operational.
provider
- resolved
Our team has deployed a fix and have seen the errors subside. All services are now functioning as expected.
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-162d00551b
Is Affirm still down?
No, this incident was resolved 2026-06-03 20:49 UTC. For Affirm's live state, see https://down.guide/affirm.
How long did it last?
1h 49m, from 2026-06-03 19:00 UTC to 2026-06-03 20:49 UTC, by the times Affirm posted.
What was affected?
Affirm named US, Canada in ca, 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.