- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 27of 100
What to do
Check whether you use Affirm 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 1d 3h it lasted.
Anything that failed between 2026-05-08 00:12 UTC and 2026-05-09 03:20 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 23
- investigating
We are currently experiencing elevated latency across our services leading to timeouts and errors. We are actively investigating the issue.
provider
- identified
We are currently experiencing elevated latency to our services. This has been traced to an issue with our cloud service provider, and our team is actively working toward resolution.
provider
- identified
We continue to experience elevated latency across our services. Error rates have decreased, though response times remain slower than normal. This is due to an issue with our cloud service provider, who is actively working toward a full resolution.
provider
- identified
We continue to experience elevated latency across our services, though error rates remain decreased. Our cloud service provider is actively working toward a full resolution.
provider
- identified
We continue to experience elevated latency across our services, with sporadic increases in error rates throughout the duration of this incident. Our cloud service provider is actively working toward a full resolution.
provider
- monitoring
We are seeing improved latency across our services and response times are trending back toward normal. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.
provider
- monitoring
We experienced a slight increase in errors and latency, which has since subsided. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.
provider
- monitoring
Latency has continued to improve across our services and overall performance has stabilized. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.
provider
- monitoring
Latency has continued to improve across our services and overall performance has stabilized. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.
provider
- monitoring
Latency has continued to improve across our services and overall performance has stabilized. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.
provider
- monitoring
Latency has continued to improve across our services and overall performance has stabilized. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.
provider
- monitoring
Latency and overall performance remain stabilized. We are continuing to monitor while we await final resolution confirmation from our cloud service provider.
provider
- monitoring
We are experiencing an increase in errors and latency. We are continuing to monitor while we await final confirmation of resolution from our cloud service provider.
provider
- monitoring
Latency and overall performance remain stabilized. We are continuing to monitor while our cloud service provider fully resolves the issue.
provider
- monitoring
Latency and overall performance remain stable. We are continuing to monitor while our cloud service provider fully resolves the issue.
provider
- monitoring
Latency and overall performance remain stable. We are continuing to monitor while our cloud service provider fully resolves the issue.
provider
- monitoring
Affirm Latency and overall performance remain stable. We are still awaiting full confirmation from our cloud service provider before declaring the incident resolved.
provider
- monitoring
We continue to receive positive signal from our cloud service provider. Affirm latency and performance remain stable. We are awaiting full confirmation from our cloud service provider before declaring the incident resolved.
provider
- monitoring
Affirm latency and performance remain stable. We are awaiting full confirmation from our cloud service provider before declaring the incident resolved.
provider
- monitoring
We are maintaining a monitoring posture on this incident as we await a statement of permanent resolution from our cloud cloud service provider. Affirm latency and performance remain stable.
provider
- monitoring
We are maintaining a monitoring posture on this incident as we await a statement of permanent resolution from our cloud cloud service provider. Affirm latency and performance remain stable.
provider
- monitoring
Our cloud service provider has notified us that full resolution will require some time to finalize. As Affirm's latency and performance have remained stable throughout the day, we will update on Affirm's status when we receive an all-clear signal from the service provider or we see a regression in service health.
provider
- resolved
Our cloud service provider has confirmed operations are fully restored and we are seeing continued healthy observability on our end. Incident 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-829602286e
Is Affirm still down?
No, this incident was resolved 2026-05-09 03:20 UTC. For Affirm's live state, see https://down.guide/affirm.
How long did it last?
1d 3h, from 2026-05-08 00:12 UTC to 2026-05-09 03:20 UTC, by the times Affirm posted.
What was affected?
Affirm named 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.