Skip to content

Outage tracker / Affirm

Is Affirm down?

Short linkrlup.io/down/affirm

I'm having a problem

Operationalchecked 19 minutes ago

We reached Affirm from all 2 regions we check.

As of Oct 5, 2026, 7:57 PM UTC, Affirm answered RealUptime's probes in all 2 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Affirm (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 7:57 PM UTC
US-East164 msOperational
US-West483 msOperational

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 5, 2026, 7:58 PM UTC
Our probes and Affirm's own status page agree: both show Affirm as reachable 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 - BigCommerceOperational
  • AUSOperational
  • 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
276msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 468ms2026-09-07 UTC: p95 288ms2026-09-08 UTC: p95 316ms2026-09-09 UTC: p95 455ms2026-09-10 UTC: p95 420ms2026-09-11 UTC: p95 411ms2026-09-12 UTC: p95 330ms2026-09-13 UTC: p95 344ms2026-09-14 UTC: p95 372ms2026-09-15 UTC: p95 266ms2026-09-16 UTC: p95 267ms2026-09-17 UTC: p95 319ms2026-09-18 UTC: p95 282ms2026-09-19 UTC: p95 322ms2026-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 276ms
Sep 6Sep 20Oct 5
US-West
609msp95 · 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-06 UTC: p95 493ms2026-09-07 UTC: p95 570ms2026-09-08 UTC: p95 504ms2026-09-09 UTC: p95 377ms2026-09-10 UTC: p95 428ms2026-09-11 UTC: p95 618ms2026-09-12 UTC: p95 429ms2026-09-13 UTC: p95 372ms2026-09-14 UTC: p95 420ms2026-09-15 UTC: p95 402ms2026-09-16 UTC: p95 447ms2026-09-17 UTC: p95 427ms2026-09-18 UTC: p95 416ms2026-09-19 UTC: p95 393ms2026-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 609ms
Sep 6Sep 20Oct 5

Is it Affirm, or is it you?

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.

Get an email when we see Affirm go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Affirm, and again when they can reach it again. That is our own measurement from ten regions, not Affirm's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 164msstatus code: 401checked: Oct 5, 2026, 7:57 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
      Operationallatency: 483msstatus code: 401checked: Oct 5, 2026, 7:47 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 outages

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

measured 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 measurements and Affirm's own claim at the time, side by side.

Full availability history for Affirm: 90-day availability by region, month-by-month uptime, and every incident 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 measured by RealUptimeLive, from this page's own readings.
[![Affirm uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Affirm's SLA implies, from our measurement

At or above your target

We measured none of downtime for Affirm over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Affirm's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.affirm.com/api/v2/charges
secondary
https://status.affirm.com/
RealUptime is not affiliated with Affirm; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Affirm serves United States and Canadian shoppers, so we check it from our US regions only. Read the full methodology.

Related services

AdyenAfterpayAlipayBinanceBrex