Skip to content

Outage tracker / Checkout.com

Is Checkout.com down?

Short linkrlup.io/down/checkout-com

I'm having a problem

Operationalchecked moments ago

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

Functional endpoints verified

No outage recorded in the 10 days we have measured Checkout.com (since Aug 22, 2026).

our independent probeslive · checked Sep 1, 2026, 4:09 AM UTC
US-East815 msOperational
US-West542 msOperational
Europe488 msOperational
Asia-Pacific829 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
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-08-22 UTC: p95 747ms2026-08-23 UTC: p95 683ms2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 905ms2026-08-26 UTC: p95 763ms2026-08-27 UTC: p95 817ms2026-08-28 UTC: p95 998ms2026-08-29 UTC: p95 985ms2026-08-30 UTC: p95 1s2026-08-31 UTC: p95 1.0s2026-09-01 UTC: p95 1.1s
Aug 3Aug 17Sep 1
US-West
680msp95 · 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-08-22 UTC: p95 513ms2026-08-23 UTC: p95 678ms2026-08-24 UTC: p95 947ms2026-08-25 UTC: p95 911ms2026-08-26 UTC: p95 734ms2026-08-27 UTC: p95 877ms2026-08-28 UTC: p95 891ms2026-08-29 UTC: p95 866ms2026-08-30 UTC: p95 954ms2026-08-31 UTC: p95 907ms2026-09-01 UTC: p95 680ms
Aug 3Aug 17Sep 1
Europe
343msp95 · 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-08-22 UTC: p95 240ms2026-08-23 UTC: p95 297ms2026-08-24 UTC: p95 500ms2026-08-25 UTC: p95 464ms2026-08-26 UTC: p95 397ms2026-08-27 UTC: p95 479ms2026-08-28 UTC: p95 623ms2026-08-29 UTC: p95 394ms2026-08-30 UTC: p95 415ms2026-08-31 UTC: p95 377ms2026-09-01 UTC: p95 343ms
Aug 3Aug 17Sep 1
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-08-22 UTC: p95 1.3s2026-08-23 UTC: p95 1.8s2026-08-24 UTC: p95 1.6s2026-08-25 UTC: p95 1.5s2026-08-26 UTC: p95 1.4s2026-08-27 UTC: p95 1.4s2026-08-28 UTC: p95 2.0s2026-08-29 UTC: p95 1.8s2026-08-30 UTC: p95 1.8s2026-08-31 UTC: p95 1.9s2026-09-01 UTC: p95 1.5s
Aug 3Aug 17Sep 1

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: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
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

  • US-East
    Operationallatency: 815msstatus code: 401checked: Sep 1, 2026, 3:59 AM 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: 542msstatus code: 401checked: Sep 1, 2026, 4:09 AM 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.
  • Europe
    Operationallatency: 488msstatus code: 401checked: Sep 1, 2026, 4:05 AM 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.
  • Asia-Pacific
    Operationallatency: 829msstatus code: 401checked: Sep 1, 2026, 4:04 AM 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.
  • US-Central
    Not monitored from this regionCheckout.com is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionCheckout.com is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionCheckout.com is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionCheckout.com is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionCheckout.com is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionCheckout.com 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 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

Tell me when this goes down

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.

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 244h 9m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 14 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 4 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. Checkout.com operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on August 22, 2026 (10 of 14 days so far, 9662 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

AdyenAffirmAfterpayAlipayBinance