System Status
Service status
Recent incidents
Online ordering slow page loads — Atlantic Canada
ResolvedA subset of online ordering pages experienced 3–5 second page-load delays for customers in NB, NS, PE, and NL. POS terminals and card payments were unaffected.
Scheduled maintenance — Clover Cloud dashboard
CompletedRoutine database maintenance on the Clover Cloud dashboard. Reporting was read-only for 38 minutes during the window. POS terminals and payments were unaffected throughout.
Brief payment processor latency
ResolvedA small percentage of card transactions experienced 4–6 second authorization delays. No transactions were lost or duplicated — all completed successfully, just slowly.
Reports dashboard timeout — affected ~3% of accounts
ResolvedA query optimization issue caused reports loading for ~3% of merchant accounts to time out. Live POS and payments were unaffected. Affected accounts saw temporary "loading" states.
Network maintenance — primary data center
CompletedPre-announced overnight network upgrade. All POS terminals continued operating in offline mode during the 22-minute window. Transactions auto-synced when the window closed — no manual reconciliation needed.
Get notified when status changes.
One email when an incident starts. One when it's resolved. Heads-up emails for scheduled maintenance. That's it — no marketing, ever.
About this page
Service status is checked every 30 seconds by our monitoring system, and the page refreshes automatically. The "Updated" timestamp at the top of the page reflects the most recent check. If an incident is in progress, status updates are posted within 5 minutes of any state change (Investigating → Identified → Monitoring → Resolved).
Operational means the service is running normally with response times in the expected range. Degraded means a measurable performance hit (e.g., slower than usual, but still working) — most users won't notice but some will. Outage means a significant portion of users can't successfully use that service. Maintenance means we've intentionally taken the service partially offline for planned work, usually overnight.
Most likely a local issue specific to your setup — Wi-Fi, a specific device, or a configuration. Try a full power cycle first (hold the power button 10 seconds, wait, restart). If that doesn't fix it, call (866) 667-1377 — a specialist can usually diagnose in under 5 minutes whether it's truly local or whether there's a regional issue our monitoring hasn't yet picked up.
Your Clover device automatically switches to offline payments mode if it can't reach our network, so you keep accepting cards (up to your configured offline limit). Transactions queue locally and sync the second the connection comes back — no data loss, no double charges, no manual reconciliation. For payment-processor-level outages (rare), pending transactions retry automatically once authorization is restored.
Any event that measurably affects a real customer's ability to use a service gets logged as an incident — even if it's brief, even if it only affects a small percentage of accounts, even if no one calls in. We publish post-mortems for outages over 30 minutes within 5 business days, including root cause and remediation steps.
Yes — partners and integrators can poll our status API at status.greatpos.ca/api/v1/status (returns JSON with service states, current incidents, and 90-day uptime data). Rate-limited to 60 requests per minute. Contact partners@greatpos.com for an API key or to discuss webhook delivery on state changes.