- Level
- confirmed
- Worst impact
- Degraded
- Components
- US
- Regions
- us
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 16m it lasted.
Anything that failed between 2025-11-10 17:11 UTC and 2025-11-10 17:27 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 3
- investigating
We are investigating an increase in latency in our checkout flow. We will provide additional updates as soon as possible.
provider
- monitoring
Our teams have mitigated the impact to latency and availability has returned to normal. We will continue monitoring to ensure our services maintain operational.
provider
- resolved
Our services have maintained operational so this incident is now 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-23b66d6eec
Is Affirm still down?
No, this incident was resolved 2025-11-10 17:27 UTC. For Affirm's live state, see https://down.guide/affirm.
How long did it last?
16m, from 2025-11-10 17:11 UTC to 2025-11-10 17:27 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.