We are experiencing a complete Auth0 AU region outage as of today 23 April 2026. All tenants on au.auth0.com are returning DNS_PROBE_FINISHED_NXDOMAIN. This affects both custom domains and raw tenant domains. Confirmed across multiple unrelated tenants: - igenchat.au.auth0.com (our tenant) - dev-immfg7q8ihx56zyx.au.auth0.com (our dev tenant) - foboh-prod.au.auth0.com (unrelated third-party tenant) DNS resolves correctly via dig but browsers and curl cannot reach any au.auth0.com endpoint. This is impacting production applications. Is there a known incident for the AU region? Status page shows no active incidents.
Hi @raja3
Welcome to the Auth0 Community!
Thank you for reporting this issue to us, we have experienced an outage yesterday that has affected the AU region, which has been resolved as per our Status Page, however some lingering effects could still be visible in some situations. As you have mentioned, currently we have no other report of an ongoing incident in the AU region, but please allow me to further investigate and see in case the behaviour that you are seeing is related to yesterday’s incident, or if happens to be a different one.
The DNS_PROBE_FINISHED_NXDOMAIN error message typically indicates that the DNS is not able to find the IP address that you are trying to reach, which in your case can likely be a server-side issue with the Auth0 server.
In the meantime, I will share some documentations and topics where the same error message was encountered and the issue resolved, in case these can help:
-
Setting Up Auth0 Custom Domains: A Complete Guide to DNS and SDK Configuration;
-
Auth0 login undefined/authorize?redirect → changes were made to the .env file and the solution was to stop the applications and run one more time with npm start;
-
React Sample APP login → a rule was misconfigured and did not allow multiple applications to run, this could be reflected via Actions, in case a new one has recently been deployed;
-
This site can’t be reachedCheck if there is a typo in undefined– Please help! → the documentation for the solution is our React Router 6 doc which outlines the steps to setup everything.
Please let us know if any of the above resources helped pin-point and resolve the issue, or if they helped in any way.
Best regards,
Gerald