Availability & Trust

We know that if you can't log in to your app, nothing else works. At web scale in the cloud, failures and outages occur. That's why we have architected Auth0 to be highly resilient to the failure of any of its components, with the goal that your users never experience any downtime.

How it Works?

At a high level, our availability strategy is rather simple, and yet very effective: we ensure that critical dependencies are redundant, we rapidly detect failures, and our failover is very quick. The Auth0 architecture implements redundant components at all levels. These are:

  • DNS
  • Datacenter
  • Application layer
  • Storage

Our High-Availability Strategy

We've done many things to ensure extra availability. An important aspect is how the application is architected: That is, how we manage user sessions, how we partition functionality, how we prioritize the availability of modules, and how we handle transient conditions

Auth0 is designed and built as a scalable, highly available, multi-tenant cloud service.

This highly reliable architecture is combined with solid operational processes and a culture of continuous improvement that constantly refines and improves Auth0 operations.

Auth0 Availability Diagram

Consider the following scenarios:

  • If one of the VMs is taken down, the load balancer will take it off rotation until it's up again.
  • If one of the database VMs is taken down, the secondary VM is elected as primary.
  • If there is an outage on the primary datacenter, the DNS will detect that and start redirecting requests to the second datacenter (in a different location).

Appliance Gives More Control to our Customers

We know there are scenarios where a public cloud-based solution is not acceptable---for example, due to compliance or legal requirements. For these cases, Auth0 is available as an appliance to be deployed in a private environment. The Auth0 architecture makes this possible: scaling down a cloud service to become a server. With traditional monolithic identity infrastructure implementations, the opposite is a very hard - or even impossible - task.

Continuous Deployment

Continuous Deployment with No DowntimeWe continuously improve Auth0. Whether we have to update a tutorial, optimize the performance of a module, or launch a whole new feature, on a typical day we might deploy three or four times. We designed our deployment infrastructure to do this with no planned downtime.

Auth0 Service Status

Auth0 StatusWe monitor our infrastructure from over 50 locations all over the world. Our availability is published instantly on status.auth0.com, and if there ever is an incident, we'll let you know immediately through Twitter. You can also check our uptime reports by clicking here.

For questions, please contact us at trust@auth0.com