Live  /  Lightspeed  /  Incident

Lightspeed: Issues with Online orders and stale reports

Lightspeed · vendhq.comMajor incidentResolved2026-10-01 18:38 UTC
Public — what happened

Summary

Lightspeed reported a major incident beginning at 09:20 UTC on 2026-10-01 that disrupted online orders and left back office reports showing outdated data. The company said it knew the underlying cause from the start, though it did not describe it, and that the problem also reached reservations and their integrations, property management system integrations, the Pay at Table 2.0 beta, refunds, and certain tip-adjusted or preauthorized payment captures, while in-store card terminal payments were unaffected. Lightspeed said a fix was in place by 12:36 UTC, and it later warned that some older online orders might show up as service returns and that refunds and payouts could be delayed, asking customers not to resend requests. The incident was marked resolved at 18:38 the same day.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Lightspeed against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Lightspeed: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Lightspeed report →

More from Lightspeed

Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.

The full archive is on the Lightspeed status & history page.

Related: Lightspeed status & history. SquidGrid is not affiliated with Lightspeed.