Affirm had a major outage on August 10, 2026 that lasted about 22 minutes. StatusBird's own monitoring recorded the first non-operational reading at 08:27 UTC and the first clear reading at 08:49 UTC, a measured window of 22 minutes.
StatusBird checks Affirm every 2 minutes from its own infrastructure, so the timeline below is what an independent observer saw rather than what the vendor's status page said afterwards. Every figure on this page comes from those readings.
When did Affirm go down and when did it recover?
| Event | Observation |
|---|---|
| First non-operational reading | 08:27 UTC, August 10, 2026 |
| Worst status observed | major |
| Recovery observed | 08:49 UTC, August 10, 2026 |
| Duration | 22 minutes |
| Non-operational readings | 11 |
Across the window StatusBird recorded 11 non-operational readings (11 major). Readings are taken every 2 minutes, so the true start and end may sit up to 2 minutes either side of the times above. All times are UTC.
How unusual is this for Affirm?
In the 90 days to August 10, 2026 StatusBird recorded 1 major or critical Affirm incidents, 22 minutes of combined downtime, and 99.98% availability. The average Affirm incident over the same period ran 22 minutes.
This was the only major or critical Affirm incident StatusBird recorded in the 90 days to August 10, 2026, so there is no prior window to compare the shape of it against. The running record is on the Affirm reliability page.
What does a Affirm outage affect?
For online stores using Affirm, checkout payments can fail or hang, which means lost orders for every minute of downtime. The size of the loss depends on when the window landed: 22 minutes across a weekday peak is a different number from the same window overnight, which is why the start time above matters more than the duration alone.
What should a store do when Affirm goes down?
The response that matters happens in the first few minutes, before the vendor has posted anything on its own status page. In order:
- Check whether orders are still being created without a captured payment. Those are the ones that quietly go missing once service returns.
- If you run a second processor, switch the default gateway at checkout rather than leaving customers on a failing one.
- Turn off paid traffic to product and checkout pages. Spend keeps running while conversion is zero.
- Pull the list of orders attempted during the outage window and reconcile authorizations against captures once the processor recovers.
- Confirm the problem is the vendor and not your own integration, by checking whether the failure affects every request or only yours.
- Tell your support team what is happening and what to say, before the tickets arrive rather than after.
- Pause any automated job that retries against the failing service, so a backlog does not fire twice on recovery.
- Write down the start time. Most vendor SLA credit claims require the window, and reconstructing it later from memory rarely works.
The longer version, with the checks specific to this service, is in what to do when Affirm goes down.
Knowing before your customers do
StatusBird detected this incident automatically and alerted affected store owners by SMS, email, and Slack within minutes of the first non-operational reading. It monitors Affirm alongside the other third-party services online stores depend on, and paid plans watch your own storefront as well. Start monitoring free.
Frequently asked questions
How long was the Affirm outage on August 10, 2026?
About 22 minutes. StatusBird observed the first non-operational reading at 08:27 UTC and the first clear reading at 08:49 UTC, for a measured window of 22 minutes.
How bad did it get?
The worst status observed during the window was major. StatusBird normalizes every vendor status page onto the same four levels, operational, degraded, major and critical, so that severity means the same thing across services.
How often does Affirm go down?
In the 90 days to August 10, 2026 StatusBird recorded 1 major or critical Affirm incidents and 99.98% availability, with the average incident running 22 minutes. The current figure is always on the Affirm reliability page.
Was my store affected?
If your store calls Affirm during checkout or fulfillment, requests made between 08:27 UTC and 08:49 UTC on August 10, 2026 are the ones to check. Orders created in that window without a matching downstream record are the usual casualty.
Where does this data come from?
StatusBird checks Affirm every 2 minutes from its own infrastructure and records each reading. These figures are those readings, not a restatement of the vendor's own incident report. The method is documented at statusbird.io/methodology, and live status is at statusbird.io/status/affirm.