Is Clover down in the US?
Vendor reports no incidentWhat Clover reports
Clover reports no incident on its status page.
As of the last successful poll, 2026-11-07 01:30 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Clover at Nov 7, 2026, 1:40 AM UTC.
Over the last 24 hours we completed 250 checks from Ashburn and San Jose and 243 answered cleanly, 97.20% availability. 1 of those was a measured failure.
Of the 2 other regions we check Clover from, all 2 read checks passing right now.
Email me when Clover reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 7, 2026, 1:40 AM UTC.
Clover from Ashburn and San Jose over the last 30 days
Over the last 30 days, Clover answered our Ashburn probe in 1,176 ms on average, and 1 check in 20 took longer than 1,964 ms.
Over the last 30 days, Clover answered our San Jose probe in 1,590 ms on average, and 1 check in 20 took longer than 2,213 ms.
Ranked by average response time across the 4 cities we check Clover from, Ashburn 1st, San Jose 3rd; Ashburn was fastest at 1,176 ms and Tokyo slowest at 2,623 ms.
From Ashburn and San Jose we ran 1,115 checks of Clover in 6 days, and 1,108 answered cleanly: 99.37% availability.
1 of the 6 days had at least one failed check. The weakest was Nov 6 (UTC), at 97.21% across 251 checks.
In Ashburn local time (EST), Clover was slowest around 8 AM, at 1,435 ms on average over the last 14 days, and quickest around 1 PM, at 887 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Sat, Nov 7 | 16 | 100.00% | 1,062 ms |
| Fri, Nov 6 | 251 | 97.21% | 1,350 ms |
| Thu, Nov 5 | 250 | 100.00% | 1,358 ms |
| Wed, Nov 4 | 250 | 100.00% | 1,215 ms |
| Tue, Nov 3 | 245 | 100.00% | 1,395 ms |
| Mon, Nov 2 | 103 | 100.00% | 1,651 ms |
Clover outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Clover outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Clover from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 96.96% of 99 checks |
| Tokyo | Checks passing | 94.91% of 59 checks |
Other countries we check Clover from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Clover's public endpoints. They are not user reports, and they are not Clover's own status page.
See Clover's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Clover has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
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 serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter