Skip to content

Outage tracker / Afterpay

Is Afterpay down?

I'm having a problem

Operationalchecked moments ago

We reached Afterpay from all 10 regions we check.

As of Oct 5, 2026, 8:16 PM UTC, Afterpay answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured Afterpay (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:16 PM UTC
US-East75 msOperational
US-West366 msOperational
Europe382 msOperational
Asia-Pacific336 msOperational
US-Central259 msOperational
Canada221 msOperational
UK402 msOperational
Southeast Asia439 msOperational
Australia703 msOperational
South America725 msOperational
their status pagetheir claim, not our reading

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

from Afterpay's own status page, checked Oct 5, 2026, 7:58 PM UTC
Our probes and Afterpay's own status page agree: both show Afterpay as reachable right now.

This is Afterpay'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.

Afterpay response time, by region

US-East
347msp95 · 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 328ms2026-09-07 UTC: p95 302ms2026-09-08 UTC: p95 383ms2026-09-09 UTC: p95 366ms2026-09-10 UTC: p95 371ms2026-09-11 UTC: p95 374ms2026-09-12 UTC: p95 400ms2026-09-13 UTC: p95 318ms2026-09-14 UTC: p95 406ms2026-09-15 UTC: p95 460ms2026-09-16 UTC: p95 466ms2026-09-17 UTC: p95 452ms2026-09-18 UTC: p95 498ms2026-09-19 UTC: p95 393ms2026-09-20 UTC: p95 426ms2026-09-21 UTC: p95 390ms2026-09-22 UTC: p95 415ms2026-09-23 UTC: p95 622ms2026-09-24 UTC: p95 701ms2026-09-25 UTC: p95 422ms2026-09-26 UTC: p95 415ms2026-09-27 UTC: p95 500ms2026-09-28 UTC: p95 428ms2026-09-29 UTC: p95 456ms2026-09-30 UTC: p95 482ms2026-10-01 UTC: p95 382ms2026-10-02 UTC: p95 419ms2026-10-03 UTC: p95 459ms2026-10-04 UTC: p95 418ms2026-10-05 UTC: p95 347ms
Sep 6Sep 20Oct 5
US-West
358msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, 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 542ms2026-09-08 UTC: p95 489ms2026-09-09 UTC: p95 464ms2026-09-10 UTC: p95 442ms2026-09-11 UTC: p95 433ms2026-09-12 UTC: p95 420ms2026-09-13 UTC: p95 521ms2026-09-14 UTC: p95 594ms2026-09-15 UTC: p95 633ms2026-09-16 UTC: p95 581ms2026-09-17 UTC: p95 644ms2026-09-18 UTC: p95 555ms2026-09-19 UTC: p95 573ms2026-09-20 UTC: p95 564ms2026-09-21 UTC: p95 699ms2026-09-22 UTC: p95 753ms2026-09-23 UTC: p95 520ms2026-09-24 UTC: p95 515ms2026-09-25 UTC: p95 507ms2026-09-26 UTC: p95 650ms2026-09-27 UTC: p95 324ms2026-09-28 UTC: p95 381ms2026-09-29 UTC: p95 493ms2026-09-30 UTC: p95 579ms2026-10-01 UTC: p95 591ms2026-10-02 UTC: p95 509ms2026-10-03 UTC: p95 544ms2026-10-04 UTC: p95 408ms2026-10-05 UTC: p95 358ms
Sep 6Sep 20Oct 5
Europe
598msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 471ms2026-09-07 UTC: p95 455ms2026-09-08 UTC: p95 491ms2026-09-09 UTC: p95 477ms2026-09-10 UTC: p95 507ms2026-09-11 UTC: p95 527ms2026-09-12 UTC: p95 578ms2026-09-13 UTC: p95 486ms2026-09-14 UTC: p95 564ms2026-09-15 UTC: p95 522ms2026-09-16 UTC: p95 536ms2026-09-17 UTC: p95 598ms2026-09-18 UTC: p95 559ms2026-09-19 UTC: p95 589ms2026-09-20 UTC: p95 550ms2026-09-21 UTC: p95 596ms2026-09-22 UTC: p95 643ms2026-09-23 UTC: p95 477ms2026-09-24 UTC: p95 525ms2026-09-25 UTC: p95 586ms2026-09-26 UTC: p95 627ms2026-09-27 UTC: p95 557ms2026-09-28 UTC: p95 519ms2026-09-29 UTC: p95 533ms2026-09-30 UTC: p95 657ms2026-10-01 UTC: p95 642ms2026-10-02 UTC: p95 639ms2026-10-03 UTC: p95 627ms2026-10-04 UTC: p95 624ms2026-10-05 UTC: p95 598ms
Sep 6Sep 20Oct 5
Asia-Pacific
640msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 644ms2026-09-24 UTC: p95 688ms2026-09-25 UTC: p95 791ms2026-09-26 UTC: p95 786ms2026-09-27 UTC: p95 763ms2026-09-28 UTC: p95 765ms2026-09-29 UTC: p95 894ms2026-09-30 UTC: p95 741ms2026-10-01 UTC: p95 791ms2026-10-02 UTC: p95 671ms2026-10-03 UTC: p95 622ms2026-10-04 UTC: p95 729ms2026-10-05 UTC: p95 640ms
Sep 6Sep 20Oct 5
US-Central
318msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 491ms2026-09-07 UTC: p95 509ms2026-09-08 UTC: p95 545ms2026-09-09 UTC: p95 331ms2026-09-10 UTC: p95 317ms2026-09-11 UTC: p95 376ms2026-09-12 UTC: p95 313ms2026-09-13 UTC: p95 264ms2026-09-14 UTC: p95 331ms2026-09-15 UTC: p95 321ms2026-09-16 UTC: p95 428ms2026-09-17 UTC: p95 415ms2026-09-18 UTC: p95 425ms2026-09-19 UTC: p95 420ms2026-09-20 UTC: p95 433ms2026-09-21 UTC: p95 404ms2026-09-22 UTC: p95 418ms2026-09-23 UTC: p95 538ms2026-09-24 UTC: p95 535ms2026-09-25 UTC: p95 431ms2026-09-26 UTC: p95 460ms2026-09-27 UTC: p95 395ms2026-09-28 UTC: p95 341ms2026-09-29 UTC: p95 352ms2026-09-30 UTC: p95 337ms2026-10-01 UTC: p95 295ms2026-10-02 UTC: p95 235ms2026-10-03 UTC: p95 425ms2026-10-04 UTC: p95 479ms2026-10-05 UTC: p95 318ms
Sep 6Sep 20Oct 5
Canada
556msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 536ms2026-09-07 UTC: p95 401ms2026-09-08 UTC: p95 498ms2026-09-09 UTC: p95 501ms2026-09-10 UTC: p95 518ms2026-09-11 UTC: p95 545ms2026-09-12 UTC: p95 517ms2026-09-13 UTC: p95 516ms2026-09-14 UTC: p95 592ms2026-09-15 UTC: p95 543ms2026-09-16 UTC: p95 586ms2026-09-17 UTC: p95 584ms2026-09-18 UTC: p95 619ms2026-09-19 UTC: p95 565ms2026-09-20 UTC: p95 569ms2026-09-21 UTC: p95 510ms2026-09-22 UTC: p95 668ms2026-09-23 UTC: p95 469ms2026-09-24 UTC: p95 450ms2026-09-25 UTC: p95 458ms2026-09-26 UTC: p95 384ms2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 490ms2026-09-29 UTC: p95 434ms2026-09-30 UTC: p95 371ms2026-10-01 UTC: p95 395ms2026-10-02 UTC: p95 469ms2026-10-03 UTC: p95 344ms2026-10-04 UTC: p95 518ms2026-10-05 UTC: p95 556ms
Sep 6Sep 20Oct 5
UK
699msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 352ms2026-09-07 UTC: p95 332ms2026-09-08 UTC: p95 324ms2026-09-09 UTC: p95 358ms2026-09-10 UTC: p95 385ms2026-09-11 UTC: p95 328ms2026-09-12 UTC: p95 332ms2026-09-13 UTC: p95 325ms2026-09-14 UTC: p95 412ms2026-09-15 UTC: p95 466ms2026-09-16 UTC: p95 339ms2026-09-17 UTC: p95 442ms2026-09-18 UTC: p95 469ms2026-09-19 UTC: p95 376ms2026-09-20 UTC: p95 325ms2026-09-21 UTC: p95 396ms2026-09-22 UTC: p95 461ms2026-09-23 UTC: p95 424ms2026-09-24 UTC: p95 345ms2026-09-25 UTC: p95 521ms2026-09-26 UTC: p95 447ms2026-09-27 UTC: p95 407ms2026-09-28 UTC: p95 543ms2026-09-29 UTC: p95 509ms2026-09-30 UTC: p95 451ms2026-10-01 UTC: p95 463ms2026-10-02 UTC: p95 443ms2026-10-03 UTC: p95 495ms2026-10-04 UTC: p95 747ms2026-10-05 UTC: p95 699ms
Sep 6Sep 20Oct 5
Southeast Asia
1.3sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.8s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5
Australia
996msp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 977ms2026-09-11 UTC: p95 968ms2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 996ms2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 980ms2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 2.1s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 977ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 927ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 913ms2026-10-02 UTC: p95 954ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 996ms
Sep 6Sep 20Oct 5
South America
1.4sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 910ms2026-09-07 UTC: p95 994ms2026-09-08 UTC: p95 940ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 933ms2026-09-11 UTC: p95 852ms2026-09-12 UTC: p95 857ms2026-09-13 UTC: p95 934ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 816ms2026-09-22 UTC: p95 969ms2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 957ms2026-09-25 UTC: p95 964ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 740ms2026-09-28 UTC: p95 808ms2026-09-29 UTC: p95 668ms2026-09-30 UTC: p95 878ms2026-10-01 UTC: p95 998ms2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.4s
Sep 6Sep 20Oct 5

Is it Afterpay, 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 Afterpay -- it cannot diagnose Afterpay's own systems.

What we measured, function by function

Afterpay answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

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

Get told when we measure this

We will tell you when our probes stop reaching Afterpay, and again when they can reach it again. That is our own measurement from ten regions, not Afterpay'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
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 75msstatus code: 401checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Afterpay normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 366msstatus code: 401checked: Oct 5, 2026, 8:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Afterpay normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 259msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Afterpay normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 221msstatus code: 401checked: Oct 5, 2026, 7:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Afterpay normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 725msstatus code: 401checked: Oct 5, 2026, 8:16 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Afterpay normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 382msstatus code: 401checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Afterpay normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 402msstatus code: 401checked: Oct 5, 2026, 8:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Afterpay normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 336msstatus code: 401checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Afterpay normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 439msstatus code: 401checked: Oct 5, 2026, 7:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Afterpay normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 703msstatus code: 401checked: Oct 5, 2026, 8:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Afterpay normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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

These are unverified reports from people using Afterpay, 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 Afterpay yet, which is not evidence that nothing is wrong.

Recent outages

Afterpay NA - Checkout degradation, 19mdeclared on their status page2026-09-23
Support Delay, 1h 28mdeclared on their status page2026-09-03
Service Disruption, 1h 10mdeclared on their status page2026-08-15
In-App Support Chat Unavailable, 46mdeclared on their status page2026-07-20
Degraded Online Checkout Conversion - US, 13mdeclared on their status page2026-07-10
Order reversals affecting Shopify merchants (AU), 3h 53mdeclared on their status page2026-07-03
Increase in payment confirmation errors for Afterpay on Shopify (AU), 33mdeclared on their status page2026-07-02
Degraded performance - Afterpay Card, 9h 15mdeclared 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 Afterpay since August 22, 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 Afterpay covering any window you pick, with our measurements and Afterpay's own claim at the time, side by side.

Full availability history for Afterpay: 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

Afterpay uptime measured by RealUptimeLive, from this page's own readings.
[![Afterpay uptime measured by RealUptime](https://realuptime.io/outages/afterpay/badge.svg?days=30)](https://realuptime.io/outages/afterpay)
<a href="https://realuptime.io/outages/afterpay"><img src="https://realuptime.io/outages/afterpay/badge.svg?days=30" alt="Afterpay 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 Afterpay's SLA implies, from our measurement

At or above your target

We measured none of downtime for Afterpay 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 Afterpay'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: live API
https://global-api.afterpay.com/v2/configuration
secondary
https://www.afterpay.com/
secondary
https://status.afterpay.com/api/v2/status.json
RealUptime is not affiliated with Afterpay; the name identifies what we measured, and nothing here speaks for Afterpay's own team. We send a single web request to Afterpay from 10 regions on our own schedule and time the response. We do not see inside Afterpay's systems, do not use an account or real transaction, and are not the same signal Afterpay's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Afterpay 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. Read the full methodology.