- Detected by Pingoru
- Feb 22, 2026, 05:25 PM UTC
- Resolved
- Feb 22, 2026, 07:05 PM UTC
- Duration
- 1h 40m
Timeline · 4 updates
-
investigating Feb 22, 2026, 05:25 PM UTC
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/
-
identified Feb 22, 2026, 05:37 PM UTC
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.
-
monitoring Feb 22, 2026, 06:53 PM UTC
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.
-
resolved Feb 22, 2026, 07:05 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 04:25 PM UTC
- Resolved
- Feb 20, 2026, 05:44 PM UTC
- Duration
- 1h 18m
Affected: CircleCI UINotifications & Status Updates
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Feb 17, 2026, 08:22 PM UTC
- Resolved
- Feb 17, 2026, 10:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 17, 2026, 08:22 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 03:21 PM UTC
- Resolved
- Feb 10, 2026, 04:13 PM UTC
- Duration
- 51m
Affected: Docker Jobs
Timeline · 7 updates
-
investigating Feb 10, 2026, 03:21 PM UTC
We are investigating delays of jobs. We will continue to update while investigating this.
-
investigating Feb 10, 2026, 03:26 PM UTC
We are continuing to investigate this issue.
-
investigating Feb 10, 2026, 03:32 PM UTC
We are continuing to investigate this issue.
-
identified Feb 10, 2026, 03:41 PM UTC
The issue has been identified and we are pushing out a fix. Thank you for your patience.
-
identified Feb 10, 2026, 03:42 PM UTC
The issue has been identified and we are pushing out a fix. Thank you for your patience.
-
monitoring Feb 10, 2026, 03:54 PM UTC
We're recovered and are clearing up the backlog.
-
resolved Feb 10, 2026, 04:13 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 07:48 PM UTC
- Resolved
- Feb 09, 2026, 08:25 PM UTC
- Duration
- 36m
Affected: GitHub Git OperationsGitHub Pull RequestsGitHub PackagesGitHub Webhooks
Timeline · 5 updates
-
investigating Feb 09, 2026, 07:48 PM UTC
We will update as soon as we have more information
-
investigating Feb 09, 2026, 07:59 PM UTC
We are currently impacted by an ongoing Github outage. We will update once we have more information.
-
monitoring Feb 09, 2026, 08:05 PM UTC
We are starting to see some recovery and jobs are beginning to be triggered by Github again.
-
monitoring Feb 09, 2026, 08:13 PM UTC
Customers using Github may continue to experience delays in Pipelines & UI.
-
resolved Feb 09, 2026, 08:25 PM UTC
Following GitHub's service recovery, all CircleCI functionality has returned to normal operation. Jobs are processing as expected across all resource classes.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 05:46 PM UTC
- Resolved
- Feb 03, 2026, 06:58 PM UTC
- Duration
- 1h 11m
Affected: Machine Jobs
Timeline · 4 updates
-
identified Feb 03, 2026, 05:46 PM UTC
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.
-
identified Feb 03, 2026, 05:46 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Feb 03, 2026, 06:19 PM UTC
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.
-
resolved Feb 03, 2026, 06:58 PM UTC
This incident has been resolved. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 08:07 PM UTC
- Resolved
- Feb 02, 2026, 10:18 PM UTC
- Duration
- 2h 11m
Affected: Notifications & Status Updates
Timeline · 7 updates
-
investigating Feb 02, 2026, 08:07 PM UTC
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.
-
identified Feb 02, 2026, 08:34 PM UTC
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.
-
identified Feb 02, 2026, 09:12 PM UTC
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.
-
identified Feb 02, 2026, 09:48 PM UTC
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.
-
monitoring Feb 02, 2026, 10:05 PM UTC
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.
-
monitoring Feb 02, 2026, 10:05 PM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 02, 2026, 10:18 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 07:29 PM UTC
- Resolved
- Jan 29, 2026, 07:37 PM UTC
- Duration
- 7m
Affected: Machine Jobs
Timeline · 4 updates
-
identified Jan 29, 2026, 07:29 PM UTC
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.
-
monitoring Jan 29, 2026, 07:35 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jan 29, 2026, 07:35 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jan 29, 2026, 07:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2026, 06:30 PM UTC
- Resolved
- Jan 12, 2026, 06:08 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 12, 2026, 06:30 PM UTC
We identified and resolved an issue that caused jobs to be delayed. During this period, some customers experienced longer than normal job start times while we performed database optimization work. Our team has completed the necessary tuning and service performance has returned to normal levels. We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 11:23 AM UTC
- Resolved
- Jan 09, 2026, 11:25 PM UTC
- Duration
- 1d 12h
Affected: Pipelines & Workflows
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Dec 16, 2025, 09:17 PM UTC
- Resolved
- Dec 16, 2025, 10:12 PM UTC
- Duration
- 54m
Affected: Machine JobsmacOS Jobs
Timeline · 4 updates
-
investigating Dec 16, 2025, 09:17 PM UTC
Customers using Machine, Linux Remote Docker, and Mac resource classes may be experiencing elevated wait times when starting jobs. We're investigating and will update again soon.
-
identified Dec 16, 2025, 09:49 PM UTC
We've ID'd the problem and we're rolling out a fix.
-
monitoring Dec 16, 2025, 10:00 PM UTC
Wait times for Linux, Remote Docker and Mac are starting to return to normal. We're going to keep our eye on things for just a bit longer and will update again shortly.
-
resolved Dec 16, 2025, 10:12 PM UTC
This incident has been resolved and wait times have returned to normal. We appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 09:59 PM UTC
- Resolved
- Dec 15, 2025, 09:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 15, 2025, 09:59 PM UTC
Between 21:14 and 21:26 UTC, December 15, 2025, customers using Machine, Linux Remote Docker, and ARM resource classes experienced elevated wait times when starting jobs. Wait times reached up to 5 minutes during this period due to the delays in our infrastructure scaling to meet the demand. The issue has been resolved and wait times have returned to normal levels. Jobs are now starting within expected timeframes. No further action is required from customers, and no jobs were lost during this incident. Thank you for your patience during this brief disruption.
Read the full incident report →
- Detected by Pingoru
- Dec 12, 2025, 05:22 PM UTC
- Resolved
- Dec 12, 2025, 07:07 PM UTC
- Duration
- 1h 45m
Affected: CircleCI Insights
Timeline · 3 updates
-
investigating Dec 12, 2025, 05:22 PM UTC
We are currently investigating an issue affecting Usage API data availability for December 11, 2025. Customers querying usage data for this date will not receive results at this time. Usage data prior to December 11 remains accessible and unaffected. This issue is isolated to data retrieval for the specified date. All other CircleCI functionality, including job execution and workflow triggering, continues to operate normally. We are actively investigating the cause and will provide our next update within 30 minutes or as we know more.
-
identified Dec 12, 2025, 05:49 PM UTC
The issue has been identified. Expected time to resolution: 90 minutes
-
resolved Dec 12, 2025, 07:07 PM UTC
The Usage API issue has been resolved. Data is loaded for yesterday 12/11. Thank you for your patience.
Read the full incident report →
Critical December 4, 2025 - Detected by Pingoru
- Dec 04, 2025, 10:53 PM UTC
- Resolved
- Dec 05, 2025, 12:15 AM UTC
- Duration
- 1h 22m
Affected: Docker JobsMachine JobsmacOS JobsWindows Jobs
Timeline · 4 updates
-
investigating Dec 04, 2025, 10:53 PM UTC
We're currently investigating a high number of infra failures. We'll update as soon as we know more details.
-
identified Dec 04, 2025, 11:36 PM UTC
We are slowly returning to normal. If you had jobs that failed with "infra-fail", those jobs can be rerun. We thank you for your patience while our engineers worked to get our system back to stability.
-
monitoring Dec 05, 2025, 12:06 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 05, 2025, 12:15 AM UTC
The incident has been resolved. Thank you for your patience. The "infra-fail" should no longer be occurring.
Read the full incident report →
- Detected by Pingoru
- Dec 04, 2025, 04:04 PM UTC
- Resolved
- Dec 04, 2025, 05:49 PM UTC
- Duration
- 1h 45m
Affected: macOS Jobs
Timeline · 5 updates
-
identified Dec 04, 2025, 04:04 PM UTC
We have identified an issue in our system which mean that MacOS jobs which don't specify a resource class will fail to run with an "Invalid resource class" error. We are working to correct this, but customers can workaround this by specifying a resource class in their config.yml.
-
identified Dec 04, 2025, 04:29 PM UTC
We have mitigated the issue and MacOS jobs which do not have a resource class specified should run normally. Customers can rerun jobs which failed an they should now run normally without any modification to their config. Thank you for your patience whillst we resolved this. Customers using M4 machine jobs may experience minor delays in jobs starting during this period as there are a large number of re-runs occurring.
-
identified Dec 04, 2025, 05:19 PM UTC
We are continuing to see recovery, but some customers may still experience delays in jobs running on M4 executors. We appreciate your patience whilst we work through the backlog of jobs.
-
monitoring Dec 04, 2025, 05:43 PM UTC
All jobs should now be running normally. The backlog of jobs has cleared and jobs should be running in typical time. We will continue monitoring to ensure consistent service. Thank you for your patience.
-
resolved Dec 04, 2025, 05:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 09:31 PM UTC
- Resolved
- Dec 03, 2025, 09:58 PM UTC
- Duration
- 27m
Affected: CircleCI UI
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 09:28 PM UTC
- Resolved
- Dec 03, 2025, 11:48 PM UTC
- Duration
- 2h 19m
Affected: Pipelines & Workflows
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 04:53 PM UTC
- Resolved
- Dec 03, 2025, 06:12 PM UTC
- Duration
- 1h 18m
Affected: Pipelines & Workflows
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 01:37 PM UTC
- Resolved
- Dec 03, 2025, 03:30 PM UTC
- Duration
- 1h 52m
Affected: CircleCI UI
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Dec 02, 2025, 02:00 AM UTC
- Resolved
- Dec 02, 2025, 02:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 03, 2025, 04:01 PM UTC
Between Dec 2, 2025 16:20 UTC and Dec 3, 2025 14:27 UTC, a change deployed to our workflow execution system caused duplicate notifications to be sent to some customers and triggered unexpected auto-reruns for a small number of projects. Impact: - Some customers received multiple failure notification emails for the same workflow. - The number of duplicate notifications varied based on how many jobs in the workflow were affected (e.g., marked skipped or cancelled). - A subset of customers may have received duplicate Slack notifications. - A small number of projects experienced duplicated auto-reruns. The issue has been fully mitigated, and notification behavior has returned to normal. We appreciate your patience while our team resolved this issue.
Read the full incident report →
- Detected by Pingoru
- Nov 26, 2025, 10:53 PM UTC
- Resolved
- Nov 26, 2025, 11:24 PM UTC
- Duration
- 31m
Affected: macOS Jobs
Timeline · 2 updates
-
identified Nov 26, 2025, 10:53 PM UTC
We are seeing an increase in wait times to start jobs on Mac M1 Large. Customers are encouraged to move workloads to Mac M4 if possible.
-
resolved Nov 26, 2025, 11:24 PM UTC
We are in the process of deprecating our M1 fleet due to limited machine capacity. So while all jobs will run, some running on M1 Large may be delayed. Customers may move to M1 Medium if you must have an M1 chip. Otherwise we encourage customers to move to M2 and M4 resource classes. Thank you for patience and we apologize for any inconvenience.
Read the full incident report →
- Detected by Pingoru
- Nov 26, 2025, 03:50 PM UTC
- Resolved
- Nov 26, 2025, 04:28 PM UTC
- Duration
- 38m
Affected: Machine Jobs
Timeline · 3 updates
-
investigating Nov 26, 2025, 03:50 PM UTC
We are currently experiencing issues with certain resource classes for Machine Executors.
-
monitoring Nov 26, 2025, 04:06 PM UTC
We've identified the issue, and have rolled out a fix. We are now monitoring. To our affected customers, thank you for your patience as we got this resolved.
-
resolved Nov 26, 2025, 04:28 PM UTC
All Machine resource classes are operating successfully. Thank you for your patience, and we apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Nov 25, 2025, 04:10 PM UTC
- Resolved
- Nov 25, 2025, 04:10 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 25, 2025, 04:30 PM UTC
There was a short issue from 16:10 UTC to 16:13 UTC which meant that we did not successfully trigger some jobs. If you expected a job to run which did not within the last 30 minutes you should attempt to run the job manually or attempt to trigger the job again. (For example, by pushing to your repository).
Read the full incident report →
- Detected by Pingoru
- Nov 22, 2025, 01:15 AM UTC
- Resolved
- Nov 22, 2025, 01:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 22, 2025, 01:15 AM UTC
Between 20:20 and 20:26 UTC, following our scheduled RabbitMQ maintenance, a small number of workflows may have experienced issues with GitHub check notifications. Impact: - Some workflows showed no check run status in GitHub - Some workflows showed check runs stuck in "pending" state - User flows requiring these checks may have been blocked Resolution: This issue resolved upon completion of our maintenance. All services are now operating normally. We apologize for any inconvenience during this maintenance period. If you have builds that completed during this window with pending or missing checks, a rerun will restore the correct status.
Read the full incident report →
- Detected by Pingoru
- Nov 20, 2025, 03:58 PM UTC
- Resolved
- Nov 20, 2025, 04:08 PM UTC
- Duration
- 9m
Affected: macOS Jobs
Timeline · 2 updates
-
investigating Nov 20, 2025, 03:58 PM UTC
We are investigating delays in M4 and M1 Mac jobs, and are working on resolving this as soon as possible. Thank you for your patience.
-
resolved Nov 20, 2025, 04:08 PM UTC
Mac M4 and M1 jobs are now running normally. Thank you again for your patience while we addressed this issue.
Read the full incident report →
