Lansweeper Outage History

8 incidents recorded over the last 365 days, 8 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 Lansweeper Incident

Lansweeper incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 17, 2026Planned Maintenance2h 0mResolved
Oct 7, 2026US Sites is down14 minResolved
Oct 7, 2026Emergency Maintenance - Authentication Provider51 minResolved
Sep 30, 2026Scanning Configuration information may take some time to update19h 32mResolved
Sep 29, 2026Assets appearing duplicated69h 16mResolved
Sep 27, 2026Planned maintenance - Network1h 41mResolved
Aug 29, 2026Database maintenance1h 44mResolved
Aug 26, 2026Asset list and asset details may not load or open1h 52mResolved

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 Lansweeper 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 Lansweeper 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 Lansweeper 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 Lansweeper outage in this window ran 2d 21h, against a mean recovery of 12h 9m. If you depend on Lansweeper 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.