After: We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.
AddedUpdateidentified#8
Before: not present
After: We have identified the cause, and have performed a rollback. We will provide further updates with changes in the incident status and as our mitigation efforts progress.
AddedUpdatemonitoring#9
Before: not present
After: The Auth0 Engineering team has applied a fix for the issue and we're monitoring the environment to ensure stability.
AddedUpdateresolved#10
Before: not present
After: Services have been restored. A root cause analysis (RCA) will be posted here within 7 business days. We sincerely apologize for the impact this had on you and your users.
AddedUpdatepostmortem#11
Before: not present
After: A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-08-27_-_Increased_Error_Rates_in_US-3_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/2026-08-27_-_Increased_Error_Rates_in_US-3_Public_Cloud_Environment.pdf)
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.