Skip to content

Outage tracker / Affirm

Is Affirm down?

I'm having a problem

Vendor reports no incidentWhat Affirm reports

Affirm reports no incident on its status page.

As of the last successful poll, 2026-10-19 18:24 UTC.

Affirm's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Partially degradedchecked 7 minutes ago

Affirm is answering our probes, but running at least 5.4x its 7-day median from US-East. The rest of the regions we check answered at their usual speed.

As of Oct 19, 2026, 6:19 PM UTC, RealUptime's checks of Affirm passed in all 2 regions that returned a reading.

Front-door and live API checks

This reading is from our two US regions.

our check readinglive · checked Oct 19, 2026, 6:19 PM UTC
US-East1048 msDegraded
US-West219 msChecks passing

Affirm serves United States and Canadian shoppers, so we check it from our US regions only.

their status pagetheir claim, not our reading

Affirm reports: All systems operational (“All Systems Operational”)

from Affirm's own status page, checked Oct 19, 2026, 6:19 PM UTC
Affirm's own status page shows no incident, and our checks of Affirm pass right now.

Affirm's own component breakdown, as they publish it

  • AUS - Shop Pay InstallmentsOperational
  • CA - Shopify Payments AppOperational
  • UK - Shop Pay InstallmentsOperational
  • USOperational
  • USOperational
  • USOperational
  • USOperational
  • USOperational
  • USOperational
  • USOperational
  • USOperational
  • USOperational
  • USOperational
  • USOperational
  • US - Shopify Payments AppOperational
  • CA - Shop Pay InstallmentsOperational
  • CanadaOperational
  • CanadaOperational
  • CanadaOperational
  • CanadaOperational
  • CanadaOperational
  • CanadaOperational
  • CanadaOperational
  • CanadaOperational
  • CanadaOperational
  • CanadaOperational
  • CanadaOperational
  • US - Shop Pay InstallmentsOperational
  • UKOperational
  • UKOperational
  • UKOperational
  • UKOperational
  • UKOperational
  • UKOperational
  • UKOperational
  • UKOperational
  • UKOperational
  • UKOperational
  • UKOperational
  • US - AdyenOperational
  • AUSOperational
  • US - BigCommerceOperational
  • US - WooCommerceOperational
  • US - WixOperational
  • US - OtherOperational

These are Affirm's components, named and scored by Affirm. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Affirm's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Affirm response time, by region

US-East
1.2sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 249ms2026-09-21 UTC: p95 420ms2026-09-22 UTC: p95 466ms2026-09-23 UTC: p95 416ms2026-09-24 UTC: p95 249ms2026-09-25 UTC: p95 339ms2026-09-26 UTC: p95 378ms2026-09-27 UTC: p95 377ms2026-09-28 UTC: p95 473ms2026-09-29 UTC: p95 304ms2026-09-30 UTC: p95 263ms2026-10-01 UTC: p95 278ms2026-10-02 UTC: p95 276ms2026-10-03 UTC: p95 759ms2026-10-04 UTC: p95 300ms2026-10-05 UTC: p95 273ms2026-10-06 UTC: p95 357ms2026-10-07 UTC: p95 316ms2026-10-08 UTC: p95 523ms2026-10-09 UTC: p95 388ms2026-10-10 UTC: p95 273ms2026-10-11 UTC: p95 283ms2026-10-12 UTC: p95 298ms2026-10-13 UTC: p95 313ms2026-10-14 UTC: p95 286ms2026-10-15 UTC: p95 274ms2026-10-16 UTC: p95 426ms2026-10-17 UTC: p95 288ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
US-West
660msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 456ms2026-09-21 UTC: p95 407ms2026-09-22 UTC: p95 476ms2026-09-23 UTC: p95 486ms2026-09-24 UTC: p95 512ms2026-09-25 UTC: p95 542ms2026-09-26 UTC: p95 744ms2026-09-27 UTC: p95 424ms2026-09-28 UTC: p95 567ms2026-09-29 UTC: p95 551ms2026-09-30 UTC: p95 517ms2026-10-01 UTC: p95 741ms2026-10-02 UTC: p95 895ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 753ms2026-10-05 UTC: p95 619ms2026-10-06 UTC: p95 652ms2026-10-07 UTC: p95 812ms2026-10-08 UTC: p95 489ms2026-10-09 UTC: p95 684ms2026-10-10 UTC: p95 481ms2026-10-11 UTC: p95 449ms2026-10-12 UTC: p95 488ms2026-10-13 UTC: p95 557ms2026-10-14 UTC: p95 485ms2026-10-15 UTC: p95 504ms2026-10-16 UTC: p95 500ms2026-10-17 UTC: p95 564ms2026-10-18 UTC: p95 643ms2026-10-19 UTC: p95 660ms
Sep 20Oct 4Oct 19

Check your own site while you wait on Affirm

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Affirm. It cannot diagnose Affirm's own systems.

Email me when Affirm reports an incident on its status page, and again when it reports it resolved.

Get an email when Affirm reports an incident

Email me when Affirm reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Affirm's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    DegradedUS-East, US-West, US-Central, Canada
    • US-East
      Degradedlatency: 1048msstatus code: 401checked: Oct 19, 2026, 6:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Affirm normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 219msstatus code: 401checked: Oct 19, 2026, 6:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Affirm normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionAffirm is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionAffirm is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionAffirm is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Not monitored from this regionAffirm is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • UK
      Not monitored from this regionAffirm is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Not monitored from this regionAffirm is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Southeast Asia
      Not monitored from this regionAffirm is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionAffirm is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Affirm, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Affirm yet, which is not evidence that nothing is wrong.

Recent probe events

Affirm Mobile Application Payment Method Degradation for CA Users, 1h 26mdeclared on their status page2026-09-29
Affirm Services Degradation, 48mdeclared on their status page2026-08-12
Checkout Degradation, 29mdeclared on their status page2026-06-22
Sandbox checkout confirm_loan failures, 1h 22mdeclared on their status page2026-06-17
CA Checkout Degradation, 52mdeclared on their status page2026-06-10
Checkout Degradation, 1h 35mdeclared on their status page2026-06-04
Degradation on Sandbox APIs, 1h 49mdeclared on their status page2026-06-03
Elevated latency across our services, 27h 8mdeclared on their status page2026-05-08

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Affirm since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Affirm covering any window you pick, with our check readings and Affirm's own claim at the time, side by side.

Full check history for Affirm: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Affirm uptime by RealUptime's checksLive, from this page's own readings.
[![Affirm uptime by RealUptime's checks](https://realuptime.io/outages/affirm/badge.svg?days=30)](https://realuptime.io/outages/affirm)
<a href="https://realuptime.io/outages/affirm"><img src="https://realuptime.io/outages/affirm/badge.svg?days=30" alt="Affirm uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Affirm down?", https://realuptime.io/outages/affirm. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional
https://api.affirm.com/api/v2/charges
secondary
https://status.affirm.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.affirm.com

RealUptime is not affiliated with Affirm; the name identifies what we checked, and nothing here speaks for Affirm's own team. We send a single web request to Affirm from 2 regions on our own schedule and time the response. We do not see inside Affirm's systems, do not use an account or real transaction, and are not the same signal Affirm's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Affirm is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Affirm serves United States and Canadian shoppers, so we check it from our US regions only. Read the full methodology.