IAM vendor status pages.
Official status pages for every major IAM vendor — Okta, Microsoft Entra, Auth0, Ping, Duo, CyberArk, SailPoint, JumpCloud — plus how to monitor IdP uptime and design for outages.
Where to check, by vendor.
- status.okta.comStatus
Okta
Workforce + Customer Identity Cloud (Auth0)
- status.cloud.microsoftStatus
Microsoft Entra
Entra ID, Conditional Access, External ID (via Microsoft 365 / Azure status)
- status.auth0.comStatus
Auth0 (Okta CIC)
Auth0 tenants by region (US, EU, AU, JP)
- status.pingidentity.comStatus
Ping Identity
PingOne, PingFederate Cloud, DaVinci
- status.duo.comStatus
Duo Security (Cisco)
Duo MFA + Admin Panel by deployment
- status.cyberark.cloudStatus
CyberArk
Identity Security Platform + Privilege Cloud
- status.sailpoint.comStatus
SailPoint
Identity Security Cloud by region
- status.jumpcloud.comStatus
JumpCloud
Directory, SSO, RADIUS, MDM
- status.onelogin.comStatus
OneLogin (One Identity)
OneLogin by region (US, EU)
- status.cloud.microsoftStatus
Microsoft 365
M365 sign-in + Entra (admin-center health is tenant-specific)
- health.aws.amazon.com/health/statusStatus
AWS (IAM Identity Center)
AWS IAM Identity Center via AWS Health
- status.cloud.google.comStatus
Google Cloud Identity
Cloud Identity + Workspace sign-in
Status URLs are the vendors' official pages and may change; we review this list quarterly. Always confirm against the vendor's own domain.
Designing for an IdP outage.
- Subscribe to every IdP status page your stack depends on — email + webhook so an incident reaches your on-call, not just a dashboard nobody watches.
- Run independent synthetic monitoring of your own login flow. A public status page reports the vendor's view; tenant- or region-specific degradation can hit you first.
- Map the cascade: when the IdP is down, what stops? PAM that federates to it, the cloud console, CI/CD OIDC, internal admin portals, vendor SaaS. Keep the map current.
- Maintain a tested break-glass procedure that does not depend on the IdP itself (do not require IdP SSO to reach the IdP support portal).
- Define RTO / RPO for the IdP as a critical dependency — regulators increasingly ask for it.
Common questions.
What is the Okta status page?+
Okta's official status page is status.okta.com — it reports real-time availability of Okta Workforce Identity, the Customer Identity Cloud (Auth0), and admin services, with incident history and the option to subscribe to updates by email, SMS, webhook, or RSS. It now covers Auth0 incidents as well, post-acquisition.
How do I monitor IAM vendor uptime?+
Subscribe to each vendor's status page (most support email, SMS, webhook, and RSS/Atom). For production resilience, also run independent synthetic monitoring of your own login flow — a vendor status page reports the vendor's view, which can lag a regional or tenant-specific degradation you experience first.
What happens to my apps when the IdP goes down?+
If your IdP is unavailable, new authentications fail — users with valid sessions/tokens keep working until those expire, but no new logins succeed, and anything that federates to the IdP (cloud consoles, SaaS, CI/CD OIDC) is affected. This is why operational-resilience targets (RTO/RPO) and a tested break-glass procedure matter for the IdP as a critical dependency.
Does an IdP status page tell me about my tenant specifically?+
Not always. Public status pages report broad/regional availability. Tenant- or region-specific degradation can affect you before (or without) a public incident being posted. Pair the status page with your own synthetic login monitoring for the truth about your environment.