CloudBees incident

Auth0 Outage

Major Resolved View vendor source →

CloudBees experienced a major incident on April 20, 2021 affecting Auth0 Authentication API and Authentication and 1 more component, lasting 4h 4m. The incident has been resolved; the full update timeline is below.

Started
Apr 20, 2021, 04:21 PM UTC
Resolved
Apr 20, 2021, 08:26 PM UTC
Duration
4h 4m
Detected by Pingoru
Apr 20, 2021, 04:21 PM UTC

Affected components

Auth0 Authentication APIAuthenticationAuth0 Authentication APIAuth0 Authentication APIZendeskapp.cloudbees.com

Update timeline

  1. monitoring Apr 20, 2021, 04:21 PM UTC

    One of our third-party providers Auth0 for authentication is experiencing a major incident, we will monitor the outage and provide updates as services come back online

  2. monitoring Apr 20, 2021, 04:41 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Apr 20, 2021, 05:36 PM UTC

    CloudBees services currently impacted by Auth0 service outage include CloudBees Feature Management, CloudBees DevOptics, CloudBees Software Delivery Management, and the CloudBees Support Portal.

  4. monitoring Apr 20, 2021, 05:37 PM UTC

    Please email [email protected] for any CloudBees-related support. Related Auth0 status: https://status.auth0.com/incidents/zvjzyc7912g5

  5. monitoring Apr 20, 2021, 06:18 PM UTC

    We are continuing to monitor the issue and will provides updates as soon as possible.

  6. monitoring Apr 20, 2021, 07:01 PM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Apr 20, 2021, 07:35 PM UTC

    We are continuing to monitor for any further issues.

  8. monitoring Apr 20, 2021, 07:57 PM UTC

    You can now login to Cloudbees services including Cloudbees Feature management, Software Delivery Management, Devoptics and Support

  9. monitoring Apr 20, 2021, 08:23 PM UTC

    We are continuing to monitor for any further issues.

  10. monitoring Apr 20, 2021, 08:25 PM UTC

    We are continuing to monitor for any further issues.

  11. resolved Apr 20, 2021, 08:26 PM UTC

    This incident has been resolved.