Users were unable to sign up or log in through auth.e2b.dev. Affected users encountered the error:

"We were unable to fetch the consent challenge associated to that request."

The issue originated with our third-party authentication provider, Ory.

• Multiple customers were affected in production.

• Users were unable to authenticate, preventing new sign-ups and logins.

• Duration: approximately 1 hour 19 minutes (10:00 AM–11:19 AM PDT).

• 10:00 AM PDT – First customer reports received.

• 10:07 AM PDT – Issue reproduced internally in production.

• 10:38 AM PDT – Investigation identified Ory as the source of the authentication failures.

• 11:19 AM PDT – Ory mitigated the issue and authentication functionality was fully restored.

The incident was caused by an outage or service degradation within Ory, our authentication provider. No changes or deployments on the E2B platform contributed to the incident.

Ory implemented a mitigation on their infrastructure, restoring normal authentication behavior. No changes were required on the E2B side.

• Follow up with Ory to obtain a detailed root cause analysis.

• Review any preventive measures or safeguards recommended by Ory.

• Evaluate additional monitoring and alerting around authentication failures.