Skip to main content

Is OneLogin Down?

OneLogin is responding, but blocks automated checks

When we last reached OneLogin directly, it answered and refused us — origin returns an empty bot-challenge response. An answer is proof the origin was serving traffic, but it measures our access, not the service, so we publish no percentage.

Last checked · checks run every 6 hours

Official status page: https://www.onelogin.com/status

Why there is no uptime figure on this page

The last time we fetched OneLogin's page directly, the origin answered and turned our client away rather than serving the page. That answer tells us the origin was reachable and responding, but it is a response about our automation, not about whether OneLogin works for you.

A percentage built from those checks would measure our own access, so we do not publish one. What this page does show is each region's most recent result and OneLogin's own status feed, which you can weigh yourself.

30-day history

Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: blocked from automated checks
Aug 17: blocked from automated checks
Aug 18: blocked from automated checks
Aug 19: blocked from automated checks
Aug 20: blocked from automated checks
Aug 21: blocked from automated checks
Aug 22: blocked from automated checks
Aug 23: blocked from automated checks
Aug 24: no data
Jul 26 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
edge reachable

A static asset loaded in 19ms. That proves the edge is up, but not that the site works.

arn
edge reachable

A static asset loaded in 21ms. That proves the edge is up, but not that the site works.

bom
edge reachable

A static asset loaded in 23ms. That proves the edge is up, but not that the site works.

cdg
edge reachable

A static asset loaded in 22ms. That proves the edge is up, but not that the site works.

dfw
edge reachable

A static asset loaded in 18ms. That proves the edge is up, but not that the site works.

sin
edge reachable

A static asset loaded in 20ms. That proves the edge is up, but not that the site works.

sjc
edge reachable

A static asset loaded in 24ms. That proves the edge is up, but not that the site works.

syd
edge reachable

A static asset loaded in 21ms. That proves the edge is up, but not that the site works.

yyz
edge reachable

A static asset loaded in 40ms. That proves the edge is up, but not that the site works.

What OneLogin does

OneLogin is a single sign-on and directory service that brokers employee access to cloud applications. Staff authenticate once and reach everything provisioned to them without separate passwords. It is now sold under the One Identity brand. Like any identity provider, it is a dependency for logging in rather than something people spend their day inside.

What an outage looks like

The portal fails to load, or credentials are accepted and the application list never appears. Applications reached through OneLogin return SAML errors or redirect loops back to the login screen. People already holding an application session usually continue working, so the effect builds through the morning as sessions expire rather than arriving all at once.

What to do about it

Check www.onelogin.com/status for the incident and your region. Avoid signing out of anything that still works, because a live application session normally survives an identity outage and cannot be recovered once dropped. Administrators should reach for a break-glass account that authenticates outside OneLogin; if none exists, note it for the post-incident review.

Is it down for everyone, or just you?

If this page says OneLogin is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

OneLogin outage FAQ

Will I lose access to applications I am already signed in to?
Usually not straight away. Applications accept an existing session until it expires, so people already working keep working. What breaks is fresh authentication: a new login, a new device, or a session that happens to time out mid-incident. That is why signing out during a OneLogin outage is worth avoiding.
Is it OneLogin or the application that is broken?
Check whether other applications behind the same sign-on still accept new logins. If several fail together, the identity provider is the common factor. If exactly one fails while others are fine, the fault is more likely that application's SAML configuration or its own availability. The status page settles the question either way.
How do administrators get in during a OneLogin outage?
Through an account that authenticates locally rather than through OneLogin. Most organisations create one deliberately so an identity incident does not lock them out of their own console. Where the outage is partial, the administration interface sometimes stays reachable while user-facing sign-on fails, so it is worth trying before escalating.
Does a OneLogin outage affect Okta or Duo?
No. These are separate platforms run by different companies, each with its own status page. Organisations sometimes chain them, using Duo as a second factor behind a OneLogin login, and in that arrangement either one failing blocks access. Check them independently rather than treating one status page as covering the others.

How we measure this

  • We request OneLogin's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where OneLogin publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it — and when OneLogin blocks our checks entirely, we report the vendor's own status directly.

Get alerted when OneLogin goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required