Resolved -
Following GitHub's service recovery, all CircleCI functionality has returned to normal operation. Jobs are processing as expected across all resource classes.
Feb 9, 20:25 UTC
Update -
Customers using Github may continue to experience delays in Pipelines & UI.
Feb 9, 20:13 UTC
Monitoring -
We are starting to see some recovery and jobs are beginning to be triggered by Github again.
Feb 9, 20:05 UTC
Update -
We are currently impacted by an ongoing Github outage. We will update once we have more information.
Feb 9, 19:59 UTC
Investigating -
We will update as soon as we have more information
Feb 9, 19:48 UTC
Resolved -
This incident has been resolved. Thank you for your patience.
Feb 3, 18:58 UTC
Monitoring -
The capacity constraints affecting Linux and Remote Docker job execution have been mitigated. Jobs are now starting within expected timeframes. We continue to monitor the situation to ensure stability.
- What's impacted: Linux and Remote Docker job execution - working within normal parameters - What's happening: Service levels have returned to normal after implementing mitigation measures
We will provide an update within 15 minutes or sooner if conditions change. Thank you for your patience while our engineers worked to resolve this issue.
Feb 3, 18:19 UTC
Update -
We are continuing to work on a fix for this issue.
Feb 3, 17:46 UTC
Identified -
We have identified delays affecting Linux and Remote Docker job execution. Customers are currently experiencing approximately 3-6 minute delays for these jobs to start due to capacity constraints in our infrastructure provider. All other compute resource classes are operating normally.
We are actively mitigating this issue by routing a portion of traffic to an alternate region and continue working to restore normal service levels.
- What's impacted: Linux and Remote Docker job execution - What's happening: Jobs are experiencing 3-6 minute delays starting execution due to upstream capacity constraints
We will provide an update with 30 minutes. Thank you for your patience while we work to reduce these delays.
Feb 3, 17:46 UTC