User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
clover.com · Money
Is Clover down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → clover.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 195 ms · 7 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:30 | 0 | 0.0 | 897 ms | 0 |
| 03:45 | 0 | 0.0 | 517 ms | 0 |
| 04:00 | 0 | 0.0 | 619 ms | 1 |
| 04:15 | 0 | 0.0 | 719 ms | 0 |
| 04:30 | 0 | 0.0 | 428 ms | 0 |
| 04:45 | 0 | 0.0 | 656 ms | 0 |
| 05:00 | 0 | 0.0 | 1059 ms | 0 |
| 05:15 | 0 | 0.0 | 608 ms | 0 |
| 05:30 | 0 | 0.0 | 409 ms | 0 |
| 05:45 | 0 | 0.0 | 191 ms | 0 |
| 06:00 | 0 | 0.0 | 789 ms | 0 |
| 06:15 | 0 | 0.0 | 388 ms | 0 |
| 06:30 | 0 | 0.0 | 259 ms | 0 |
| 06:45 | 0 | 0.0 | 583 ms | 0 |
| 07:00 | 0 | 0.0 | 686 ms | 0 |
| 07:15 | 0 | 0.0 | 530 ms | 0 |
| 07:30 | 0 | 0.0 | 484 ms | 0 |
| 07:45 | 0 | 0.0 | 305 ms | 0 |
| 08:00 | 0 | 0.0 | 615 ms | 0 |
| 08:15 | 0 | 0.0 | 634 ms | 0 |
| 08:30 | 0 | 0.0 | 422 ms | 0 |
| 08:45 | 0 | 0.0 | 669 ms | 0 |
| 09:00 | 0 | 0.0 | 398 ms | 0 |
| 09:15 | 0 | 0.0 | 299 ms | 0 |
| 09:30 | 0 | 0.0 | 529 ms | 0 |
| 09:45 | 0 | 0.0 | 597 ms | 0 |
| 10:00 | 0 | 0.0 | 409 ms | 0 |
| 10:15 | 0 | 0.0 | 510 ms | 0 |
| 10:30 | 0 | 0.0 | 695 ms | 0 |
| 10:45 | 0 | 0.0 | 433 ms | 0 |
| 11:00 | 0 | 0.0 | 600 ms | 0 |
| 11:15 | 0 | 0.0 | 430 ms | 0 |
| 11:30 | 0 | 0.0 | 409 ms | 0 |
| 11:45 | 0 | 0.0 | 265 ms | 0 |
| 12:00 | 0 | 0.0 | 694 ms | 0 |
| 12:15 | 0 | 0.0 | 544 ms | 0 |
| 12:30 | 0 | 0.0 | 718 ms | 0 |
| 12:45 | 0 | 0.0 | 290 ms | 0 |
| 13:00 | 0 | 0.0 | 385 ms | 0 |
| 13:15 | 0 | 0.0 | 738 ms | 0 |
| 13:30 | 0 | 0.0 | 455 ms | 0 |
| 13:45 | 0 | 0.0 | 353 ms | 0 |
| 14:00 | 0 | 0.0 | 246 ms | 0 |
| 14:15 | 0 | 0.0 | 396 ms | 0 |
| 14:30 | 0 | 0.0 | 462 ms | 0 |
| 14:45 | 0 | 0.0 | 589 ms | 0 |
| 15:00 | 0 | 0.0 | 499 ms | 0 |
| 15:15 | 0 | 0.0 | 195 ms | 0 |
Reliability
98.67%Uptime · 30 days
98.67%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live Clover status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Clover yet. Outages of 10 minutes or more get their own page here.
Having trouble with Clover?
One report per service every 10 minutes from this network. No account.
Follow Clover
Get an email when Clover goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Clover alerts to Slack, Discord or a webhook — free.
Questions
Is Clover down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Clover not working for me but the status is fine. What now?
If Clover is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Clover's side.
How does Damn is it down decide Clover's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is Clover checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.