← Back to Auth0 History
major✓ Resolved
We have detected an issue.
Status
resolved
Duration
2h 40m
Updates
6
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
resolved
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2026-07-14\_-\_Tenant\_Logs\_Impacted\_on\_US-1\_Public\_Cloud\_Environment.pdf](https://cdn.auth0.com/blog/2026-07-14_-_Tenant_Logs_Impacted_on_US-1_Public_Cloud_Environment.pdf)
resolved
Services have been restored. We sincerely apologize for the impact this had on you and your users.
identified
We are continuing to investigate the root cause in our tenant logs streaming service. The tenant logs are accessible via Auth0 management dashboard. We will provide next update at 7am UTC with any changes in the incident status and as our mitigation efforts progress. This issue is not impacting any core authentication services.
identified
We have identified an issue with our tenant logs streaming service. We are continuing to investigate the root cause and will provide further updates with changes in the incident status and as our mitigation efforts progress. This issue is not impacting any core authentication services.
identified
We have identified an issue with our tenant logs streaming service. We will provide further updates with changes in the incident status and as our mitigation efforts progress.
investigating
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.
📊 TECHNICAL DETAILS
Internal ID
ef760299-a7dd-4999-ba14-cf1629273fad
External ID
2nz8nfffj7vy
🕐 Started
🔄 Last Updated
✓ Resolved
MAJOR
Impact Level
2h 40m
Total Duration
6
Status Updates
Affected Components
US-1 / Tenant Logs
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed