- Level
- confirmed
- Worst impact
- Degraded
- Components
- US, Canada, UK
- Regions
- ca, us
- Down Index
- 26of 100
What to do
Check whether you use Affirm US, Canada, UK 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 21m it lasted.
Anything that failed between 2025-11-18 14:07 UTC and 2025-11-18 15:28 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 investigating a sudden drop in all successful traffic to Affirm services in the US, CA and UK
provider
- identified
Our teams have confirmed that the degradation is a result of a widespread issue impacting a core infrastructure provider. We are monitoring the situation closely and will update in the next 30 minutes.
provider
- monitoring
Service is being restored and we expect full resolution shortly.
provider
- resolved
This issue has been resolved and full service has been restored
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-654ea541d2
Is Affirm still down?
No, this incident was resolved 2025-11-18 15:28 UTC. For Affirm's live state, see https://down.guide/affirm.
How long did it last?
1h 21m, from 2025-11-18 14:07 UTC to 2025-11-18 15:28 UTC, by the times Affirm posted.
What was affected?
Affirm named US, Canada, UK 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.