← Back to Checkout.com's check readings
We started checking Checkout.com on August 22, 2026, which is 63 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when our checks of Checkout.com fail from two or more distant regions
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Checkout.com's own status page declared. Below it, any public chatter we saw about Checkout.com and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Checkout.com's own status page declared. Three records side by side; none of them changes another.
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Checkout.com's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Checkout.com next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
| Region | Checks passing | Probes recorded |
|---|---|---|
| US-East | 100.00% | 8709 |
| US-West | 100.00% | 8705 |
| Europe | 99.99% | 8632 |
| Asia-Pacific | 99.95% | 8391 |
| US-Central | 100.00% | 3615 |
| Canada | 99.97% | 3614 |
| UK | 100.00% | 3613 |
| Southeast Asia | 97.12% | 3582 |
| Australia | 97.99% | 3577 |
| South America | 95.61% | 3603 |
Monthly summary
Tracking Checkout.com since Aug 22, 2026. In that time our checks failed from two or more distant regions in no probe event. Months before that date are not tracked and carry no figure.
| Month | Uptime by our checks | Probe events | Time failing |
|---|---|---|---|
| Nov 2025 | not tracked | ||
| Dec 2025 | not tracked | ||
| Jan 2026 | not tracked | ||
| Feb 2026 | not tracked | ||
| Mar 2026 | not tracked | ||
| Apr 2026 | not tracked | ||
| May 2026 | not tracked | ||
| Jun 2026 | not tracked | ||
| Jul 2026 | not tracked | ||
| Aug 2026 from Aug 22, 2026 | 100% | 0 | 0 min |
| Sep 2026 | 100% | 0 | 0 min |
| Oct 2026 | 100% | 0 | 0 min |
Uptime by our checks is the share of each month in which no probe event was open for Checkout.com. An event opens only when our checks fail from two or more distant regions, meaning regions on different continents. One that nothing else backs stops counting as an outage after 6 hours, and after 48 hours we treat our check as broken. An event that fails these rules is retracted, kept, and listed on the corrections page. An event that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Checkout.com's own status page contribute nothing to these figures.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime.
Our probe event log
Every probe event for Checkout.com in the last 90 days, or since we started checking it if that is more recent. This list is probe-only: Checkout.com's own declared incidents appear further down this page in their own attributed section, never merged with what our checks show here. User reports live on the live page, in their own labeled block.
Full detail on what a probe does and does not prove is in the methodology page.