Skip to content

Outage tracker

Lightspeed: incident history

The last 24 hours in detail, Lightspeed's declared incident record, and our regional check results beside it.

← Back to Lightspeed's check readings

We started checking Lightspeed on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

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

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

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

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 Lightspeed's own status page declared. Below it, any public chatter we saw about Lightspeed 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 Lightspeed'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 Lightspeed in the last 24 hours, which is not evidence that nothing is wrong.
Lightspeed's status pageNo incident declared in the last 24 hours.

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 Lightspeed's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Lightspeed 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.

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.

RegionChecks passingProbes recorded
US-East100.00%427
US-West99.69%320
Europe100.00%294
Asia-Pacific100.00%179

Their declared record

Lightspeed's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Restaurant O-Series: Accounting Integration DelaysMinor incident
Oct 28, 2026, 12:36 AM UTC to Nov 2, 2026, 10:04 PM UTC (5d 21h)resolved
their latest update (Nov 2, 2026, 10:04 PM UTC): This incident has been resolved.
Delayed Hospitality payout reportingMinor incident
Oct 26, 2026, 8:26 AM UTC to Oct 26, 2026, 1:33 PM UTC (5h 6m)resolved
their latest update (Oct 26, 2026, 1:33 PM UTC): The payment reports have synced, and details are now available.
Lightspeed Retail (R/C-Series) Latency or outageAll systems operational
Oct 23, 2026, 4:14 PM UTC to Oct 23, 2026, 9:17 PM UTC (5h 3m)resolved
their latest update (Oct 23, 2026, 9:17 PM UTC): The incident is resolved on the Cloudflare side
Slowness on C-Series webshops in EuropeMinor incident
Oct 23, 2026, 6:13 AM UTC to Oct 23, 2026, 8:25 AM UTC (2h 12m)resolved
their latest update (Oct 23, 2026, 8:25 AM UTC): This incident has been resolved.
Statement on PHP vulnerabilitiesMinor incident
Oct 21, 2026, 4:15 PM UTC to Oct 23, 2026, 1:32 PM UTC (1d 21h)resolved
their latest update (Oct 23, 2026, 1:32 PM UTC): Lightspeed has completed the deployment of security updates across all products in response to the recently reported PHP vulnerabilities. All services should be available at this time.
Restaurant O-Series: Brief API degradationAll systems operational
Oct 20, 2026, 6:30 AM UTC to Oct 20, 2026, 6:30 AM UTC (0 min)resolved
their latest update (Oct 20, 2026, 6:30 AM UTC): Our team were alerted by a small group of customers that our API had some degradation between 5:17PM and 5:29PM AEDT. This has been isolated to a scaling issue and resolved, most online orders would have succeeded with a retry during this time.
Delays - Sales history lagMinor incident
Oct 17, 2026, 2:24 AM UTC to Oct 17, 2026, 7:50 AM UTC (5h 26m)resolved
their latest update (Oct 17, 2026, 7:50 AM UTC): The sales history delays have been resolved.
Store credit issue causing sale errorsPartial outage
Oct 16, 2026, 4:34 PM UTC to Oct 16, 2026, 5:04 PM UTC (30 min)resolved
their latest update (Oct 16, 2026, 5:04 PM UTC): This incident has been resolved.
LS Pay Payment processing degraded for R-series, C-series and few L-seriesMinor incident
Oct 16, 2026, 3:44 PM UTC to Oct 20, 2026, 7:12 AM UTC (3d 15h)resolved
their latest update (Oct 20, 2026, 7:12 AM UTC): The issue with Lightspeed Payments has been resolved. Transactions are now being processed normally.
Unable to process charges for golfers at some clubsPartial outage
Oct 9, 2026, 3:58 PM UTC to Oct 9, 2026, 4:07 PM UTC (9 min)resolved
their latest update (Oct 9, 2026, 4:07 PM UTC): This incident has been resolved.

Showing the 10 most recent of 50 incidents Lightspeed has declared in the history we hold.

These entries are Lightspeed'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.

Lightspeed'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.