YourSix experienced a minor incident on November 16, 2025 affecting Main application, lasting 19m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 16, 2025, 08:16 PM UTC
We are currently investigating an incident that is impacting the YourSix login service. Our team is actively working to understand the root cause and mitigate the issue. This incident is tied to a sub-processor issue that has been acknowledged by (Okta) Auth0 in US-3.
- monitoring Nov 16, 2025, 08:27 PM UTC
We have identified that this incident is solely related to errors from our sub-processor. Error rates being received by YourSix's sub-processor are clearing and logins are processing successfully. We will continue monitoring the incident and updates from the sub-processor.
- resolved Nov 16, 2025, 08:36 PM UTC
As of 20:13 UTC, error rates for login returned to healthy targets. This incident appears to be resolved. More details on the sub-processor incident can be found at: https://status.auth0.com/incidents/hykzwhgmgn8z We will continue monitoring error rates and communication from the sub-processor.
- postmortem Nov 17, 2025, 02:14 PM UTC
## Incident Post-Mortem: Main Application ### Summary On 11/16/2025 at 19:36 UTC, YourSixOS experienced an authentication disruption caused by an issue with Auth0, our identity provider. During this window, some users were unable to log in or experienced intermittent authentication failures. The issue was fully resolved at 20:31. ### Impact * Affected services: Main Application * User impact: * Users may have been unable to log in * API calls requiring fresh tokens may have failed * Duration: 55 minutes ### Root Cause Auth0 experienced a temporary service degradation affecting authentication transactions. This resulted in failed or delayed token issuance for customers relying on Auth0-hosted login. ### Resolution Once the issue was identified, we monitored Auth0’s status and error responses. Service returned to normal after Auth0 mitigated the underlying issue. No action was required on the customer side. ### Preventive Actions / Next Steps * Reviewing session caching mechanisms and timers * Continuing to coordinate with Auth0 to ensure timely updates on future issues ### Current Status All services are fully operational. We will continue to monitor system performance closely.