- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 100
What to do
Check whether your product depends on Affirm. 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 6h 58m it lasted.
Anything that failed between 2024-07-03 06:29 UTC and 2024-07-03 13:26 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
Our team is aware of elevated failure rates on authentication due to SMS PIN delivery failures. This appears to be related to carrier network degradation. We believe users are able to retry and successfully authenticate.
provider
- monitoring
SMS failure rates have normalized, and authentication rates are back to normal. Our team is continuing to monitor.
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-9d5c08bfab
Is Affirm still down?
No, this incident was resolved 2024-07-03 13:26 UTC. For Affirm's live state, see https://down.guide/affirm.
How long did it last?
6h 58m, from 2024-07-03 06:29 UTC to 2024-07-03 13:26 UTC, by the times Affirm posted.
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.