- Level
- confirmed
- Worst impact
- Major outage
- Regions
- ca
What to do
Check whether you use Affirm in ca. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 10m it lasted.
Anything that failed between 2024-08-06 15:54 UTC and 2024-08-06 17:04 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 currently investigating the issue.
provider
- identified
We have identified the cause and are continuing to work on a fix for the customer service call center disruption.
provider
- resolved
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-7705bdfb9b
Is Affirm still down?
No, this incident was resolved 2024-08-06 17:04 UTC. For Affirm's live state, see https://down.guide/providers/affirm.
How long did it last?
1h 10m, from 2024-08-06 15:54 UTC to 2024-08-06 17:04 UTC, by the times Affirm posted.
What was affected?
Affirm named in ca.
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.