Skip to content

Outage tracker / Checkout.com

Is Checkout.com down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Checkout.com from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, Checkout.com 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 Checkout.com (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East495 msOperational
US-West916 msOperational
Europe330 msOperational
Asia-Pacific931 msOperational
US-Central574 msOperational
Canada1001 msOperational
UK390 msOperational
Southeast Asia950 msOperational
Australia1960 msOperational
South America1501 msOperational
their status pagetheir claim, not our reading

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

Checkout.com response time, by region

US-East
993msp95 · 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-06 UTC: p95 770ms2026-09-07 UTC: p95 817ms2026-09-08 UTC: p95 834ms2026-09-09 UTC: p95 796ms2026-09-10 UTC: p95 810ms2026-09-11 UTC: p95 875ms2026-09-12 UTC: p95 771ms2026-09-13 UTC: p95 827ms2026-09-14 UTC: p95 857ms2026-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 993ms
Sep 6Sep 20Oct 5
US-West
936msp95 · 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 1.0s2026-09-07 UTC: p95 936ms2026-09-08 UTC: p95 871ms2026-09-09 UTC: p95 679ms2026-09-10 UTC: p95 748ms2026-09-11 UTC: p95 686ms2026-09-12 UTC: p95 617ms2026-09-13 UTC: p95 973ms2026-09-14 UTC: p95 989ms2026-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 936ms
Sep 6Sep 20Oct 5
Europe
379msp95 · 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 487ms2026-09-07 UTC: p95 413ms2026-09-08 UTC: p95 424ms2026-09-09 UTC: p95 589ms2026-09-10 UTC: p95 609ms2026-09-11 UTC: p95 657ms2026-09-12 UTC: p95 589ms2026-09-13 UTC: p95 594ms2026-09-14 UTC: p95 592ms2026-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 379ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.7sp95 · 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-06 UTC: p95 1.9s2026-09-07 UTC: p95 1.8s2026-09-08 UTC: p95 1.9s2026-09-09 UTC: p95 1.8s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.9s2026-09-13 UTC: p95 1.8s2026-09-14 UTC: p95 1.8s2026-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.7s
Sep 6Sep 20Oct 5
US-Central
951msp95 · 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 881ms2026-09-07 UTC: p95 942ms2026-09-08 UTC: p95 827ms2026-09-09 UTC: p95 817ms2026-09-10 UTC: p95 769ms2026-09-11 UTC: p95 729ms2026-09-12 UTC: p95 757ms2026-09-13 UTC: p95 791ms2026-09-14 UTC: p95 761ms2026-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 951ms
Sep 6Sep 20Oct 5
Canada
1.1sp95 · 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 865ms2026-09-07 UTC: p95 733ms2026-09-08 UTC: p95 621ms2026-09-09 UTC: p95 813ms2026-09-10 UTC: p95 882ms2026-09-11 UTC: p95 752ms2026-09-12 UTC: p95 645ms2026-09-13 UTC: p95 639ms2026-09-14 UTC: p95 675ms2026-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.1s
Sep 6Sep 20Oct 5
UK
443msp95 · 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 303ms2026-09-07 UTC: p95 534ms2026-09-08 UTC: p95 369ms2026-09-09 UTC: p95 390ms2026-09-10 UTC: p95 470ms2026-09-11 UTC: p95 390ms2026-09-12 UTC: p95 542ms2026-09-13 UTC: p95 445ms2026-09-14 UTC: p95 392ms2026-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 443ms
Sep 6Sep 20Oct 5
Southeast Asia
1.1sp95 · 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.5s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.5s2026-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.1s
Sep 6Sep 20Oct 5
Australia
2.1sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 2.2s2026-09-07 UTC: p95 2.0s2026-09-08 UTC: p95 2.3s2026-09-09 UTC: p95 2.9s2026-09-10 UTC: p95 2.7s2026-09-11 UTC: p95 2.3s2026-09-12 UTC: p95 2.5s2026-09-13 UTC: p95 2.6s2026-09-14 UTC: p95 2.2s2026-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.1s
Sep 6Sep 20Oct 5
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-06 UTC: p95 1.9s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 2.1s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.6s2026-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.7s
Sep 6Sep 20Oct 5

Is it Checkout.com, 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 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: 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 Checkout.com go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Checkout.com, and again when they can reach it again. That is our own measurement from ten regions, not Checkout.com'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: 495msstatus code: 401checked: Oct 5, 2026, 8:09 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
      Operationallatency: 916msstatus code: 401checked: Oct 5, 2026, 8:08 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
      Operationallatency: 574msstatus code: 401checked: Oct 5, 2026, 8:15 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
      Operationallatency: 1001msstatus code: 401checked: Oct 5, 2026, 8:10 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
    Operationallatency: 1501msstatus code: 401checked: Oct 5, 2026, 8:03 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 330msstatus code: 401checked: Oct 5, 2026, 8:09 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
      Operationallatency: 390msstatus code: 401checked: Oct 5, 2026, 8:08 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 931msstatus code: 401checked: Oct 5, 2026, 8:11 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
      Operationallatency: 950msstatus code: 401checked: Oct 5, 2026, 7:57 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
      Operationallatency: 1960msstatus code: 401checked: Oct 5, 2026, 8:08 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 outages

No outages on record yet for Checkout.com.

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

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

Checkout.com uptime measured by RealUptimeLive, from this page's own readings.
[![Checkout.com uptime measured by RealUptime](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 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 Checkout.com's SLA implies, from our measurement

At or above your target

We measured none of downtime for Checkout.com 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 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/
RealUptime is not affiliated with Checkout.com; the name identifies what we measured, 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 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.