API Response Times for Authentication and Management APIs

Problem Statement:

We need to have the API response times for authentication and management APIs. Is this documented and part of your SLA?

Solution:

Our SLA covers availability but not the response times.

https://auth0.com/docs/troubleshoot/customer-support/services-level-descriptions

For Private Cloud Customer:

We have periodic internal tests for each private cloud release to detect regressions. Still, the results from these tests may not give the proper indication of what you may observe as the latency has many contributing factors that may be different in your setup. E.g.,

1- The customization in the tenant, like the rules/hooks/actions, and custom DB login scripts.
2- The hosted page code and scripts.
3- The used authentication flow.
4- The number of users in the tenant.
5- The applied load.
6- The network latency between the test environment to the Auth0 servers.
7- The private cloud type (Basic, Performance, Performance Plus)

As a better idea, I suggest performing a load test on your end, and if you notice any unacceptably long delays, we can investigate how to improve it.

To perform a load test, we have a process. The related public documentation is the following. For our private cloud customers, we are quicker to approve the tests; still, we require the same information to be shared before testing.

https://auth0.com/docs/troubleshoot/customer-support/operational-policies/load-testing-policy

For Enterprise Public Cloud Customer:

We have periodic internal tests to detect regressions. Still, the results from these tests may not give the proper indication of what you may observe as the latency has many contributing factors that may be different in your setup. E.g.,

1- The customization in the tenant, like the rules/hooks/actions, and custom DB login scripts.
2- The hosted page code and scripts.
3- The used authentication flow.
4- The number of users in the tenant.
5- The applied load.
6- The network latency between the test environment to the Auth0 servers.

As a better idea, I suggest performing a load test on your end, and if you notice any unacceptably long delays, we can investigate how to improve it. To perform a load test, we have a process. The related documentation is the following.

https://auth0.com/docs/troubleshoot/customer-support/operational-policies/load-testing-policy

For Low Paid Public Cloud Customer:

We have periodic internal tests to detect regressions. Still, the results from these tests may not give the proper indication of what you may observe as the latency has many contributing factors that may be different in your setup. E.g.,

1- The customization in the tenant, like the rules/hooks/actions, and custom DB login scripts.
2- The hosted page code and scripts.
3- The used authentication flow.
4- The number of users in the tenant.
5- The applied load.
6- The network latency between the test environment to the Auth0 servers.

A load test could help to find the average latency. We allow load testing for our enterprise customers. If it can be an option for you to upgrade your plan to Enterprise you may perform a load test. The detailed load test policy is available here:

https://auth0.com/docs/troubleshoot/customer-support/operational-policies/load-testing-policy