Skip to content

Outage tracker / Checkout.com

Is Checkout.com down?

I'm having a problem

Checks passingchecked moments ago

Our checks of Checkout.com pass from all 10 regions we check.

As of Oct 14, 2026, 2:13 PM UTC, RealUptime's checks of Checkout.com passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Checkout.com did not fail from two or more distant regions in the 53 days we have checked it (since Aug 22, 2026). This does not show Checkout.com works for users.

our check readinglive · checked Oct 14, 2026, 2:13 PM UTC
US-East838 msChecks passing
US-West844 msChecks passing
Europe122 msChecks passing
Asia-Pacific973 msChecks passing
US-Central704 msChecks passing
Canada466 msChecks passing
UK93 msChecks passing
Southeast Asia1040 msChecks passing
Australia1832 msChecks passing
South America909 msChecks passing
their status pagetheir claim, not our reading

Checkout.com publishes no status feed we can read, so the only reading here is our check reading on the left.

Checkout.com response time, by region

US-East
1.1sp95 · 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-15 UTC: p95 816ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 943ms2026-09-20 UTC: p95 808ms2026-09-21 UTC: p95 788ms2026-09-22 UTC: p95 883ms2026-09-23 UTC: p95 824ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 807ms2026-09-26 UTC: p95 791ms2026-09-27 UTC: p95 858ms2026-09-28 UTC: p95 820ms2026-09-29 UTC: p95 876ms2026-09-30 UTC: p95 844ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 967ms2026-10-03 UTC: p95 938ms2026-10-04 UTC: p95 996ms2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 973ms2026-10-07 UTC: p95 957ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 875ms2026-10-10 UTC: p95 871ms2026-10-11 UTC: p95 868ms2026-10-12 UTC: p95 972ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.1s
Sep 15Sep 29Oct 14
US-West
980msp95 · 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-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 823ms2026-09-27 UTC: p95 887ms2026-09-28 UTC: p95 847ms2026-09-29 UTC: p95 966ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 980ms2026-10-03 UTC: p95 940ms2026-10-04 UTC: p95 872ms2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 931ms2026-10-08 UTC: p95 880ms2026-10-09 UTC: p95 926ms2026-10-10 UTC: p95 977ms2026-10-11 UTC: p95 841ms2026-10-12 UTC: p95 942ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 980ms
Sep 15Sep 29Oct 14
Europe
414msp95 · 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-15 UTC: p95 575ms2026-09-16 UTC: p95 461ms2026-09-17 UTC: p95 413ms2026-09-18 UTC: p95 421ms2026-09-19 UTC: p95 423ms2026-09-20 UTC: p95 427ms2026-09-21 UTC: p95 456ms2026-09-22 UTC: p95 478ms2026-09-23 UTC: p95 455ms2026-09-24 UTC: p95 439ms2026-09-25 UTC: p95 485ms2026-09-26 UTC: p95 464ms2026-09-27 UTC: p95 453ms2026-09-28 UTC: p95 456ms2026-09-29 UTC: p95 460ms2026-09-30 UTC: p95 274ms2026-10-01 UTC: p95 260ms2026-10-02 UTC: p95 252ms2026-10-03 UTC: p95 266ms2026-10-04 UTC: p95 379ms2026-10-05 UTC: p95 387ms2026-10-06 UTC: p95 432ms2026-10-07 UTC: p95 448ms2026-10-08 UTC: p95 417ms2026-10-09 UTC: p95 371ms2026-10-10 UTC: p95 337ms2026-10-11 UTC: p95 415ms2026-10-12 UTC: p95 369ms2026-10-13 UTC: p95 356ms2026-10-14 UTC: p95 414ms
Sep 15Sep 29Oct 14
Asia-Pacific
1.5sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.9s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 2.1s2026-09-25 UTC: p95 2.0s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 2.0s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 1.9s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.8s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.5s
Sep 15Sep 29Oct 14
US-Central
709msp95 · 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-15 UTC: p95 774ms2026-09-16 UTC: p95 720ms2026-09-17 UTC: p95 728ms2026-09-18 UTC: p95 743ms2026-09-19 UTC: p95 760ms2026-09-20 UTC: p95 740ms2026-09-21 UTC: p95 726ms2026-09-22 UTC: p95 728ms2026-09-23 UTC: p95 871ms2026-09-24 UTC: p95 810ms2026-09-25 UTC: p95 828ms2026-09-26 UTC: p95 958ms2026-09-27 UTC: p95 843ms2026-09-28 UTC: p95 849ms2026-09-29 UTC: p95 875ms2026-09-30 UTC: p95 866ms2026-10-01 UTC: p95 786ms2026-10-02 UTC: p95 839ms2026-10-03 UTC: p95 855ms2026-10-04 UTC: p95 734ms2026-10-05 UTC: p95 945ms2026-10-06 UTC: p95 882ms2026-10-07 UTC: p95 820ms2026-10-08 UTC: p95 760ms2026-10-09 UTC: p95 732ms2026-10-10 UTC: p95 752ms2026-10-11 UTC: p95 736ms2026-10-12 UTC: p95 741ms2026-10-13 UTC: p95 798ms2026-10-14 UTC: p95 709ms
Sep 15Sep 29Oct 14
Canada
918msp95 · 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-15 UTC: p95 641ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 882ms2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 961ms2026-09-21 UTC: p95 867ms2026-09-22 UTC: p95 841ms2026-09-23 UTC: p95 878ms2026-09-24 UTC: p95 927ms2026-09-25 UTC: p95 961ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 970ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 972ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 995ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 949ms2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 997ms2026-10-09 UTC: p95 880ms2026-10-10 UTC: p95 859ms2026-10-11 UTC: p95 852ms2026-10-12 UTC: p95 939ms2026-10-13 UTC: p95 904ms2026-10-14 UTC: p95 918ms
Sep 15Sep 29Oct 14
UK
220msp95 · 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-15 UTC: p95 432ms2026-09-16 UTC: p95 442ms2026-09-17 UTC: p95 526ms2026-09-18 UTC: p95 452ms2026-09-19 UTC: p95 471ms2026-09-20 UTC: p95 479ms2026-09-21 UTC: p95 603ms2026-09-22 UTC: p95 595ms2026-09-23 UTC: p95 775ms2026-09-24 UTC: p95 768ms2026-09-25 UTC: p95 751ms2026-09-26 UTC: p95 769ms2026-09-27 UTC: p95 776ms2026-09-28 UTC: p95 730ms2026-09-29 UTC: p95 619ms2026-09-30 UTC: p95 625ms2026-10-01 UTC: p95 450ms2026-10-02 UTC: p95 500ms2026-10-03 UTC: p95 476ms2026-10-04 UTC: p95 463ms2026-10-05 UTC: p95 441ms2026-10-06 UTC: p95 467ms2026-10-07 UTC: p95 301ms2026-10-08 UTC: p95 296ms2026-10-09 UTC: p95 449ms2026-10-10 UTC: p95 382ms2026-10-11 UTC: p95 277ms2026-10-12 UTC: p95 319ms2026-10-13 UTC: p95 243ms2026-10-14 UTC: p95 220ms
Sep 15Sep 29Oct 14
Southeast Asia
1.2sp95 · 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-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.8s2026-09-20 UTC: p95 1.9s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.3s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s
Sep 15Sep 29Oct 14
Australia
2.1sp95 · 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-15 UTC: p95 2.4s2026-09-16 UTC: p95 2.0s2026-09-17 UTC: p95 2.3s2026-09-18 UTC: p95 2.1s2026-09-19 UTC: p95 2.1s2026-09-20 UTC: p95 2.1s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.4s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.2s2026-09-25 UTC: p95 2.2s2026-09-26 UTC: p95 2.4s2026-09-27 UTC: p95 2.3s2026-09-28 UTC: p95 2.3s2026-09-29 UTC: p95 2.3s2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 2.0s2026-10-02 UTC: p95 2.2s2026-10-03 UTC: p95 2.0s2026-10-04 UTC: p95 2.0s2026-10-05 UTC: p95 2.1s2026-10-06 UTC: p95 2.1s2026-10-07 UTC: p95 1.9s2026-10-08 UTC: p95 2.0s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 1.9s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 2.0s2026-10-14 UTC: p95 2.1s
Sep 15Sep 29Oct 14
South America
1.7sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.7s2026-09-16 UTC: p95 3.3s2026-09-17 UTC: p95 2.3s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.8s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 2.1s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 3.4s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 2.1s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.6s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.9s2026-10-09 UTC: p95 1.9s2026-10-10 UTC: p95 2.4s2026-10-11 UTC: p95 1.7s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 2.0s2026-10-14 UTC: p95 1.7s
Sep 15Sep 29Oct 14

Check your own site while you wait on Checkout.com

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 Checkout.com. It cannot diagnose Checkout.com's own systems.

What we measured, function by function

Checkout.com 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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Get an email when our checks of Checkout.com fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Checkout.com fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Checkout.com's official status.

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
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 838msstatus code: 401checked: Oct 14, 2026, 2:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Checkout.com normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 844msstatus code: 401checked: Oct 14, 2026, 2:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Checkout.com normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 704msstatus code: 401checked: Oct 14, 2026, 2:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Checkout.com normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 466msstatus code: 401checked: Oct 14, 2026, 2:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Checkout.com normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 909msstatus code: 401checked: Oct 14, 2026, 2:05 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Checkout.com normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 122msstatus code: 401checked: Oct 14, 2026, 2:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Checkout.com normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 93msstatus code: 401checked: Oct 14, 2026, 2:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Checkout.com normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 973msstatus code: 401checked: Oct 14, 2026, 2:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Checkout.com normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1040msstatus code: 401checked: Oct 14, 2026, 2:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Checkout.com normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1832msstatus code: 401checked: Oct 14, 2026, 1:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Checkout.com 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 Checkout.com, 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 Checkout.com yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Checkout.com.

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

We have been measuring Checkout.com 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 Checkout.com covering any window you pick, with our check readings and Checkout.com's own claim at the time, side by side.

Full check history for Checkout.com: 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

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

The badge shows the share of our checks that passed 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 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 Checkout.com down?", https://realuptime.io/outages/checkout-com. 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.

How our checks compare with Checkout.com's stated SLA

At or above your target

Our checks of Checkout.com failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Checkout.com'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://api.checkout.com/payments/x
secondary
https://www.checkout.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.checkout.com

RealUptime is not affiliated with Checkout.com; the name identifies what we checked, and nothing here speaks for Checkout.com's own team. We send a single web request to Checkout.com from 10 regions on our own schedule and time the response. We do not see inside Checkout.com's systems, do not use an account or real transaction, and are not the same signal Checkout.com's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Checkout.com 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. Read the full methodology.