Lakeside Software incident

SIP Slowness

Minor Resolved View vendor source →

Lakeside Software experienced a minor incident on May 9, 2025 affecting SysTrack API/UI and SysTrack API/UI, lasting 2h 40m. The incident has been resolved; the full update timeline is below.

Started
May 09, 2025, 03:45 PM UTC
Resolved
May 09, 2025, 06:26 PM UTC
Duration
2h 40m
Detected by Pingoru
May 09, 2025, 03:45 PM UTC

Affected components

SysTrack API/UISysTrack API/UI

Update timeline

  1. identified May 09, 2025, 04:37 PM UTC

    The SIP addon to SysTrack CE is experience slowness due to an underlay Microsoft Cloud issue (Tracking Code LSLX-3WG)

  2. identified May 09, 2025, 05:58 PM UTC

    We are seeing improvements in responses but we are still waiting for Microsoft to clear the incident.

  3. resolved May 09, 2025, 06:26 PM UTC

    Microsoft Azure has completely mitigated the issue. Please contact support if you have an future concerns.

  4. postmortem May 23, 2025, 04:54 PM UTC

    # What was the issue? Portions of SIP were non-operational and returned error code 500. # What was the root cause? Between 13:30 UTC and 17:45 UTC on 09 May 2025, Microsoft Azure OpenAI Service stopped responding to requests. # What is the Prevention Strategy? 1. Microsoft has posted its RCA and has provided multiple remediation steps for when the Azure OpenAI Service is not responding. \(Tracking Code: LSLX-3WG\) 2. Lakeside is adding additional internal alerts for when Microsoft Azure OpenAI Service is not responding. \(7/1\)