Mar 2, 18:21 UTC
Resolved - Looks like everything is good. Thank you for your patience.

Mar 2, 18:15 UTC
Monitoring - The fix has gone out. We will continue to monitor the situation. Sorry for any inconvenience.

Mar 2, 17:59 UTC
Identified - We're seeing issues with docker on some convenience images (cimg:*) and a docker update we just pushed this morning. We are working on a fix and will let you know when we have more information. Thank you for your patience.

Feb 27, 00:17 UTC
Resolved - GitHub have acknowledged and resolved an incident affecting their platform.
https://www.githubstatus.com/incidents/vd3xqfq36rgm
Users should no longer experience intermittent checkout failures.

Feb 26, 22:57 UTC
Update - We are continuing to investigate this issue.

Feb 26, 22:56 UTC
Update - We are continuing to investigate this issue.

Feb 26, 22:50 UTC
Identified - Some users are currently experiencing inconsistent failures when checking out.
We believe this to be an issue with an upstream VCS provider and are investigating.

Feb 22, 19:05 UTC
Resolved - Our authentication provider has confirmed the earlier service disruption has been fully mitigated: https://status.auth0.com/incidents/kknl0nbdzbvx

Email/password login functionality has been restored and is operating normally.

Feb 22, 18:53 UTC
Monitoring - Our downstream authentication provider has implemented mitigation actions and is reporting a reduction in errors. We are seeing corresponding improvement in email/password login success rates. We are continuing to monitor closely to ensure stability before marking this incident resolved.

Feb 22, 17:37 UTC
Identified - We’ve identified that the issue affecting email/password sign-ins is caused by a degradation in service from our downstream authentication provider, Auth0: https://status.auth0.com/incidents/kknl0nbdzbvx

Users should still be able to sign in using GitHub or Bitbucket OAuth, which remain operational. We continue to monitor and will update as we learn more.

Feb 22, 17:25 UTC
Investigating - We are currently investigating an issue affecting users attempting to log in with email and password credentials. Sign-in via GitHub or Bitbucket OAuth is not affected and remains fully operational.

This issue appears to be related to an outage with a downstream authentication provider: https://status.auth0.com/

Feb 20, 17:44 UTC
Resolved - This incident has been resolved. Between approximately 16:00 UTC and 17:10 UTC, users may have experienced slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered.

Jobs and builds were not impacted during this time.

We apologize for the disruption and thank you for your patience.

Feb 20, 17:31 UTC
Monitoring - We have deployed a fix to stabilize internal services that were experiencing elevated load. Affected components are recovering and we are closely monitoring to confirm full resolution.

Users may still experience some residual slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered as systems continue to catch up and stabilize.

Jobs and builds remain unaffected and continue to run as expected.

We thank you for your patience while our engineers worked to stabilize the affected services. We will provide an update within 30 minutes or earlier.

Feb 20, 17:19 UTC
Identified - We have deployed a fix to stabilize internal services that were experiencing elevated load since approximately 16:00 UTC. Affected components appear to be recovering and we are closely monitoring the situation.

Users may still experience some slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered as systems continue to stabilize.

Jobs and builds remain unaffected and continue to run as expected.

We will provide our next update within 30 minutes or sooner if things change. We thank you for your patience while we continue to work to resolve this issue.

Feb 20, 16:56 UTC
Update - At approximately 16:00 UTC, we began seeing elevated load on internal data systems that serve read operations across CircleCI. This has resulted in degraded performance on the Pipelines page, difficulty loading historical workflow and pipeline data, and delays in GitHub commit status checks being posted.

Write operations and job execution are unaffected — builds are queuing and running as expected. We are actively working to stabilize affected internal services and restore full read performance across the platform.

We will provide an update within 30 minutes. Thank you for your patience while we work to investigate this issue

Feb 20, 16:25 UTC
Investigating - We are currently investigating two issues affecting CircleCI services. Users may experience slow load times on the Pipelines page and errors when attempting to view workflow details. Additionally, GitHub commit status checks may not be updating as expected for some users.

Builds and jobs are continuing to run and are not impacted at this time.

We will provide an update within 30 minutes. Thank you for your patience while we work to investigate this issue

Feb 17, 10:30 UTC
Resolved - From 11:48 to 17:16UTC some Bitbucket users may have experienced their organization not present in the CircleCI UI. Additionally some users may have encountered an issue when using `circleci config validate`. We identified the root cause of this issue and have since reverted the change. All systems for Bitbucket users are fully operational as of 17:16 UTC.

Feb 10, 16:13 UTC
Resolved - This incident has been resolved.

Feb 10, 15:54 UTC
Monitoring - We're recovered and are clearing up the backlog.

Feb 10, 15:42 UTC
Update - The issue has been identified and we are pushing out a fix. Thank you for your patience.

Feb 10, 15:41 UTC
Identified - The issue has been identified and we are pushing out a fix. Thank you for your patience.

Feb 10, 15:32 UTC
Update - We are continuing to investigate this issue.

Feb 10, 15:26 UTC
Update - We are continuing to investigate this issue.

Feb 10, 15:21 UTC
Investigating - We are investigating delays of jobs.
We will continue to update while investigating this.

Feb 9, 20:25 UTC
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:13 UTC
Update - Customers using Github may continue to experience delays in Pipelines & UI.

Feb 9, 20:05 UTC
Monitoring - We are starting to see some recovery and jobs are beginning to be triggered by Github again.

Feb 9, 19:59 UTC
Update - We are currently impacted by an ongoing Github outage. We will update once we have more information.

Feb 9, 19:48 UTC
Investigating - We will update as soon as we have more information

Feb 3, 18:58 UTC
Resolved - This incident has been resolved. Thank you for your patience.

Feb 3, 18:19 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, 17:46 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 2, 22:18 UTC
Resolved - The issue affecting email notifications has been resolved. Build completion emails and plan-related notifications are now being delivered normally. We apologize for any inconvenience this may have caused.

Feb 2, 22:05 UTC
Update - We are continuing to monitor for any further issues.

Feb 2, 22:05 UTC
Monitoring - Our upstream provider has resolved the issue affecting their system. We are currently monitoring email notification delivery to confirm full restoration. Build completion emails and plan-related notifications should begin flowing normally. All other notification types and build results through the CircleCI web interface and GitHub checks continue to function normally.

We will provide a final update within 15 minutes.

Feb 2, 21:48 UTC
Update - We are continuing to work with our upstream provider to restore email notification delivery. Build completion emails and plan-related notifications remain impacted. All other notification types and build results through the CircleCI web interface and GitHub checks continue to function normally.

We will provide an update within 30 minutes.

Feb 2, 21:12 UTC
Update - We continue to work with our vendor on restoring email notification delivery. Build completion emails and plan-related notifications remain impacted. All other notification types and build results through the CircleCI web interface and GitHub checks continue to function normally.

We will provide an update within 30 minutes.

Feb 2, 20:34 UTC
Identified - We have identified the issue affecting email notifications. Our notification delivery system is experiencing disruptions that are preventing build completion emails and plan-related notifications from being sent. We are actively working with our vendor to restore service. All other notification types, including Slack and webhook notifications, continue to function normally, and build results remain accessible through the CircleCI web interface and GitHub checks.

We will provide an update within 30 minutes.

Feb 2, 20:07 UTC
Investigating - We are currently experiencing issues with email notifications across CircleCI. Build completion emails and plan-related notifications are not being delivered as expected. All other notification types, including Slack and webhook notifications, continue to function normally. Build results remain accessible through the CircleCI web interface and GitHub checks.

We are actively investigating the issue with our notification delivery system and will provide an update within 30 minutes.

Jan 29, 19:37 UTC
Resolved - This incident has been resolved.

Jan 29, 19:35 UTC
Update - We are continuing to monitor for any further issues.

Jan 29, 19:35 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jan 29, 19:29 UTC
Identified - We are experiencing capacity constraints affecting arm-medium, large, xlarge, 2xl, resulting in job start delays of up to 5 minutes.

Current Status:
- arm-medium, large, xlarge, 2xl: Experiencing delays up to 5 minutes due to capacity constraints
- Docker, Mac, Windows, and Android jobs: Operating normally without delays

Our engineering team is actively working to address these constraints and expand available capacity. All jobs will continue to run normally after the initial delay.

We appreciate your patience as we work to resolve this issue. Next Update: Within 30 minutes or as the situation changes.