Skip to content

Outage tracker / Clover

Is Clover down?

Short linkrlup.io/down/clover-pos

I'm having a problem

Vendor reports no incidentWhat Clover reports

Clover reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:51 UTC.

Clover's status page

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 passingchecked 2 minutes ago

Our checks of Clover pass from all 4 regions we check.

As of Nov 5, 2026, 3:58 PM UTC, RealUptime's checks of Clover passed in all 4 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:58 PM UTC
US-East1219 msChecks passing
US-West1807 msChecks passing
Europe1906 msChecks passing
Asia-Pacific3215 msChecks passing
their status pagetheir claim, not our reading

Clover reports: All systems operational (“All Systems Operational”)

from Clover's own status page, checked Nov 5, 2026, 3:32 PM UTC
Clover's own status page shows no incident, and our checks of Clover pass right now.

Clover's own component breakdown, as they publish it

  • Clover Platform APIOperational
  • European - Auth ServicesOperational
  • Latin America - Clover Platform ServiceOperational
  • North America - Payment Authorization ServicesOperational
  • Payment Authorization ServicesOperational
  • Payment Authorization ServicesOperational
  • Payment Authorization ServicesOperational
  • Clover Platform ServicesOperational
  • Clover Platform ServicesOperational
  • Clover Platform ServicesOperational
  • DashboardOperational
  • DashboardOperational
  • European - COS ServicesOperational
  • North America - Clover Platform ServicesOperational
  • Clover GOOperational
  • Clover GOOperational
  • Clover GOOperational
  • DashboardOperational
  • WebhooksOperational
  • Cloud Pay DisplayOperational
  • Clover GOOperational
  • DashboardOperational
  • DashboardOperational
  • DashboardOperational
  • SandboxOperational
  • Cloud Pay DisplayOperational
  • TipsOperational
  • TipsOperational
  • DashboardOperational
  • RefundsOperational
  • RefundsOperational
  • TipsOperational
  • Clover SportOperational
  • PaymentsOperational
  • PaymentsOperational
  • RefundsOperational
  • Batch CloseoutsOperational
  • Batch CloseoutsOperational
  • RefundsOperational
  • TipsOperational
  • CloseoutsOperational
  • CloseoutsOperational
  • PaymentsOperational
  • RefundsOperational
  • Batch CloseoutsOperational
  • Card Issuer ProcessingOperational
  • Card Issuer ProcessingOperational
  • PaymentsOperational
  • Batch CloseoutsOperational
  • CloseoutsOperational
  • EcommerceOperational
  • EcommerceOperational
  • Card Issuer ProcessingOperational
  • CloseoutsOperational
  • Online OrderingOperational
  • Online OrderingOperational
  • Card Issuer ProcessingOperational
  • Cloud Pay DisplayOperational
  • Cloud Pay DisplayOperational
  • EcommerceOperational
  • EcommerceOperational
  • InvoicingOperational
  • InvoicingOperational
  • Online OrderingOperational
  • Cloud Pay DisplayOperational
  • Online BookingOperational
  • Online BookingOperational
  • Online OrderingOperational
  • Cloud Pay DisplayOperational
  • InvoicingOperational
  • Online ShoppingOperational
  • Online ShoppingOperational
  • InvoicingOperational
  • Online BookingOperational
  • Website BuilderOperational
  • Website BuilderOperational
  • Appointment BookingOperational
  • Appointment BookingOperational
  • Online BookingOperational
  • Online ShoppingOperational
  • Call CentersOperational
  • Call CentresOperational
  • Online ShoppingOperational
  • Website BuilderOperational
  • Appointment BookingOperational
  • Website BuilderOperational
  • Appointment BookingOperational
  • Call CentersOperational
  • Call CentersOperational
  • Multi-Factor AuthenticationOperational
  • Kitchen PrintersOperational
  • Uber EatsOperational
  • Clover Practice PayOperational
  • Gift CardOperational

These are Clover's components, named and scored by Clover. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Clover's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Clover response time, by region

US-East
2.3sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
US-West
2.2sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
Europe
2.3sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
Asia-Pacific
3.2sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 5.2s2026-11-03 UTC: p95 3.2s2026-11-04 UTC: p95 3.3s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5

Check your own site while you wait on Clover

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 Clover. It cannot diagnose Clover's own systems.

What we measured, function by function

Clover 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 auth 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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-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
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-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

Email me when Clover reports an incident on its status page, and again when it reports it resolved.

Get an email when Clover reports an incident

Email me when Clover reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Clover's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1219msstatus code: 401checked: Nov 5, 2026, 3:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Clover normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1807msstatus code: 401checked: Nov 5, 2026, 3:48 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Clover normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionClover is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionClover is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionClover is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 1906msstatus code: 401checked: Nov 5, 2026, 3:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Clover normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionClover is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 3215msstatus code: 401checked: Nov 5, 2026, 3:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Clover normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionClover is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionClover 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 Clover, 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 Clover yet, which is not evidence that nothing is wrong.

Recent probe events

Clover is experiencing an issue impacting Ecommerce products, 2h 45mdeclared on their status page2026-10-21
[NA] Clover experiencing issues with the Customer Engagement Apps, 1h 21mdeclared on their status page2026-10-08
[NA]Web dashboard login issues for a small subset of merchants on Safari Browsers, 28mdeclared on their status page2026-09-22
Clover in EMEA is experiencing an issue, 3h 19mdeclared on their status page2026-09-16
[NA] Clover merchants experiencing issues with payment processing, 1h 54mdeclared on their status page2026-08-30
Clover in NA is experiencing issues with Cloud Pay Display, 1h 10mdeclared on their status page2026-08-25
Clover in Latin America is experiencing with Cloud Pay Display, 2h 29mdeclared on their status page2026-07-08
Telstra Outage in Australia, 7h 28mdeclared on their status page2026-07-07

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Clover since November 2, 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 Clover covering any window you pick, with our check readings and Clover's own claim at the time, side by side.

Full check history for Clover: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run 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

Put this badge in your README

Clover uptime by RealUptime's checksLive, from this page's own readings.
[![Clover uptime by RealUptime's checks](https://realuptime.io/outages/clover-pos/badge.svg?days=30)](https://realuptime.io/outages/clover-pos)
<a href="https://realuptime.io/outages/clover-pos"><img src="https://realuptime.io/outages/clover-pos/badge.svg?days=30" alt="Clover uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Clover down?", https://realuptime.io/outages/clover-pos. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: auth surface
https://api.clover.com/v3/merchants
secondary
https://www.clover.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.clover.com

RealUptime is not affiliated with Clover; the name identifies what we checked, and nothing here speaks for Clover's own team. We send a single web request to Clover from 4 regions on our own schedule and time the response. We do not see inside Clover's systems, do not use an account or real transaction, and are not the same signal Clover's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Clover is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Clover 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 November 2, 2026 (3 of 14 days so far, 2488 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

ANZAbsa GroupAdyenAffirmAfterpay