Path LMS Outage History

10 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Path LMS Incident

Path LMS incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jul 30, 2026Degraded System PerformanceThe issue has been resolved and all outstanding items have been processed.22 minResolved
May 22, 2026Errors on Homepages for some accountsWe have deployed a fix for the issue and all pages are loading normally again. We apologize for the disruption, and have put in place improvements to ensure this issue does not occur again.46 minResolved
Apr 15, 2026Homepage errors for a subset of websitesThis incident is resolved.3 minResolved
Feb 18, 2026Brief Maintenance Window for Report Builder and DashboardsThe scheduled maintenance has been completed.1h 0mScheduled
Feb 10, 2026Investigating Email Deliverability IssuesThis has been resolved and all emails have been processed.67h 55mResolved
Jan 30, 2026Maintenance WIndow Scheduled for Report Builder and DashboardsThe maintenance has been completed.72h 0mScheduled
Jan 26, 2026Report Builder and Dashboard Data LagWe have identified a solution and will be completing the data propagation during a schedule maintenance window starting Friday, January 30th.28h 58mResolved
Jan 16, 2026System Maintenance WindowThe scheduled maintenance has been completed.2h 0mScheduled
Dec 18, 2025Admin page unavailableThe problem has been resolved and access to the Admin page has been restored. We will continue to monitor.24 minResolved
Nov 18, 2025Intermittent Site Loading IssuesThis incident has been resolved.1h 50mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Path LMS incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Path LMS Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Path LMS acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Path LMS outage in this window ran 3d, against a mean recovery of 17h 32m. If you depend on Path LMS in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.