Hi - I have just signed up for the Free Plan. I am setting up my app. I checked your service status and it appears that you do have times where you go down. For the app I am building, it is time sensitive. Seems your Australia API is rather stable..and so is Canada. Should I be setting up my stuff on those APIs? Or is there a failover so that our users can continue to sign in?

Hi, I'm Descope's AI assistant. I've put together an initial response below based on your question. --- ### Important Clarifications: 1. Regional APIs Are Tied to Your Project's Region - The AU (

<http://api.aps2.descope.com|api.aps2.descope.com>

) and CA (

<http://api.cac1.descope.com|api.cac1.descope.com>

) regional APIs are not interchangeable fallbacks. Each Descope project is hosted in one region, and all API requests must use the base URL for that specific region. You cannot switch to a different regional API to route around downtime. 2. Multi-Region Requires a Paid Plan - Region selection (US, EU, AU, CA) is only available on the Growth or Enterprise plan. On the Free Plan, your project is hosted in the default US region — you cannot choose AU or CA. 3. There Is No Automatic Failover - Descope does not provide an automatic cross-region failover mechanism. If you need high availability across regions, the recommended approach is a multi-region architecture — running separate Descope projects per region — but this requires significant setup and a paid plan. ### Recommended Next Steps: • If the app is time-sensitive and availability is critical, consider upgrading to Growth or Enterprise to access multi-region support and discuss your architecture needs with Descope. ### Additional Resources: • Multi-Region Architecture | Descope Documentation • Multi-Region Support | Descope Documentation • Descope Pricing

Anand, all regions are treated the same, and actually running on AWS USE1 has been proven to be no less reliable than the others. Have a look at descopestatus.com. From an authentication perspective, we maintain>99.99% availability, and as you can see, the most recent issues were related to non-authentication APIs.

Thanks