OneLogin Outage History

11 incidents recorded over the last 365 days, 11 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 OneLogin status99.90% uptime history

Every Recorded OneLogin Incident

OneLogin incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jul 27, 2026OneLogin services experiencing Degraded performance190h 38mResolved
Jul 8, 2026Issue with Single Sign-On Services.A configuration change intended for the standby clusters was inadvertently propagated to the active cluster. The change was identified and reverted immediately.3 minResolved
May 27, 2026OneLogin Support PortalThe issue has been resolved.4h 43mResolved
May 27, 2026OneLogin Support PortalThe issue has been resolved.4h 43mResolved
May 25, 2026OneLogin Smart Hooks Degraded Performance1699h 25mResolved
Apr 20, 2026Marketing and Status WebsiteIssue is resolved and status page is available now1h 25mResolved
Apr 20, 2026Marketing and Status WebsiteIssue is resolved and status page is available now1h 39mResolved
Apr 16, 2026OneLogin Single Sign on Services experiencing Service Disruption in US RegionOneLogin engineers have confirmed that all the services are restored and operational as expected.2h 3mResolved
Apr 14, 2026OneLogin Admin Services Degraded PerformanceIncident is resolved now54 minResolved
Apr 7, 2026OneLogin Support Portal degraded performanceIssue is resolved now and Support Portal is available2h 19mResolved
Apr 7, 2026OneLogin Support Portal degraded performanceIssue is resolved now and Support Portal is available2h 20mResolved

How to Read This OneLogin 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 OneLogin 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 OneLogin outage in this window ran 70d 19h, against a mean recovery of 7d 5h. If you depend on OneLogin 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.