Is Clover Down?

No — Clover is up

Reachable from all 8 checked regions

Average response time: 345ms

Last checked 46 minutes ago · checks run every 6 hours

Official status page: https://status.clover.com

Clover uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

484ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

20-day clean streak

Sep 7 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

452ms

DNS 135ms TCP 6ms TLS 196ms TTFB 452ms

arn

550ms

DNS 207ms TCP 5ms TLS 216ms TTFB 549ms

cdg

390ms

DNS 127ms TCP 2ms TLS 162ms TTFB 390ms

dfw

152ms

DNS 36ms TCP 2ms TLS 67ms TTFB 152ms

ewr

105ms

DNS 52ms TCP 7ms TLS 20ms TTFB 103ms

fra

410ms

DNS 81ms TCP 2ms TLS 205ms TTFB 410ms

gru

510ms

DNS 139ms TCP 2ms TLS 236ms TTFB 510ms

yyz

197ms

DNS 0ms TCP 1ms TLS 50ms TTFB 197ms

What Clover does

Clover sells point of sale systems and card readers for restaurants, retailers and service businesses, with software for payments, tips, refunds, online ordering, invoicing and appointment booking running on top. For a merchant it is the till, the card terminal and often the online store at once, so an outage reaches straight into the checkout line.

What an outage looks like

Card payments decline or hang on the device while cash sales still work. The merchant dashboard will not load, so sales reports and settings are unreachable. Refunds and tip adjustments fail. Batch closeouts do not complete when the business closes for the day. Online orders stop arriving, kitchen printers go quiet, and orders coming in through Uber Eats may not reach the device.

What to do about it

Check status.clover.com and read by region and function. Clover separates North America, Europe and Latin America, and lists Payment Authorization Services, Clover Platform Services, Dashboard, Refunds, Batch Closeouts, Online Ordering, Kitchen Printers and Webhooks as separate rows. If authorization is the affected row, take cash or pause card sales rather than repeatedly running the same card.

Is it down for everyone, or just you?

If this page says Clover is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Clover outage FAQ

Is Clover down or is it my card reader?

Check status.clover.com first. If Payment Authorization Services for your region is operational and a second device in the same store works, the problem is the device or its connection: restart it and check the network. If authorization is degraded, every device will struggle, and retrying cards only creates confusion about which attempts went through.

Will I lose sales that failed during a Clover outage?

A declined or failed card attempt is not a completed sale, so there is nothing to recover. The risk is the opposite: a customer charged more than once because staff retried. Once Clover recovers, check the transaction list in the dashboard for duplicates before refunding or running anything again, and refund any that were captured twice.

Why did my end-of-day closeout not finish?

Clover reports Batch Closeouts and Closeouts as their own components, so they can fail while card payments during the day worked normally. Check those rows on the status page. If they show an incident, wait for recovery and run the closeout again rather than trying repeatedly, and confirm the batch shows as closed in the dashboard afterwards.

Online orders stopped arriving. Is that Clover?

It may be. Clover lists Online Ordering, Online Shopping, Kitchen Printers and Uber Eats as separate components, so online orders can stop while in-store payments work. If one of those rows is degraded, pause online ordering where you can so customers are not paying for food the kitchen never sees, and check for orders that arrived late once it recovers.

Does a Clover outage affect developers and integrations?

Yes, separately. Clover reports the Clover Platform API, Webhooks and the Sandbox as their own components. An integration can stop receiving webhook events or get API errors while merchants' devices keep taking payments. If you build on Clover, check those rows before debugging your own code, and reconcile any events missed during the incident.

How we measure this

We request Clover's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Clover publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Clover goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required