Lakeside Software Outage History

Lakeside Software is up right now

Lakeside Software had 7 outages in the last 2 years totaling 35h 22m of downtime — averaging 0.3 incidents per month.

There were 7 Lakeside Software outages since July 8, 2025 totaling 35h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://cloudstatus.lakesidesoftware.com

Minor May 13, 2026

SysTrack Cloud – Availability Issues

Detected by Pingoru
May 13, 2026, 03:00 PM UTC
Resolved
May 13, 2026, 04:53 PM UTC
Duration
1h 53m
Affected: SysTrack API/UI
Timeline · 3 updates
  1. investigating May 13, 2026, 03:00 PM UTC

    We are currently investigating reports that some users in the below regions are experiencing availability issues with SysTrack Cloud endpoints. Some request may be unavailable for affected endpoints. We're actively working on identifying the root cause. We apologize for any inconvenience and will provide an update once more details become available.

  2. monitoring May 13, 2026, 03:44 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 13, 2026, 04:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026

NLQ Feature

Detected by Pingoru
Mar 12, 2026, 05:33 PM UTC
Resolved
Mar 13, 2026, 12:52 AM UTC
Duration
7h 19m
Affected: SysTrack AISysTrack AISysTrack AI
Timeline · 5 updates
  1. identified Mar 12, 2026, 05:33 PM UTC

    A Microsoft Azure dependency used by our NLQ feature is currently experiencing issues, which may result in degraded or unavailable NLQ responses. All other SysTrack functionality remains unaffected. We have engaged Microsoft and are actively monitoring the situation. We will provide updates as more information becomes available.

  2. identified Mar 12, 2026, 05:40 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Mar 12, 2026, 06:49 PM UTC

    We are continuing to work with Microsoft on a resolution.

  4. identified Mar 12, 2026, 10:44 PM UTC

    We are continuing to work with Microsoft on a resolution. Microsoft Azure Tracking ID: SH0P-S10

  5. resolved Mar 13, 2026, 12:52 AM UTC

    We have mitigated the issue and are working with our cloud provider to identify the root cause. If you are experiences any problems, please contact support.

Read the full incident report →

Minor January 29, 2026

Sensor Data not ingested into the central cloud database

Detected by Pingoru
Jan 29, 2026, 09:24 AM UTC
Resolved
Jan 29, 2026, 02:46 PM UTC
Duration
5h 22m
Affected: SysTrack Endpoint Connections
Timeline · 5 updates
  1. identified Jan 29, 2026, 11:24 AM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Jan 29, 2026, 12:33 PM UTC

    A fix has been deployed and we are observing system recovery. We will continue to monitor and provide updates as needed.

  3. identified Jan 29, 2026, 01:16 PM UTC

    We are continuing to observing system recovery.

  4. monitoring Jan 29, 2026, 01:50 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jan 29, 2026, 02:46 PM UTC

    This incident has been resolved. If you need further assistance, please open a ticket on the customer portal (https://customers.lakesidesoftware.com/).

Read the full incident report →

Minor October 29, 2025

NLQ Agent Queries Issue

Detected by Pingoru
Oct 29, 2025, 04:00 PM UTC
Resolved
Oct 30, 2025, 12:28 AM UTC
Duration
8h 27m
Affected: SysTrack AISysTrack AISysTrack AISysTrack AISysTrack AI
Timeline · 5 updates
  1. identified Oct 29, 2025, 06:56 PM UTC

    Only NLQ Agent queries are not processing data from the end points due to the ongoing Microsoft Azure Outage (YKYN-BWZ).

  2. identified Oct 29, 2025, 08:18 PM UTC

    We are monitoring the on going Azure outage for recovery.

  3. monitoring Oct 29, 2025, 11:02 PM UTC

    We are continuing to monitor the Azure recovery efforts.

  4. resolved Oct 30, 2025, 12:28 AM UTC

    We have mitigated the issue and are working with our cloud provider to identify the root cause. If you are experiences any problems, please contact support.

  5. postmortem Nov 07, 2025, 05:02 PM UTC

    # What was the issue? NLQ Agent queries responses could not be guaranteed to be processed. # What was the root cause? See Microsoft public RCA located here: [https://azure.status.microsoft/en-us/status/history/](https://azure.status.microsoft/en-us/status/history/) under “Preliminary Post Incident Review \(PIR\) - Azure Front Door - Connectivity issues across multiple regions” # What is the Prevention Strategy? Design a failover back system if Azure Front Door is not available.

Read the full incident report →

Minor October 27, 2025

SysTrack Cloud – Reports of Delayed Performance

Detected by Pingoru
Oct 27, 2025, 01:34 PM UTC
Resolved
Oct 27, 2025, 04:48 PM UTC
Duration
3h 13m
Affected: SysTrack API/UI
Timeline · 6 updates
  1. investigating Oct 27, 2025, 01:34 PM UTC

    Some slowness when using the SysTrack Cloud UI or while making API calls. We're actively working on identifying the root cause. We apologize for any inconvenience and will provide an update once more details become available

  2. investigating Oct 27, 2025, 02:33 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 27, 2025, 03:41 PM UTC

    The issue has been identified and a fix is being implemented.

  4. identified Oct 27, 2025, 04:39 PM UTC

    We are continuing to work on a fix for this issue.

  5. resolved Oct 27, 2025, 04:48 PM UTC

    We have mitigated the issue and are working with our cloud provider to identify the root cause. If you are experiences any problems, please contact support.

  6. postmortem Nov 07, 2025, 05:02 PM UTC

    # What was the issue? Some customers experienced slowness when accessing the SysTrack CE UI in the America's region. # What was the root cause? An under-layering resource was over utilized causes the slowness in the UI. # What is the Prevention Strategy? 1. Query data from the underlaying resource less often and implement cache where possible. **\(Completed\)** 2. Add additional alerting \(12/1\)

Read the full incident report →

Minor October 24, 2025

SysTrack Cloud – Intermittent SIP Outage

Detected by Pingoru
Oct 24, 2025, 09:31 PM UTC
Resolved
Oct 25, 2025, 02:03 AM UTC
Duration
4h 32m
Affected: SysTrack AISysTrack AISysTrack AISysTrack AI
Timeline · 5 updates
  1. investigating Oct 24, 2025, 09:31 PM UTC

    Some requests may fail intermittently when using SIP. We're actively working on identifying the root cause with our backend service provider. We apologize for any inconvenience and will provide an update once more details become available.

  2. identified Oct 24, 2025, 11:54 PM UTC

    Microsoft has acknowledged the intermittent azure OpenAI connection issues with tracking ID 3LRH-PBZ. We are continuing to monitor our vendor progress and provide updates as available.

  3. monitoring Oct 25, 2025, 01:09 AM UTC

    It appears Microsoft Azure has implemented a fix, as our internal monitors are reporting no further issues, but Microsoft Azure have yet to clear the outage (Incident: 3LRH-PBZ). We will continue to monitor the situation.

  4. resolved Oct 25, 2025, 02:03 AM UTC

    Microsoft Azure has resolved the issue. Please contact support if you need any further assistance.

  5. postmortem Nov 07, 2025, 05:01 PM UTC

    # What was the issue? SIP features were not responding for customers # What was the root cause? From Microsoft: “Between **18:00 UTC on 24 October 2025** and **00:41 UTC on 25 October 2025**, a platform issue caused intermittent authentication failures and 401 unauthorized errors for services leveraging VNET and/or Private Endpoints across multiple regions \(East US 2, Central US, Australia East, West US, and UK South\). This was due to a conflict in managed identity assignment stemming from an internal configuration change.” # What is the Prevention Strategy? Better error handling within the application

Read the full incident report →

Minor July 8, 2025

Sensor Processing

Detected by Pingoru
Jul 08, 2025, 03:39 PM UTC
Resolved
Jul 08, 2025, 08:13 PM UTC
Duration
4h 34m
Affected: SysTrack API/UISysTrack Endpoint Connections
Timeline · 5 updates
  1. investigating Jul 08, 2025, 03:39 PM UTC

    We are currently investigating this issue.

  2. identified Jul 08, 2025, 04:27 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 08, 2025, 06:48 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 08, 2025, 08:13 PM UTC

    This incident has been resolved. If you need further support, please open a ticket at the customer portal (https://customers.lakesidesoftware.com/).

  5. postmortem Jul 15, 2025, 03:46 PM UTC

    # What was the issue? Access to the SysTrack CE America’s cloud was slow due to sensor processing. # What was the root cause? Preliminary root cause, which is still being verified, was an Azure networking issue causing the utilization of our caching service to respond slowly to requests. This slowness caused cascading slowness to other areas of the platform. # What is the Prevention Strategy? 1. Running a large cache until other steps have been taken. **\(Completed\)** 2. Migrations to a different networking path to access the cache **\(Sept 2025\)** 3. Updates to how the system gets the cache information for recovery quicker **\(Oct 2025\)** 4. Updating the Sensor agent upload mechanism to implement resends or retries. **\(TBD\)**

Read the full incident report →