Salto KS Outage History

17 incidents recorded over the last 365 days, 17 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.

Live Salto KS status100.00% uptime history

Every Recorded Salto KS Incident

Salto KS incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 8, 2026Service Access management seems to be down21 minResolved
Oct 7, 2026Service Access management seems to be down20 minResolved
Oct 1, 2026Service Login and Authentication Services seems to be down4 minResolved
Sep 21, 2026Service Login and Authentication Services seems to be down2 minResolved
Sep 21, 2026Database Maintenance1h 0mResolved
Sep 17, 2026Activity Log - Degraded performance15h 11mResolved
Sep 15, 2026Service Login and Authentication Services seems to be down4 minResolved
Aug 31, 2026Service Event Processing and Notifications seems to be down1h 23mResolved
Aug 30, 2026Service Event Processing and Notifications seems to be down3 minResolved
Aug 28, 2026Service Login and Authentication Services seems to be down3 minResolved
Aug 28, 2026Service Login and Authentication Services seems to be down5 minResolved
Aug 27, 2026Service Login and Authentication Services seems to be down5 minResolved
Aug 27, 2026Investigate possible access sync problems2h 28mResolved
Aug 4, 2026Database Maintenance1h 15mResolved
Jul 20, 2026Service Login and Authentication Services seems to be down334h 21mResolved
Jul 14, 2026Service Access management seems to be down496h 36mResolved
Jul 13, 2026Service Login and Authentication Services seems to be down512h 29mResolved

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 Salto KS 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 Salto KS 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 Salto KS 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 Salto KS outage in this window ran 21d 8h, against a mean recovery of 3d 8h. If you depend on Salto KS 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.