We started checking Clover on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Clover reports an incident on its status page, and again when it reports it resolved.
01
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 Clover's own status page declared. Below it, any public chatter we saw about Clover 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 Clover's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, auth (primary)
Unverified user reportsNo reports about Clover in the last 24 hours, which is not evidence that nothing is wrong.
Clover's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
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 Clover's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Clover 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.
Confirmation probe10:36 UTC, Europe: our own first failed reading prompted an extra probe. Result: Clover did not answer.
Confirmation probe10:29 UTC, US-East: our own first failed reading prompted an extra probe. Result: our probe was refused, which tells us about our reception rather than about the service.
Confirmation probe10:18 UTC, Asia-Pacific: our own first failed reading prompted an extra probe. Result: our probe was refused, which tells us about our reception rather than about the service.
02
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
99.32%
586
US-West
99.33%
445
Europe
99.26%
406
Asia-Pacific
98.37%
246
Their declared record
Clover's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Clover is experiencing an issue impacting Ecommerce productsPartial outage
Oct 21, 2026, 1:54 AM UTC to Oct 21, 2026, 4:40 AM UTC (2h 45m)resolved
their latest update (Oct 21, 2026, 4:40 AM UTC): The issue has been resolved, and all Clover systems are working as expected. If you need further assistance, please contact Clover support at 1-877-273-8191. Thank you again for your patience while we worked through this issue.
[NA] Clover experiencing issues with the Customer Engagement AppsAll systems operational
Oct 8, 2026, 8:05 PM UTC to Oct 8, 2026, 9:26 PM UTC (1h 21m)resolved
their latest update (Oct 8, 2026, 9:26 PM UTC): The issue has been resolved, and all Clover systems are working as expected. If you need further assistance, please contact Clover support at 1-877-273-8191. Thank you again for your patience while we worked through this issue.
[NA]Web dashboard login issues for a small subset of merchants on Safari BrowsersMinor incident
Sep 22, 2026, 6:01 PM UTC to Sep 22, 2026, 6:29 PM UTC (28 min)resolved
their latest update (Sep 22, 2026, 6:29 PM UTC): The issue has been resolved, and all Clover systems are working as expected. If you need further assistance, please contact Clover support at 1-877-273-8191. Thank you again for your patience while we worked through this issue.
Clover in EMEA is experiencing an issueMinor incident
Sep 16, 2026, 12:31 PM UTC to Sep 16, 2026, 3:50 PM UTC (3h 19m)resolved
their latest update (Sep 16, 2026, 3:50 PM UTC): The impacted services are actively recovering; we will continue to monitor until full health is restored. If you need further assistance, please contact Clover support. Thank you again for your patience while we worked through this issue.
[NA] Clover merchants experiencing issues with payment processingMinor incident
Aug 30, 2026, 5:49 AM UTC to Aug 30, 2026, 7:44 AM UTC (1h 54m)resolved
their latest update (Aug 30, 2026, 7:44 AM UTC): The issue has been resolved, and all Clover systems are working as expected. If you need further assistance, please contact Clover support at 1-877-273-8191. Thank you again for your patience while we worked through this issue.
Clover in NA is experiencing issues with Cloud Pay DisplayMinor incident
Aug 25, 2026, 1:16 PM UTC to Aug 25, 2026, 2:26 PM UTC (1h 10m)resolved
their latest update (Aug 25, 2026, 2:26 PM UTC): The issue has been resolved, and all Clover systems are working as expected. If you need further assistance, please contact Clover support at 1-877-273-8191. Thank you again for your patience while we worked through this issue.
Clover in Latin America is experiencing with Cloud Pay DisplayPartial outage
Jul 8, 2026, 2:46 PM UTC to Jul 8, 2026, 5:14 PM UTC (2h 29m)resolved
their latest update (Jul 8, 2026, 5:14 PM UTC): We have successfully resolved the issue affecting transaction processing via the REST API for the LATAM region. All services are fully operational.
Thank you for your patience while our teams worked to restore service.
Telstra Outage in AustraliaPartial outage
Jul 7, 2026, 10:14 PM UTC to Jul 8, 2026, 5:42 AM UTC (7h 28m)resolved
their latest update (Jul 8, 2026, 5:42 AM UTC): Telstra has fully restored their network services, resolving the nationwide cellular outage.
The issue has been resolved, and all Clover systems are working as expected. If you need further assistance, please contact support. Thank you again for your patience through this issue.
Clover in North America is experiencing an issuePartial outage
May 8, 2026, 7:09 PM UTC to May 8, 2026, 7:23 PM UTC (14 min)resolved
their latest update (May 8, 2026, 7:23 PM UTC): The issue has been resolved, and all Clover systems are working as expected. If you need further assistance, please contact Clover support at 1-877-273-8191. Thank you again for your patience while we worked through this issue.
Clover Online Ordering is currently experiencing issues for Australia RegionMinor incident
Apr 29, 2026, 3:24 AM UTC to Apr 29, 2026, 4:38 AM UTC (1h 14m)resolved
their latest update (Apr 29, 2026, 4:38 AM UTC): The issue has been resolved, and all Clover systems are working as expected. Thank you again for your patience while we worked through this issue.
Showing the 10 most recent of 50 incidents Clover has declared in the history we hold.
These entries are Clover's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Clover's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.