Notice September 14, 2026 - Detected by Pingoru
- Sep 14, 2026, 04:24 PM UTC
- Resolved
- Sep 15, 2026, 08:15 PM UTC
- Duration
- 1d 3h
Affected: Phone Support
Timeline · 3 updates
-
investigating Sep 14, 2026, 04:24 PM UTC
We are currently receiving reports of degraded service on our French K-series support line for French callers. Our team is currently investigating this. Our French support service is temporarily available at the following number: +33187652207
-
monitoring Sep 15, 2026, 03:02 PM UTC
Services are gradually being restored on the French K-series support lines. Our team is monitoring further.
-
resolved Sep 15, 2026, 08:15 PM UTC
Services are now fully restored on the French K-series support lines.
Read the full incident report →
- Detected by Pingoru
- Sep 10, 2026, 08:15 AM UTC
- Resolved
- Sep 10, 2026, 08:15 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 10, 2026, 09:34 PM UTC
Completed / Resolved Between 20:16 UTC and 21:28 UTC, Lightspeed Payments experienced elevated error rates and response delays with Interac payment processing. This was caused by a third-party issue on the Interac network external to our systems. The upstream network issue has since been resolved, and Interac processing is fully operational.
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2026, 04:16 AM UTC
- Resolved
- Sep 10, 2026, 04:26 AM UTC
- Duration
- 1d
Affected: Lightspeed Payments
Timeline · 3 updates
-
investigating Sep 09, 2026, 04:16 AM UTC
We have received reports that some CA merchants have been unable to process AMEX transactions since 4 September 2026 due to the payment method being disabled in error. Our team is actively investigating the issue, and we will provide further updates as soon as possible.
-
investigating Sep 09, 2026, 07:03 AM UTC
We are currently investigating the issue.
-
resolved Sep 10, 2026, 04:26 AM UTC
The payment method was re-added for those accounts, allowing them to process AMEX cards again. This is now resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 07, 2026, 09:01 AM UTC
- Resolved
- Sep 05, 2026, 02:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 07, 2026, 09:01 AM UTC
Some K-Series Cloud merchants may have experienced intermittent issues when processing payments. A configuration update was applied to mitigate the issue, payment processing returned to normal, and the service is being monitored.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 03:22 PM UTC
- Resolved
- Sep 03, 2026, 11:53 PM UTC
- Duration
- 8h 30m
Affected: Setup
Timeline · 3 updates
-
investigating Sep 03, 2026, 03:22 PM UTC
We are aware of an issue where on-account payment information is not updating as expected. Our team is currently investigating the issue and working to resolve it. We’ll provide another update as soon as we have more information.
-
investigating Sep 03, 2026, 03:23 PM UTC
We are aware of an issue where on-account payment information is not updating as expected. Our team is currently investigating the issue and working to resolve it. We’ll provide another update as soon as we have more information.
-
resolved Sep 03, 2026, 11:53 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 01:26 AM UTC
- Resolved
- Sep 01, 2026, 01:42 AM UTC
- Duration
- 15m
Affected: API
Timeline · 2 updates
-
investigating Sep 01, 2026, 01:26 AM UTC
Our team is investigating an issue where Integration Partners are unable to contact the Lightspeed O-Series API intermittently, resulting in online ordering delays starting at approximately 11:10AM AEST.
-
resolved Sep 01, 2026, 01:42 AM UTC
Our team have resolved a configuration error and systems should now be functioning as normal.
Read the full incident report →
- Detected by Pingoru
- Aug 27, 2026, 04:06 AM UTC
- Resolved
- Aug 27, 2026, 10:36 AM UTC
- Duration
- 6h 30m
Affected: Retail POS
Timeline · 3 updates
-
investigating Aug 27, 2026, 04:06 AM UTC
We are currently investigating an issue where a sale can be completed when there is still outstanding balance after split payments.
-
monitoring Aug 27, 2026, 04:37 AM UTC
We identified the root cause, and deployed a fix. If you still observe this behaviour make sure to refresh your browser to ensure you get the latest updated code.
-
resolved Aug 27, 2026, 10:36 AM UTC
The issue has been resolved now
Read the full incident report →
- Detected by Pingoru
- Aug 15, 2026, 05:57 AM UTC
- Resolved
- Aug 16, 2026, 11:07 PM UTC
- Duration
- 1d 17h
Affected: Lightspeed Payments
Timeline · 5 updates
-
investigating Aug 15, 2026, 05:48 AM UTC
We are aware of an issue impacting some customers’ ability to process Lightspeed Payments transactions. Card payments may be declined intermittently across both Wi-Fi and hotspot connections. Our team is investigating and will continue to post updates here as they become available.
-
investigating Aug 15, 2026, 05:57 AM UTC
We continue to monitor the Mastercard issue affecting some Lightspeed Payments transactions across Wi-Fi and hotspot connections. Our team is working on this and will provide further updates as more information becomes available.
-
identified Aug 15, 2026, 05:59 AM UTC
We have identified a widespread issue affecting Mastercard payment processing. Some Lightspeed Payments transactions may be declined, regardless of whether the terminal is connected via Wi-Fi or hotspot. We are working with Mastercard and monitoring the situation closely. We’ll provide further updates as they become available.
-
monitoring Aug 15, 2026, 06:29 AM UTC
Mastercard service is now operational, and we are seeing successful Lightspeed Payments transactions again. We are continuing to monitor payment processing across Wi-Fi and hotspot connections before resolving the incident.
-
resolved Aug 16, 2026, 11:07 PM UTC
Mastercard has resolved the issue affecting Mastercard payment processing. No further impact has been observed for Lightspeed Payments, and this incident is now closed.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 07:18 PM UTC
- Resolved
- Aug 07, 2026, 07:30 PM UTC
- Duration
- 11m
Timeline · 1 update
-
investigating Aug 07, 2026, 07:18 PM UTC
One of our servers is having problems since August 7, 06:51 UTC. This causes some of the storefronts to open slowly. We are working on restoring the service. All your data and store settings will be intact. We are sorry for this downtime. Next update in 30 minutes.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 01:59 PM UTC
- Resolved
- Aug 11, 2026, 08:43 PM UTC
- Duration
- 4d 6h
Affected: Retail POS for iPadOS
Timeline · 4 updates
-
investigating Aug 07, 2026, 01:59 PM UTC
We're aware of an issue where retailers using app version 6.22 on iPads with a non-English language setting are unable to open registers. We're actively working on a fix and will provide updates as they become available.
-
identified Aug 07, 2026, 02:07 PM UTC
We've identified the issue preventing registers from opening on app version 6.22 for iPads using a non-English language setting. We're working on a fix and will share updates as they become available.
-
monitoring Aug 10, 2026, 01:38 PM UTC
We have released version 6.22.1 that restores the capability to open the register on iPad.
-
resolved Aug 11, 2026, 08:43 PM UTC
This incident is now resolved, registers can be open again from X-Series iOS client for non-English language.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 09:42 AM UTC
- Resolved
- Aug 07, 2026, 10:21 AM UTC
- Duration
- 39m
Affected: Lightspeed eCom (Europe)
Timeline · 3 updates
-
identified Aug 07, 2026, 09:42 AM UTC
We are currently investigating an issue affecting merchants using Lightspeed eCom in Europe. A dedicated team is investigating the issue.
-
monitoring Aug 07, 2026, 09:57 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 07, 2026, 10:21 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2026, 02:45 AM UTC
- Resolved
- Aug 08, 2026, 07:16 AM UTC
- Duration
- 2d 4h
Affected: Customer ManagementInventoryProducts
Timeline · 4 updates
-
identified Aug 06, 2026, 02:45 AM UTC
We’re looking into an issue where Entities (products, sales and inventory and customers) are displaying out-of-date results to Lightspeed (X-Series) retailers and will keep you posted with updates as they come. Thanks for your patience.
-
monitoring Aug 06, 2026, 03:39 AM UTC
We have identified the root cause and now we are working on the recovering. We will post an update once the delay is over. Thank you for your patience.
-
monitoring Aug 06, 2026, 09:51 PM UTC
We are still monitoring this incident, we still have some lag to catch up on, and we will post an update when are fully recovered.
-
resolved Aug 08, 2026, 07:16 AM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2026, 03:34 PM UTC
- Resolved
- Aug 05, 2026, 04:18 PM UTC
- Duration
- 44m
Affected: Retail POS
Timeline · 2 updates
-
investigating Aug 05, 2026, 03:34 PM UTC
We are investigating reports of receipt printers failing to work or not being detected after the latest system update. Some users are encountering a "Bad Request 400" error.
-
monitoring Aug 05, 2026, 03:48 PM UTC
A fix has been implemented and we are monitoring the results.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2026, 09:01 AM UTC
- Resolved
- Aug 04, 2026, 12:14 PM UTC
- Duration
- 3h 13m
Affected: InventorySales History
Timeline · 4 updates
-
investigating Aug 04, 2026, 09:01 AM UTC
Newly created sales are processing successfully and receipts can be printed, but they are not appearing in Sales History or updating stock adjustments; our team is currently investigating the issue.
-
identified Aug 04, 2026, 09:15 AM UTC
Newly created sales are processing successfully and receipts can be printed, but they are not appearing in Sales History or updating stock adjustments; our team have identified the issue and rolling out a fix.
-
monitoring Aug 04, 2026, 09:26 AM UTC
A fix has been rolled out.
-
resolved Aug 04, 2026, 12:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2026, 05:33 AM UTC
- Resolved
- Jul 29, 2026, 08:14 AM UTC
- Duration
- 2h 40m
Affected: Standard Reporting
Timeline · 3 updates
-
identified Jul 29, 2026, 05:33 AM UTC
Our team are adjusting the work done earlier today to fine tune back office reports performance after users had reported delayed updates. Some users remain impacted by this issue and our team are working to bring this back up to date.
-
monitoring Jul 29, 2026, 06:58 AM UTC
The fix released earlier today has been refined, we will monitor performance.
-
resolved Jul 29, 2026, 08:14 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2026, 12:55 AM UTC
- Resolved
- Jul 29, 2026, 01:42 AM UTC
- Duration
- 46m
Affected: Back Office
Timeline · 3 updates
-
identified Jul 29, 2026, 12:55 AM UTC
We are currently investigating an issue where some merchants may experience their Back Office Dashboard reports not updating with the latest data. Our Development team is aware of the issue and is actively investigating the root cause. We will provide further updates as soon as more information becomes available. We apologize for any inconvenience and appreciate your patience while we work to resolve this issue.
-
monitoring Jul 29, 2026, 01:26 AM UTC
A fix has been implemented, and we are currently monitoring the results to ensure the issue has been resolved successfully. We appreciate your patience while we continue to verify the stability of the fix. We will provide another update once monitoring has been completed or if we identify any further issues.
-
resolved Jul 29, 2026, 01:42 AM UTC
The issue affecting Back Office Dashboard reports not updating has now been resolved. Our team has verified that the fix has been successfully implemented, and dashboard data is updating as expected.
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 05:08 PM UTC
- Resolved
- Jul 27, 2026, 06:21 PM UTC
- Duration
- 1h 13m
Affected: Retail POS
Timeline · 2 updates
-
monitoring Jul 27, 2026, 05:08 PM UTC
We are currently investigating an issue where merchants are experiencing error messages when attempting to view or load customer details within the X-Series Sell Screen. Our engineering team has identified the cause and deployed a fix. Systems are recovering, and we are actively monitoring to confirm full resolution.
-
resolved Jul 27, 2026, 06:21 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 03:42 PM UTC
- Resolved
- Jul 27, 2026, 04:07 PM UTC
- Duration
- 24m
Affected: Lightspeed eCom (North America & Australia)
Timeline · 3 updates
-
investigating Jul 27, 2026, 03:42 PM UTC
We are currently investigating an issue affecting merchants using Lightspeed eCom in North America. A dedicated team is investigating the issue.
-
monitoring Jul 27, 2026, 03:59 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 27, 2026, 04:07 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 12:00 PM UTC
- Resolved
- Jul 24, 2026, 12:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 24, 2026, 05:59 PM UTC
Between 12:45 PM and 1:15 PM BST, an upstream issue with a third-party cloud infrastructure provider caused brief slowness and connection errors affecting X-Series POS selling screens for some stores. The core impact was limited to a ~35-minute window, and services quickly normalized. All Lightspeed core internal systems remained fully operational throughout the event, and any offline transactions processed during the disruption have synchronized. The upstream provider has resolved the issue, and all systems are running normally.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 10:35 PM UTC
- Resolved
- Jul 23, 2026, 11:48 PM UTC
- Duration
- 1h 13m
Affected: Sales History
Timeline · 3 updates
-
investigating Jul 23, 2026, 10:35 PM UTC
We are currently investigating an issue impacting return and exchange processing under certain specific transaction conditions. Our engineering team are currently investigating the reported issue. We apologize for the inconvenience caused in the meantime
-
monitoring Jul 23, 2026, 11:00 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 23, 2026, 11:48 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2026, 09:10 PM UTC
- Resolved
- Jul 18, 2026, 08:19 PM UTC
- Duration
- 23h 9m
Affected: Tee SheetsMarketplaceHouse AccountsBusiness IntelligenceMobile AppsPartner API
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2026, 11:18 AM UTC
- Resolved
- Jul 17, 2026, 12:17 PM UTC
- Duration
- 58m
Affected: Lightspeed Payments
Timeline · 3 updates
-
investigating Jul 17, 2026, 11:18 AM UTC
We are aware of an issue affecting certain payment terminal integrations. Our team is actively investigating and working to restore normal processing. We apologise for the disruption to your sales operations and will provide updates as we learn more.
-
monitoring Jul 17, 2026, 11:48 AM UTC
The issue is now resolved. We will continue to monitor the situation. If you are still experiencing issues, please use our standalone payments workaround: https://k-series-support.lightspeedhq.com/hc/en-us/articles/5028210082715-Standalone-payments
-
resolved Jul 17, 2026, 12:17 PM UTC
The issue with Lightspeed Payments has been resolved. Transactions are now being processed normally.
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2026, 08:03 PM UTC
- Resolved
- Jul 11, 2026, 08:39 PM UTC
- Duration
- 35m
Affected: PaymentsIntegrated Payments
Timeline · 3 updates
-
investigating Jul 11, 2026, 08:03 PM UTC
Merchants may be experiencing a freeze in their POS while processing but it appears transactions are still successful. A refresh of the POS should resolve the freeze. Please verify Financial Services reporting before retrying transactions.
-
monitoring Jul 11, 2026, 08:19 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 11, 2026, 08:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2026, 02:51 PM UTC
- Resolved
- Jul 09, 2026, 03:02 PM UTC
- Duration
- 11m
Affected: Genesys API's
Timeline · 1 update
-
investigating Jul 09, 2026, 02:51 PM UTC
Add your message to here for the platform users or subscribers
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 08:49 PM UTC
- Resolved
- Jul 08, 2026, 09:13 PM UTC
- Duration
- 24m
Affected: Payments
Timeline · 3 updates
-
investigating Jul 08, 2026, 08:49 PM UTC
Our engineering team has been notified and is actively investigating the root cause. We will provide updates as soon as we have more information.
-
monitoring Jul 08, 2026, 09:09 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 08, 2026, 09:13 PM UTC
This incident has been resolved.
Read the full incident report →