- 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 →
- Detected by Pingoru
- Jul 08, 2026, 06:58 PM UTC
- Resolved
- Jul 08, 2026, 09:01 PM UTC
- Duration
- 2h 3m
Affected: Lightspeed eCom (Europe)
Timeline · 6 updates
-
investigating Jul 08, 2026, 06:58 PM UTC
We are currently investigating this issue.
-
investigating Jul 08, 2026, 06:58 PM UTC
We are continuing to investigate this issue.
-
identified Jul 08, 2026, 07:28 PM UTC
The issue affecting C-Series has been mitigated. Merchants may have experienced slow performance, 500 errors when accessing the cart, or their cart appearing empty. The issue has been identified, and a fix is being implemented.
-
monitoring Jul 08, 2026, 08:13 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jul 08, 2026, 09:00 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 08, 2026, 09:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 10:44 AM UTC
- Resolved
- Jul 07, 2026, 01:03 PM UTC
- Duration
- 2h 19m
Affected: Lightspeed PaymentsLightspeed PaymentsPaymentsLightspeed Payments
Timeline · 3 updates
-
monitoring Jul 07, 2026, 10:44 AM UTC
Payouts initiated on July 5th and July 6th are currently not visible in the Back Office, despite being successfully transferred to the respective bank accounts. This issue impacts Lightspeed Payments reporting for users in Europe (excluding Switzerland) and Australia. The root cause has already been identified. The affected reports are currently being ingested, but this process is taking additional time to complete. We will continue monitoring the progress until all reports are available in the Back Office.
-
monitoring Jul 07, 2026, 11:39 AM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 07, 2026, 01:03 PM UTC
The incident has been resolved. All affected payouts are now correctly reflected in the Back Office.
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 08:09 AM UTC
- Resolved
- Jul 06, 2026, 01:05 PM UTC
- Duration
- 4h 55m
Affected: Lightspeed PaymentsLightspeed Payments
Timeline · 5 updates
-
investigating Jul 06, 2026, 08:09 AM UTC
We have identified an external issue resulting in a partial payout delay for a subset of AUD transactions processed through one of our partner banks. As a result, some customers receiving Regular (BECS) payouts in Australia may experience a delay in receiving their payouts expected this Monday. We are actively monitoring the situation and coordinating with the affected partner to support resolution efforts.
-
investigating Jul 06, 2026, 08:11 AM UTC
We are continuing to investigate this issue.
-
investigating Jul 06, 2026, 08:12 AM UTC
We are continuing to investigate this issue.
-
monitoring Jul 06, 2026, 10:04 AM UTC
We have identified an external issue causing delays to some Regular (BECS) payouts in Australia. Affected funds are expected to be credited by the end of the day on 6 July 2026 in AU time.
-
resolved Jul 06, 2026, 01:05 PM UTC
The external issue that caused delays to some Regular (BECS) payouts in Australia has been resolved. All impacted payouts have now been processed and will be credited to the affected accounts.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 10:21 PM UTC
- Resolved
- Jul 02, 2026, 10:57 PM UTC
- Duration
- 36m
Affected: InventoryProductsSales History
Timeline · 2 updates
-
monitoring Jul 02, 2026, 10:21 PM UTC
Some retailers may experience delays in updates made to the system showing throughout the system. This impacts - inventory levels slow in reflecting the right levels - product added not appearing in searches and online store - product updated not reflecting in searches and online store - sales made may not be available in sales history We have identified and resolving the issue and are monitoring system recovery
-
resolved Jul 02, 2026, 10:57 PM UTC
The delay is gone. There might be some remaining webhooks being sent to integrators.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 09:05 PM UTC
- Resolved
- Jul 05, 2026, 11:02 PM UTC
- Duration
- 4d 1h
Affected: Inventory
Timeline · 2 updates
-
monitoring Jul 01, 2026, 09:05 PM UTC
The polecat event pusher is experiencing significant lag. The problem has been identified and resolved. Monitoring the situation.
-
resolved Jul 05, 2026, 11:02 PM UTC
Resolved
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2026, 01:21 PM UTC
- Resolved
- Jun 30, 2026, 08:49 PM UTC
- Duration
- 7h 27m
Affected: POS
Timeline · 3 updates
-
investigating Jun 30, 2026, 01:21 PM UTC
Nous examinons actuellement ce cas. We are currently investigating this issue.
-
identified Jun 30, 2026, 01:56 PM UTC
Revenu Québec a identifié des difficultés techniques liées à la communication entre les systèmes d'enregistrement des ventes (SRS) et le WEB-SRM, qui peuvent causer l'affichage de messages d'erreur sur les appareils. Cette situation n'a toutefois aucune incidence sur les données que les exploitants transmettent à Revenu Québec. Ils n'ont donc pas à nous les retransmettre. Revenu Québec travaillent à rétablir la situation dès que possible. ---- Revenu Québec is aware of the technical difficulties with how sales recording systems (SRSs) communicate with the WEB-SRM which may be causing error messages to display on the devices. This situation does not affect the data that operators send to Revenu Québec, and data does not need to be resent. Revenu Québec is currently working to quickly address the issue.
-
resolved Jun 30, 2026, 08:49 PM UTC
Les difficultés techniques de ce matin touchant la communication des systèmes d'enregistrement des ventes (SEV) avec le MEV-WEB sont maintenant rétablies. ----- The technical difficulties of this morning concerning the communication of the sales recording systems (SRSs) with the WEB-SRM have now been restored.
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2026, 08:34 AM UTC
- Resolved
- Jun 25, 2026, 11:31 AM UTC
- Duration
- 2h 56m
Affected: Sales History
Timeline · 3 updates
-
investigating Jun 25, 2026, 08:34 AM UTC
We are currently investigating an issue where some sales are not appearing in Sales History. We are actively working to identify the root cause and restore normal functionality. We will provide additional updates as more information becomes available.
-
monitoring Jun 25, 2026, 11:09 AM UTC
The fix for the issue causing some sales to not appear in Sales History has been successfully rolled out. Sales History should now be updating as expected. We are continuing to monitor the system closely to ensure stability and confirm the issue is fully resolved. We will provide additional updates if necessary.
-
resolved Jun 25, 2026, 11:31 AM UTC
The issue has been resolved and Sales History is now updating as expected.
Read the full incident report →
- Detected by Pingoru
- Jun 24, 2026, 12:43 PM UTC
- Resolved
- Jun 23, 2026, 11:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 24, 2026, 12:43 PM UTC
K-Series merchants experienced a Lightspeed Payments issue that could cause payment failures. As a temporary workaround, merchants could take payments in standalone mode until full service resumed.
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 02:15 PM UTC
- Resolved
- Jun 22, 2026, 03:07 PM UTC
- Duration
- 51m
Affected: Retail POSRetail API
Timeline · 4 updates
-
investigating Jun 22, 2026, 02:15 PM UTC
We are aware of login issues on R-Series for some accounts. We are currently investigating.
-
identified Jun 22, 2026, 02:31 PM UTC
The issue has been identified to be related to a 3rd party and they are working on a fix.
-
monitoring Jun 22, 2026, 02:43 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 22, 2026, 03:07 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 04:25 PM UTC
- Resolved
- Jun 18, 2026, 04:25 PM UTC
- Duration
- —
Affected: Payments
Timeline · 1 update
-
resolved Jun 18, 2026, 04:25 PM UTC
Some merchants may have experienced a payments degradation that hindered payment completion. A fix has been implemented and payments can be retired.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 03:58 PM UTC
- Resolved
- Jun 18, 2026, 04:13 PM UTC
- Duration
- 14m
Affected: Payments
Timeline · 2 updates
-
monitoring Jun 18, 2026, 03:58 PM UTC
We are currently investigating an issue where merchants are unable to complete transactions using Lightspeed Payments.
-
resolved Jun 18, 2026, 04:13 PM UTC
The issue preventing merchants from completing transactions using Lightspeed Payments has been fully resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 07:48 AM UTC
- Resolved
- Jun 18, 2026, 07:22 AM UTC
- Duration
- 23h 33m
Affected: Lightspeed Payments
Timeline · 3 updates
-
investigating Jun 17, 2026, 07:48 AM UTC
We are currently investigating an issue where the Lightspeed K-Series app becomes unresponsive on iOS devices when the iPhone is locked (screen turned off) after a payment has successfully completed. Workaround: Force-close and restart the app to restore functionality.
-
identified Jun 17, 2026, 03:34 PM UTC
Update: We have successfully identified the issue. We are working to deploy a fix and expect version 26.24.1 to be available on the App Store as soon as possible.
-
resolved Jun 18, 2026, 07:22 AM UTC
We have released a fix for this issue in version 26.24.1. Please update your Lightspeed K-Series app through the App Store to resolve the problem.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 04:11 PM UTC
- Resolved
- Jun 10, 2026, 08:27 PM UTC
- Duration
- 4h 16m
Affected: Retail POSRetail API
Timeline · 4 updates
-
investigating Jun 10, 2026, 04:11 PM UTC
We are currently investigating an issue affecting merchants using Lightspeed Retail. A dedicated team is investigating the issue.
-
identified Jun 10, 2026, 04:44 PM UTC
We have identified the cause of the Lightspeed Retail (R-Series) issue and a dedicated team of engineers is working on a solution.
-
monitoring Jun 10, 2026, 08:09 PM UTC
We have implemented a fix and will continue to monitor the situation.
-
resolved Jun 10, 2026, 08:27 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 11:51 AM UTC
- Resolved
- Jun 04, 2026, 02:01 PM UTC
- Duration
- 2h 10m
Affected: Payments
Timeline · 5 updates
-
investigating Jun 04, 2026, 11:51 AM UTC
We are currently investigating this issue.
-
investigating Jun 04, 2026, 11:53 AM UTC
We are continuing to investigate this issue.
-
investigating Jun 04, 2026, 12:06 PM UTC
We are currently experiencing an issue with integrated payments initiated through the POS system. As a workaround, payments can still be processed using standalone mode: https://k-series-support.lightspeedhq.com/hc/en-us/articles/5028210082715-Standalone-payments
-
monitoring Jun 04, 2026, 01:19 PM UTC
A fix has been implemented, and we are currently monitoring the results.
-
resolved Jun 04, 2026, 02:01 PM UTC
The issue affecting integrated payments has been resolved.
Read the full incident report →
