Snapshot 15290
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"pages": [
{
"end_time": "2026-09-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "zxqlp0926vcz",
"impact": "none",
"message": "This incident has been resolved.",
"name": "Delays in processing new signups and plan changes",
"timestamp": "Sep \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e18:13\u003c/var\u003e - \u003cvar data-var='time'\u003e20:06\u003c/var\u003e UTC"
},
{
"code": "3kx4rv23998z",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Delays starting Linux Machine jobs",
"timestamp": "Sep \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e16:22\u003c/var\u003e - \u003cvar data-var='time'\u003e17:09\u003c/var\u003e UTC"
},
{
"code": "3lnp36dwl73z",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Customers may experience delays in UI updates",
"timestamp": "Sep \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e14:55\u003c/var\u003e - \u003cvar data-var='time'\u003e19:30\u003c/var\u003e UTC"
},
{
"code": "ynpn1xvjsx86",
"impact": "minor",
"message": "The incident impacting pipeline data in the UI has now been resolved. We thank you for your patience while our engineers worked on reducing the delays.",
"name": "Customers may experience delays in UI updates",
"timestamp": "Sep \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e14:42\u003c/var\u003e - \u003cvar data-var='time'\u003e17:02\u003c/var\u003e UTC"
},
{
"code": "q7z4zxl8mf24",
"impact": "minor",
"message": "Wait times for macOS jobs are back to normal.",
"name": "Increased wait times for macOS jobs",
"timestamp": "Sep \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e11:59\u003c/var\u003e - \u003cvar data-var='time'\u003e12:59\u003c/var\u003e UTC"
},
{
"code": "f2w7c18std4n",
"impact": "minor",
"message": "This incident has been resolved. A small number of customers who created pipelines between 18:53 UTC and 19:24 UTC that contained config using deprecated config syntax will have seen their build-type jobs fail to start. Customers whose jobs or pipelines failed may rerun them.",
"name": "Issues loading pipelines for a small number of projects",
"timestamp": "Sep \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e20:25\u003c/var\u003e - \u003cvar data-var='time'\u003e20:26\u003c/var\u003e UTC"
},
{
"code": "wl4yqd96zl2h",
"impact": "minor",
"message": "We've seen no further impact to queue times and everything has returned to normal. We appreciate your patience while we worked to resolve and monitor this issue.",
"name": "macOS Job Delays",
"timestamp": "Sep \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e15:16\u003c/var\u003e - \u003cvar data-var='time'\u003e16:55\u003c/var\u003e UTC"
}
],
"name": "September",
"year": 2026
},
{
"incidents": [
{
"code": "6krzv75hq75h",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Intermittent errors when viewing plan usage UIs or calling plan usage APIs",
"timestamp": "Aug \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e15:43\u003c/var\u003e - \u003cvar data-var='time'\u003e16:10\u003c/var\u003e UTC"
},
{
"code": "yxxll285k6sf",
"impact": "minor",
"message": "Between 19:49 UTC and 21:07 UTC on August 25, 2026, customers attempting to log in to CircleCI using GitHub were unable to sign in, and received an error from GitHub stating the callback URL was invalid. Customers who were already logged in were not affected. The issue has been resolved and GitHub login is functioning normally. We thank you for your patience while our team worked on implementing a fix.",
"name": "GitHub Login Disruption",
"timestamp": "Aug \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e20:00\u003c/var\u003e - \u003cvar data-var='time'\u003e20:00\u003c/var\u003e UTC"
},
{
"code": "bd3dy5yl5cqm",
"impact": "minor",
"message": "Insights data is good once more. Thank you for your patience.",
"name": "Insight data is currently delayed",
"timestamp": "Aug \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e21:06\u003c/var\u003e - \u003cvar data-var='time'\u003e21:37\u003c/var\u003e UTC"
},
{
"code": "h3cw7x07ggf2",
"impact": "major",
"message": "GitHub's APIs appear to be operating normally.",
"name": "GitHub Incidents impacting CircleCI functionality",
"timestamp": "Aug \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e14:04\u003c/var\u003e - \u003cvar data-var='time'\u003e19:05\u003c/var\u003e UTC"
},
{
"code": "phn6832tvb84",
"impact": "none",
"message": "Following planned maintenance that ended at 13:00 UTC on August 15, some impact to job processing continued for approximately 30 minutes beyond the window we announced.\n\nSome customers continued to see delays in jobs starting, along with a small number of jobs failing with infrastructure errors, until approximately 13:30 UTC.\n\nThis has been resolved and job processing has returned to normal. Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix and apologize for any inconvenience the extended impact may have caused.",
"name": "Delays starting jobs following planned maintenance",
"timestamp": "Aug \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e17:00\u003c/var\u003e - \u003cvar data-var='time'\u003e17:00\u003c/var\u003e UTC"
},
{
"code": "cqjc71nw8t30",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Infrastructure Maintenance",
"timestamp": "Aug \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e12:00\u003c/var\u003e - \u003cvar data-var='time'\u003e13:00\u003c/var\u003e UTC"
},
{
"code": "by4dk5ttk6j4",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] macOS Executor Maintenance",
"timestamp": "Aug \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e01:00\u003c/var\u003e - \u003cvar data-var='time'\u003e05:00\u003c/var\u003e UTC"
},
{
"code": "ljvrkzc9pdfr",
"impact": "minor",
"message": "The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/76t89hbfb09h) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to normal. \n\nWe thank you for your patience.",
"name": "GitHub service degradation may impact customers using GitHub",
"timestamp": "Aug \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e16:33\u003c/var\u003e - \u003cvar data-var='time'\u003e16:43\u003c/var\u003e UTC"
},
{
"code": "lh8681zry6jd",
"impact": "none",
"message": "Between 13:50 UTC and approximately 17:30 UTC on August 11, 2026, some customers experienced delays of up to an hour in pipeline status updates and in notification delivery. \n\nBetween 16:40 UTC and 17:00 UTC within that same window, a small number of customers also saw newly created pipelines fail to process, appearing in an errored state in the UI and API. \n\nThe issue has been resolved and all affected functionality has returned to normal. Customers whose pipelines errored during that window can retrigger them. \n\nWe thank you for your patience while our team worked on implementing a fix.",
"name": "Delayed pipeline updates and pipeline processing failures",
"timestamp": "Aug \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e18:00\u003c/var\u003e - \u003cvar data-var='time'\u003e18:00\u003c/var\u003e UTC"
},
{
"code": "7l9wg4375jr4",
"impact": "none",
"message": "The Usage API issue has been resolved. Data has been loaded for yesterday, 8/5/2026. We appreciate your patience.",
"name": "Usage API data delayed for 8/5",
"timestamp": "Aug \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e13:06\u003c/var\u003e - \u003cvar data-var='time'\u003e19:54\u003c/var\u003e UTC"
},
{
"code": "t6h24sd17ydk",
"impact": "maintenance",
"message": "Our new support portal is up and operational, please reach out with any issues or questions via the messenger on support.circleci.com or via email at [email protected].\n\nThank you for your patience throughout this maintenance period.",
"name": "[Scheduled] Scheduled Maintenance - Support Portal",
"timestamp": "Aug \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e14:36\u003c/var\u003e - \u003cvar data-var='time'\u003e15:24\u003c/var\u003e UTC"
},
{
"code": "xwrqk8hh14zf",
"impact": "minor",
"message": "The upstream issue has been resolved, and the insights data from the last 24 hours has caught up. Thank you for your patience.",
"name": "Insights service data is lagging",
"timestamp": "Aug \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e16:58\u003c/var\u003e - \u003cvar data-var='time'\u003e21:01\u003c/var\u003e UTC"
},
{
"code": "n8p81wk9xjrz",
"impact": "minor",
"message": "Queue times for Android and Windows jobs have reduced significantly over the last hour. You may still notice brief, isolated queuing at times, but this is no longer at incident-level impact. This was related to capacity constraints with a third-party infrastructure provider. We thank you for your patience while we monitored the situation. If you have any issues, please reach out to our Support team.",
"name": "Increased Job Queue Times: Windows, Android, and GPU",
"timestamp": "Aug \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e19:27\u003c/var\u003e - \u003cvar data-var='time'\u003e23:40\u003c/var\u003e UTC"
}
],
"name": "August",
"year": 2026
},
{
"incidents": [
{
"code": "q17ysw9wn2pr",
"impact": "minor",
"message": "The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/yjysg0xrl67m) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to normal. \n\nWe thank you for your patience.",
"name": "GitHub service degradation may impact customers using GitHub",
"timestamp": "Jul \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e16:35\u003c/var\u003e - \u003cvar data-var='time'\u003e17:41\u003c/var\u003e UTC"
},
{
"code": "l3hk1qv7hbmj",
"impact": "minor",
"message": "Between 19:24 UTC on 22 July and 01:50 UTC on 23 July, customers using the gen3 preview machine (Linux VM) resource classes experienced delays and, in some cases, jobs failing to start. We have removed the gen3 resource classes while we address stability issues affecting them. Unfortunately, workflows that we were unable to provision compute capacity for during this period were cancelled. Affected customers should change their resource class from gen3 to gen2 and rerun those workflows. \n\nWe thank you for your patience while our team worked to resolve this.",
"name": "Delays in starting jobs using the gen3 resource class",
"timestamp": "Jul \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e19:57\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e02:05\u003c/var\u003e UTC"
},
{
"code": "l6yh0qf4c20c",
"impact": "none",
"message": "Between 03:18 UTC and 06:04 UTC on July 22, 2026, a subset of customers were unable to access app.circleci.com. The issue has been resolved and access has returned to normal. \n\nWe thank you for your patience while our team worked on implementing a fix.",
"name": "Errors loading app.circleci.com",
"timestamp": "Jul \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e06:13\u003c/var\u003e - \u003cvar data-var='time'\u003e06:27\u003c/var\u003e UTC"
},
{
"code": "9lvbbbs9l87b",
"impact": "minor",
"message": "GitHub API error rates have recovered to normal levels.\n\nDuring the incident, some customers may have seen pipelines fail to start or not receive status updates. Some pipelines may be stuck in a running state.\n\n* You should re-push commits or use the UI to manually trigger pipelines that didn't start.\n* Pipelines in a stuck running state should be canceled and rerun.\n\nIf you encounter any issues please contact CircleCI support.",
"name": "Errors with GitHub APIs delaying workflows",
"timestamp": "Jul \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e00:35\u003c/var\u003e - \u003cvar data-var='time'\u003e01:45\u003c/var\u003e UTC"
},
{
"code": "2b55fgxy67rb",
"impact": "minor",
"message": "An incident affecting GitHub's API caused CircleCI customers to experience errors loading the web app and signing in, along with pipelines and scheduled workflows failing to start or running late. GitHub has resolved the underlying incident (https://www.githubstatus.com/) and all affected functionality has returned to normal.\n\nCustomers whose jobs or pipelines failed may rerun them. Scheduled pipelines and workflows that were missed during the incident will not run automatically and will need to be re-triggered.\n\nWe thank you for your patience.",
"name": "Errors accessing CircleCI and delays starting pipelines and scheduled workflows",
"timestamp": "Jul \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e23:04\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e00:26\u003c/var\u003e UTC"
},
{
"code": "rfz5wdpg2nl0",
"impact": "minor",
"message": "On July 13 between 15:30 UTC and 22:40 UTC, we experienced delays starting jobs on Docker (Gen 2) resource classes due to capacity constraints from our cloud provider. The same issue recurred on July 14 between 15:45 UTC and 22:50 UTC.\n\nDelays reached up to 25 minutes on July 13 and up to 24 minutes on July 14. The medium+ and 2 X-large+ resource classes saw the longest waits. Earlier updates in this incident reported figures based on average wait times, which didn't reflect the maximum impact some customers may have experienced.\n\nWait times have now returned to normal. We are continuing to work with our cloud provider to add capacity ahead of the next peak period. Thank you for your patience.",
"name": "Delays starting jobs on Docker (Gen 2) resource classes",
"timestamp": "Jul \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e22:54\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e00:32\u003c/var\u003e UTC"
},
{
"code": "7cnl777wp9qz",
"impact": "minor",
"message": "We continue to see significant VCS fetch time recovery over the last couple of hours. We're going to resolve this incident, and our engineering team will continue to monitor closely. We greatly appreciate your patience as we worked through this with our Mac infrastructure provider. Please reach out to our Support team if you have any issues.",
"name": "Issues with network routing for Mac jobs",
"timestamp": "Jul \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e21:52\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e23:18\u003c/var\u003e UTC"
},
{
"code": "gsyjwybg477g",
"impact": "minor",
"message": "The issue where customers logging in with a Bitbucket-linked identity experienced login errors, and some customers experienced workflows that failed to start or did not update, has been resolved. \n\nWhat you may still experience and need to do\n- If you use Bitbucket as your login method, please log out and reauthenticate the CircleCI Bitbucket integration on your account.\n- If any of your workflows are stuck or showing missing status checks, please rerun them to pick up the fix.\n- If you continue to experience issues after taking these steps, please reach out to CircleCI Support.\n\nWe thank you for your patience while our team worked on implementing a fix.",
"name": "Login issues for some Bitbucket users",
"timestamp": "Jul \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e02:49\u003c/var\u003e - \u003cvar data-var='time'\u003e05:15\u003c/var\u003e UTC"
},
{
"code": "n1tc2lw9q7l0",
"impact": "minor",
"message": "We've confirmed the fix with our infrastructure provider and successful tests on our end. If customers continue to see any failed runs, please run again for a successful connection and reach out to Support if any further issues.",
"name": "Issues with network routing for Mac jobs",
"timestamp": "Jul \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e18:55\u003c/var\u003e - \u003cvar data-var='time'\u003e19:40\u003c/var\u003e UTC"
},
{
"code": "z3bmk3c1rvh9",
"impact": "maintenance",
"message": "We have completed the kernel upgrades across all of the infrastructure used to run Docker jobs. Our monitoring shows Docker job execution is working as normal.\n\nDuring the maintenance, a small number of running jobs were canceled as machines were upgraded. These jobs will have an \"Infrastructure Fail\" status in the CircleCI UI. You can rerun Infrastructure Fail jobs from the UI or pushing to your VCS brach.\n\nPlease contact CircleCI support if you have any additional questions or have problems running Docker jobs.\n\nThank you for your patience during this maintenance.",
"name": "[Scheduled] Emergency Maintenance: Security Updates for Docker Jobs.",
"timestamp": "Jul \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e02:25\u003c/var\u003e - \u003cvar data-var='time'\u003e05:03\u003c/var\u003e UTC"
},
{
"code": "82j91239k876",
"impact": "critical",
"message": "Pipelines and UI access have fully recovered.\n\nPlease contact customer support if you have issues running builds.\n\nThis incident has been resolved.",
"name": "Outage impacting web experience and pipelines starting",
"timestamp": "Jul \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e15:25\u003c/var\u003e - \u003cvar data-var='time'\u003e16:44\u003c/var\u003e UTC"
}
],
"name": "July",
"year": 2026
}
],
"start_time": "2026-07-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-06-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "njbxb52z1g1y",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Some customers are unable to access their organizations",
"timestamp": "Jun \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e10:23\u003c/var\u003e - \u003cvar data-var='time'\u003e16:58\u003c/var\u003e UTC"
},
{
"code": "6s53wvppvby5",
"impact": "minor",
"message": "We observed a surge in demand for Xcode 26.6 and have since mitigated the incident by increasing the available capacity for that Xcode version. Customers may have seen jobs queueing for ~10-15 mins.",
"name": "Xcode 26.6 Demand + Queueing",
"timestamp": "Jun \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e15:00\u003c/var\u003e - \u003cvar data-var='time'\u003e15:00\u003c/var\u003e UTC"
},
{
"code": "xyzcdfq55stc",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Investigating — Usage API Not Available",
"timestamp": "Jun \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e22:44\u003c/var\u003e - \u003cvar data-var='time'\u003e23:03\u003c/var\u003e UTC"
},
{
"code": "gvysjmkf4ct9",
"impact": "minor",
"message": "We are concluding this incident based on a confirmed fix with our infrastructure provider and successful tests. For any customers seeing failed runs, please run again for a successful connection.",
"name": "Issues with network routing for Mac jobs",
"timestamp": "Jun \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e23:13\u003c/var\u003e - Jun \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e03:06\u003c/var\u003e UTC"
},
{
"code": "rp9y8kszn25j",
"impact": "major",
"message": "The issue where customers running Docker jobs experienced significant delays, with jobs stuck in a \"preparing environment\" state, has now been resolved. We thank you for your patience while our team worked on implementing a fix.",
"name": "Delays starting Docker jobs",
"timestamp": "Jun \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e18:34\u003c/var\u003e - \u003cvar data-var='time'\u003e19:58\u003c/var\u003e UTC"
},
{
"code": "9b44dhlr1ym2",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Scheduled Maintenance — Bitbucket Integration",
"timestamp": "Jun \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e17:00\u003c/var\u003e - \u003cvar data-var='time'\u003e19:00\u003c/var\u003e UTC"
},
{
"code": "brp558x5kfn1",
"impact": "minor",
"message": "Customers using Bitbucket as their VCS provider or as their login provider experienced errors when interacting with Bitbucket repositories and authenticating to CircleCI. This was caused by an incident with Atlassian Bitbucket's OAuth service, which has now been resolved and all affected functionality has returned to normal.",
"name": "Issue authenticating only Bitbucket users",
"timestamp": "Jun \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e21:31\u003c/var\u003e - Jun \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e00:18\u003c/var\u003e UTC"
},
{
"code": "76fmvjmy0jfx",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Issues publishing orbs",
"timestamp": "Jun \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e22:39\u003c/var\u003e - \u003cvar data-var='time'\u003e23:07\u003c/var\u003e UTC"
},
{
"code": "lh98c0k4pc1h",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Incident with GitHub APIs",
"timestamp": "Jun \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e16:30\u003c/var\u003e - \u003cvar data-var='time'\u003e16:41\u003c/var\u003e UTC"
},
{
"code": "tqh9zwszp05w",
"impact": "minor",
"message": "Between 13:29 UTC and 18:20 UTC on June 9, 2026, some customers experienced 500 errors when making requests to the pipeline values and workflow API endpoints, as well as errors in the UI. Jobs running were not impacted during this window. The issue has been resolved and all affected functionality has returned to normal. We thank you for your patience while our team worked on implementing a fix.",
"name": "Increased 500 Errors on Pipeline and Workflow API Endpoints and UI",
"timestamp": "Jun \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e17:45\u003c/var\u003e - \u003cvar data-var='time'\u003e18:43\u003c/var\u003e UTC"
},
{
"code": "2rhbvp9382px",
"impact": "major",
"message": "This issue has been resolved and macOS jobs across all resource classes are starting normally again. Customers whose jobs failed to start during this window may rerun them. We thank you for your patience while our team worked on implementing a fix.",
"name": "macOS jobs failing to start",
"timestamp": "Jun \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e04:20\u003c/var\u003e - \u003cvar data-var='time'\u003e04:44\u003c/var\u003e UTC"
},
{
"code": "zvkm3drwt6xd",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Machine Cloud Maintenance",
"timestamp": "Jun \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e00:30\u003c/var\u003e - \u003cvar data-var='time'\u003e01:00\u003c/var\u003e UTC"
},
{
"code": "b4jcpwt024vc",
"impact": "none",
"message": "This incident has been resolved.",
"name": "Errors on Cloud Docker Pulls",
"timestamp": "Jun \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e12:52\u003c/var\u003e - \u003cvar data-var='time'\u003e13:11\u003c/var\u003e UTC"
},
{
"code": "grz5fksl49mn",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Machine Cloud Maintenance",
"timestamp": "Jun \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e14:00\u003c/var\u003e - \u003cvar data-var='time'\u003e15:00\u003c/var\u003e UTC"
},
{
"code": "wcsh4hxwkrh7",
"impact": "minor",
"message": "All Mac jobs are running successfully.\n\nOur infrastructure provider has confirmed that the DDoS attack has been mitigated and that services have been restored.\n\nThank you for your patience during this incident.",
"name": "Mac jobs failing to start",
"timestamp": "Jun \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e01:04\u003c/var\u003e - \u003cvar data-var='time'\u003e03:26\u003c/var\u003e UTC"
},
{
"code": "t7vt8j14jnbg",
"impact": "minor",
"message": "Mac jobs have now fully recovered.\n\nThank you for your patience during this incident.",
"name": "Mac jobs failing to start",
"timestamp": "May \u003cvar data-var='date'\u003e31\u003c/var\u003e, \u003cvar data-var='time'\u003e18:15\u003c/var\u003e - Jun \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e00:45\u003c/var\u003e UTC"
}
],
"name": "June",
"year": 2026
},
{
"incidents": [
{
"code": "dqlq3v1q8pvn",
"impact": "none",
"message": "The Usage API incident has been resolved.",
"name": "Usage API data delayed for 5/28",
"timestamp": "May \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e14:51\u003c/var\u003e - \u003cvar data-var='time'\u003e18:10\u003c/var\u003e UTC"
},
{
"code": "qhxl36d29vfl",
"impact": "minor",
"message": "Customers running jobs that pulled dependencies from Maven Central experienced elevated 429 (rate limit) errors. We have worked with Sonatype to allow list CircleCI's dedicated IP ranges. Customers using our IP ranges feature should no longer see Maven Central rate limits affect their jobs while we continue work to fully address the issue for all customers.\n\nCustomers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix.",
"name": "Elevated 429 errors pulling from maven central",
"timestamp": "May \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e16:49\u003c/var\u003e - \u003cvar data-var='time'\u003e19:38\u003c/var\u003e UTC"
},
{
"code": "jtnrz91kc7m7",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Maintenance — OIDC Token Minting",
"timestamp": "May \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e - \u003cvar data-var='time'\u003e01:00\u003c/var\u003e UTC"
},
{
"code": "d4gch9k0tcsq",
"impact": "none",
"message": "This incident has been resolved.",
"name": "GitHub incident with Pull Requests",
"timestamp": "May \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e17:54\u003c/var\u003e - \u003cvar data-var='time'\u003e21:26\u003c/var\u003e UTC"
},
{
"code": "68kk6515ztfp",
"impact": "major",
"message": "This incident is resolved. Thank you for your patience, and we apologize for any inconvenience.",
"name": "Some Pipelines are being lost",
"timestamp": "May \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e19:42\u003c/var\u003e - \u003cvar data-var='time'\u003e20:13\u003c/var\u003e UTC"
},
{
"code": "mspf5pqp7d42",
"impact": "none",
"message": "This issue has been resolved. All data is up to date through yesterday.",
"name": "Usage API data is delayed for data from yesterday, 4/30. All prior data is available. We are investigating.",
"timestamp": "May \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e10:04\u003c/var\u003e - \u003cvar data-var='time'\u003e14:02\u003c/var\u003e UTC"
},
{
"code": "t30mkznmqskh",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Jobs using Xcode 14.3.1 on m4pro.large are delayed.",
"timestamp": "May \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e10:51\u003c/var\u003e - \u003cvar data-var='time'\u003e11:08\u003c/var\u003e UTC"
}
],
"name": "May",
"year": 2026
},
{
"incidents": [
{
"code": "90354ss2tb8t",
"impact": "minor",
"message": "Customers running macOS jobs on m4pro.medium and m4pro.large with the xcode:26.4.0 image experienced job rejections with the error: \"Job was rejected because resource class , image xcode:26.4.0 is not a valid resource class\". The issue has been resolved and affected jobs should now run normally. \n\nCustomers whose jobs failed may rerun affected jobs. \n\nWe thank you for your patience while our team worked on implementing a fix.",
"name": "Build failures Xcode 26.4.0",
"timestamp": "Apr \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e17:25\u003c/var\u003e - \u003cvar data-var='time'\u003e18:36\u003c/var\u003e UTC"
},
{
"code": "2v2q3ht88fh1",
"impact": "none",
"message": "The Usage API issue has been resolved. All data is now current. Appreciate your patience.",
"name": "Usage API data delayed this morning",
"timestamp": "Apr \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e12:07\u003c/var\u003e - \u003cvar data-var='time'\u003e15:05\u003c/var\u003e UTC"
},
{
"code": "l7vz5yr3wrp0",
"impact": "minor",
"message": "The Usage API incident is resolved on an ongoing basis. There was a 4-hour period yesterday 4/7 for which we did not capture RAM and CPU utilization in our logs. We will not be backfilling the data for that period. Appreciate your patience.",
"name": "Delays in Workflow and Job data in the Usage API",
"timestamp": "Apr \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e13:20\u003c/var\u003e - \u003cvar data-var='time'\u003e20:33\u003c/var\u003e UTC"
},
{
"code": "2l1y8dhrvtzd",
"impact": "major",
"message": "This incident has been resolved.",
"name": "Degradation in CircleCI UI elements",
"timestamp": "Apr \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e20:33\u003c/var\u003e - \u003cvar data-var='time'\u003e21:12\u003c/var\u003e UTC"
},
{
"code": "lxkrhs9rmrxv",
"impact": "minor",
"message": "The Usage API issue affecting 4/1 data has been resolved. Updated data will be available on 4/3. Thank you for your patience.",
"name": "Usage API data for 4/1 is incomplete with multiple columns showing null values. Data prior to 4/1 is unaffected. We are investigating.",
"timestamp": "Apr \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e19:19\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e02:18\u003c/var\u003e UTC"
},
{
"code": "hth87g8tfm2y",
"impact": "major",
"message": "It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.",
"name": "Some pipelines not triggering due to GitHub API failures",
"timestamp": "Apr \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e11:55\u003c/var\u003e - \u003cvar data-var='time'\u003e12:23\u003c/var\u003e UTC"
}
],
"name": "April",
"year": 2026
}
],
"start_time": "2026-04-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-03-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "g0b66jlry2kf",
"impact": "none",
"message": "On March 18, 2026, customers using workflows configured with serial groups or terminal job dependencies experienced two brief periods of disruption due to a code change.\n\nBetween approximately 12:08 and 12:35 UTC, affected pipelines encountered errors when creating workflows. For pipelines created in a second window from approximately 14:23 to 14:35 UTC, GitHub status updates were not delivered for some completed jobs. Long-running workflows triggered during this window may encounter these errors after the resolution time. The underlying change was reverted in both cases.\n\nAll systems have been operating normally since 14:35 UTC.",
"name": "Pipelines — Workflow Creation Errors and Missing GitHub Status Updates",
"timestamp": "Mar \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e16:00\u003c/var\u003e UTC"
},
{
"code": "01zmcr93tysy",
"impact": "minor",
"message": "Our engineering team has identified the root cause and has fixes prepared. Due to the nature of the data refresh process, the fix will require a deployment followed by a full refresh cycle before data is fully up to date. We expect that the data should be available within 24-36 hours. The last-24-hours reporting window continues to work normally, and all pipeline pages and job runs remain unaffected.",
"name": "Insights API and Dashboard displaying stale data for reporting windows greater than 24 hours",
"timestamp": "Mar \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e03:02\u003c/var\u003e - \u003cvar data-var='time'\u003e03:52\u003c/var\u003e UTC"
},
{
"code": "v86p9jb46jt1",
"impact": "minor",
"message": "The issue affecting the orb list on the Organization Settings page has been resolved. Our engineers have deployed a fix and users should now be able to view their orb list as expected. Orb usage in pipelines and builds was not impacted during this incident. If you continue to experience issues, please contact CircleCI support.\n\nThank you for your patience while we worked on resolving this issue.",
"name": "Unable to view orb list on Organization Settings page",
"timestamp": "Mar \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e01:58\u003c/var\u003e - \u003cvar data-var='time'\u003e02:24\u003c/var\u003e UTC"
},
{
"code": "lg8x09p2d2n3",
"impact": "minor",
"message": "Looks like everything is good. Thank you for your patience.",
"name": "docker not working in cimg:*",
"timestamp": "Mar \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e17:59\u003c/var\u003e - \u003cvar data-var='time'\u003e18:21\u003c/var\u003e UTC"
}
],
"name": "March",
"year": 2026
},
{
"incidents": [
{
"code": "r88g618tt765",
"impact": "minor",
"message": "GitHub have acknowledged and resolved an incident affecting their platform.\nhttps://www.githubstatus.com/incidents/vd3xqfq36rgm\nUsers should no longer experience intermittent checkout failures.",
"name": "Degradation in some checkout steps",
"timestamp": "Feb \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e22:50\u003c/var\u003e - Feb \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e00:17\u003c/var\u003e UTC"
},
{
"code": "826586ng6h55",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Mac Cloud Maintenance - Tuesday, February 24th, 2:00 AM – 6:00 AM UTC",
"timestamp": "Feb \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e02:00\u003c/var\u003e - \u003cvar data-var='time'\u003e06:00\u003c/var\u003e UTC"
},
{
"code": "5xrywvlmqd9b",
"impact": "major",
"message": "Our authentication provider has confirmed the earlier service disruption has been fully mitigated: https://status.auth0.com/incidents/kknl0nbdzbvx\n\nEmail/password login functionality has been restored and is operating normally.",
"name": "Sign-In Issue Affecting Email/Password Logins",
"timestamp": "Feb \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e17:25\u003c/var\u003e - \u003cvar data-var='time'\u003e19:05\u003c/var\u003e UTC"
},
{
"code": "6rpnwxd8zbt6",
"impact": "minor",
"message": "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.\n\nJobs and builds were not impacted during this time.\n\nWe apologize for the disruption and thank you for your patience.",
"name": "Pipeline UI Degradation and GitHub Checks Delivery",
"timestamp": "Feb \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e16:25\u003c/var\u003e - \u003cvar data-var='time'\u003e17:44\u003c/var\u003e UTC"
},
{
"code": "8t0k593wrlf1",
"impact": "minor",
"message": "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.",
"name": "Bitbucket Organizations unavailable in the CircleCI UI",
"timestamp": "Feb \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e10:30\u003c/var\u003e - \u003cvar data-var='time'\u003e10:30\u003c/var\u003e UTC"
},
{
"code": "y247jq72y6hn",
"impact": "major",
"message": "This incident has been resolved.",
"name": "Delay in Jobs starting",
"timestamp": "Feb \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e15:21\u003c/var\u003e - \u003cvar data-var='time'\u003e16:13\u003c/var\u003e UTC"
},
{
"code": "0ss2l980mvxx",
"impact": "major",
"message": "Following GitHub's service recovery, all CircleCI functionality has returned to normal operation. Jobs are processing as expected across all resource classes.",
"name": "We are investigating issues with delays in pages loading",
"timestamp": "Feb \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e19:48\u003c/var\u003e - \u003cvar data-var='time'\u003e20:25\u003c/var\u003e UTC"
},
{
"code": "d1147yfn3mjr",
"impact": "minor",
"message": "This incident has been resolved. Thank you for your patience.",
"name": "Delays affecting Linux and Remote Docker jobs",
"timestamp": "Feb \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e17:46\u003c/var\u003e - \u003cvar data-var='time'\u003e18:58\u003c/var\u003e UTC"
},
{
"code": "wzg0fsnzs7hq",
"impact": "minor",
"message": "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.",
"name": "Email Notifications Delayed",
"timestamp": "Feb \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e20:07\u003c/var\u003e - \u003cvar data-var='time'\u003e22:18\u003c/var\u003e UTC"
}
],
"name": "February",
"year": 2026
},
{
"incidents": [
{
"code": "zm1hqtf9tmnb",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Job start delays for arm-medium, large, xlarge, 2xl resources",
"timestamp": "Jan \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e19:29\u003c/var\u003e - \u003cvar data-var='time'\u003e19:37\u003c/var\u003e UTC"
},
{
"code": "8k5d6fdhxw84",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Deprecation of Mac M1 and M2 resource classes",
"timestamp": "Jan \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e UTC"
},
{
"code": "rmfw6lg2fmxz",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Deprecation of Mac M1 and M2 resource classes",
"timestamp": "Jan \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e UTC"
},
{
"code": "d08dgsh3gppy",
"impact": "minor",
"message": "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.\nOur team has completed the necessary tuning and service performance has returned to normal levels. \n\nWe apologize for any inconvenience this may have caused.",
"name": "Delays in job start",
"timestamp": "Jan \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e18:08\u003c/var\u003e - \u003cvar data-var='time'\u003e18:08\u003c/var\u003e UTC"
},
{
"code": "wtsg771pdb09",
"impact": "minor",
"message": "This issue has been resolved. Organizations using Bitbucket are now able to build successfully following mitigation actions we implemented earlier today.\n\nWhat happened: We identified an issue where retrieving user identities from Bitbucket was encountering rate limiting for accounts with extensive project configurations. This was caused by recent changes to Bitbucket's rate limiting behavior that were enforced in late December 2025. Our mitigating actions helped resolve the issue for most of the affected organizations.\n\nCurrent status: Organizations that were previously unable to build are now building successfully. A small number of individual users with access to very large numbers of repositories may still occasionally encounter rate limiting by Bitbucket during the identity retrieval process. These users can have another team member trigger builds as a workaround.\n\nIf you continue to experience issues: Please reach out to us via your regular support channels.",
"name": "Issues with jobs starting for certain Bitbucket users",
"timestamp": "Jan \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e11:23\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e23:25\u003c/var\u003e UTC"
}
],
"name": "January",
"year": 2026
}
],
"start_time": "2026-01-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2025-12-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "n5xfqggvbrrn",
"impact": "minor",
"message": "This incident has been resolved and wait times have returned to normal. We appreciate your patience.",
"name": "Higher wait times for Linux, Remote Docker and Mac resource classes",
"timestamp": "Dec \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e21:17\u003c/var\u003e - \u003cvar data-var='time'\u003e22:12\u003c/var\u003e UTC"
},
{
"code": "49b7b000783q",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Deprecation of Mac M1 and M2 resource classes",
"timestamp": "Dec \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e16:43\u003c/var\u003e - Dec \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e UTC"
},
{
"code": "w2ztzzvzy7pz",
"impact": "none",
"message": "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.\n \nThe 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.",
"name": "Higher wait times for Linux, Remote Docker and ARM resource classes",
"timestamp": "Dec \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e21:30\u003c/var\u003e - \u003cvar data-var='time'\u003e21:30\u003c/var\u003e UTC"
},
{
"code": "x8k88dhlbxgw",
"impact": "minor",
"message": "The Usage API issue has been resolved. Data is loaded for yesterday 12/11. Thank you for your patience.",
"name": "Usage API Data Unavailable for December 11, 2025",
"timestamp": "Dec \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e17:22\u003c/var\u003e - \u003cvar data-var='time'\u003e19:07\u003c/var\u003e UTC"
},
{
"code": "1fnjbc82yqxy",
"impact": "critical",
"message": "The incident has been resolved. Thank you for your patience. The \"infra-fail\" should no longer be occurring.",
"name": "Issue with Jobs",
"timestamp": "Dec \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e22:53\u003c/var\u003e - Dec \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e00:15\u003c/var\u003e UTC"
},
{
"code": "gk9pcm1jz8s0",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "MacOS jobs without a resource class set will not run",
"timestamp": "Dec \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e16:04\u003c/var\u003e - \u003cvar data-var='time'\u003e17:49\u003c/var\u003e UTC"
},
{
"code": "jq4bgq2sjt1r",
"impact": "minor",
"message": "We have resolved the issues affecting job triggering, workflow starts, and API queries. Our systems have been stabilized and are operating normally.\n\nWhat was impacted: Job triggering, workflow starts, API queries, and pipeline page loading experienced disruptions for some customers. This affected all resource classes and executors.\n\nResolution: We implemented mitigation measures to address high volume workflow queries impacting our internal systems and increased system capacity. All new jobs and workflows are now starting normally, pipeline pages are loading, and API queries are functioning as expected.\n\nWhat to expect: If you have jobs that became stuck during this incident, please rerun them. If you continue to experience issues after rerunning, please contact our support team. Some customers may still see jobs stuck in a cancelling state. Engineering is aware and addressing to mitigate risk. \n\nWe will continue monitoring our systems and conducting a thorough review to identify additional preventive measures.",
"name": "Jobs not starting",
"timestamp": "Dec \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e21:28\u003c/var\u003e - \u003cvar data-var='time'\u003e23:48\u003c/var\u003e UTC"
},
{
"code": "fjpg0vmh476k",
"impact": "minor",
"message": "The issues affecting the pipelines page display are related to a broader incident impacting our systems. We have opened a separate incident tracking job triggering and API status issues, which encompasses the pipelines page loading problems. Please follow https://status.circleci.com/incidents/jq4bgq2sjt1r for ongoing updates.",
"name": "Pipelines page not loading - Cont.",
"timestamp": "Dec \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e21:31\u003c/var\u003e - \u003cvar data-var='time'\u003e21:58\u003c/var\u003e UTC"
},
{
"code": "kvzp8x242n34",
"impact": "minor",
"message": "Between 16:20 and 16:32 UTC, job triggering and workflow starts experienced disruptions across all resource classes due to memory pressure on our internal job distributor systems. We identified the issue and scaled our infrastructure to handle the load. Services returned to normal operation at 16:32 UTC.\n\nWhat was impacted: Job triggering and workflow starts were disrupted for 12 minutes. Some workflows and jobs appeared stuck in a running state during this window.\n\nResolution: Our systems are now operating normally with additional capacity in place to prevent similar disruptions. If you had workflows or jobs that were stuck during this window, please manually rerun them.\n\nThe incident is now resolved and we will be conducting a thorough review to understand what triggered the memory pressure and identify any additional preventive measures",
"name": "Jobs stuck in running state",
"timestamp": "Dec \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e16:53\u003c/var\u003e - \u003cvar data-var='time'\u003e18:12\u003c/var\u003e UTC"
},
{
"code": "21cysyp8d333",
"impact": "minor",
"message": "This incident has been resolved. Things should be back to normal.",
"name": "Pipelines page not loading",
"timestamp": "Dec \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e13:37\u003c/var\u003e - \u003cvar data-var='time'\u003e15:30\u003c/var\u003e UTC"
},
{
"code": "qq3x5734kbw9",
"impact": "none",
"message": "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.\n\nImpact: \n- Some customers received multiple failure notification emails for the same workflow.\n- The number of duplicate notifications varied based on how many jobs in the workflow were affected (e.g., marked skipped or cancelled).\n- A subset of customers may have received duplicate Slack notifications.\n- A small number of projects experienced duplicated auto-reruns.\n\nThe issue has been fully mitigated, and notification behavior has returned to normal. We appreciate your patience while our team resolved this issue.",
"name": "Duplicate Notifications",
"timestamp": "Dec \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e02:00\u003c/var\u003e - \u003cvar data-var='time'\u003e02:00\u003c/var\u003e UTC"
}
],
"name": "December",
"year": 2025
},
{
"incidents": [
{
"code": "wf6y6934w0d2",
"impact": "minor",
"message": "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.",
"name": "Mac M1 Large job start are delayed",
"timestamp": "Nov \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e22:53\u003c/var\u003e - \u003cvar data-var='time'\u003e23:24\u003c/var\u003e UTC"
},
{
"code": "wlkl91fxyzfr",
"impact": "minor",
"message": "All Machine resource classes are operating successfully. Thank you for your patience, and we apologize for any inconvenience this may have caused.",
"name": "Issue with certain resource classes for Machine Executors",
"timestamp": "Nov \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e15:50\u003c/var\u003e - \u003cvar data-var='time'\u003e16:28\u003c/var\u003e UTC"
},
{
"code": "ptfypc6vygft",
"impact": "none",
"message": "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).",
"name": "Some jobs were not triggered and will need to be manually retried",
"timestamp": "Nov \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e16:10\u003c/var\u003e - \u003cvar data-var='time'\u003e16:10\u003c/var\u003e UTC"
},
{
"code": "scp36zp1kb59",
"impact": "none",
"message": "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.\n\nImpact:\n- Some workflows showed no check run status in GitHub\n- Some workflows showed check runs stuck in \"pending\" state\n- User flows requiring these checks may have been blocked\n\nResolution: This issue resolved upon completion of our maintenance. All services are now operating normally.\n\nWe 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.",
"name": "GitHub Check Notifications Impacted During RabbitMQ Maintenance",
"timestamp": "Nov \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e01:00\u003c/var\u003e - \u003cvar data-var='time'\u003e01:00\u003c/var\u003e UTC"
},
{
"code": "4p6vwsdznvwp",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Scheduled Maintenance - RMQ Infrastructure Updates",
"timestamp": "Nov \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e20:00\u003c/var\u003e - \u003cvar data-var='time'\u003e22:00\u003c/var\u003e UTC"
},
{
"code": "4xxfs5fkrb6q",
"impact": "minor",
"message": "Mac M4 and M1 jobs are now running normally. Thank you again for your patience while we addressed this issue.",
"name": "M4 and M1 Mac Jobs are delayed",
"timestamp": "Nov \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e15:58\u003c/var\u003e - \u003cvar data-var='time'\u003e16:08\u003c/var\u003e UTC"
},
{
"code": "cr80s68lm23c",
"impact": "major",
"message": "This incident has been resolved.",
"name": "CircleCI UI is inaccessible",
"timestamp": "Nov \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e16:21\u003c/var\u003e - \u003cvar data-var='time'\u003e17:19\u003c/var\u003e UTC"
},
{
"code": "fvv8g845sn51",
"impact": "minor",
"message": "This incident has been resolved. All resource classes including Linux, ARM, AMD, and Remote Docker are operating normally with standard queue times. System performance has been stable and capacity has been restored.\n\nThank you for your patience while our engineers addressed this issue",
"name": "Job Start Delays for Linux, AMD, ARM and Remote Docker Resources",
"timestamp": "Nov \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e16:44\u003c/var\u003e - \u003cvar data-var='time'\u003e19:57\u003c/var\u003e UTC"
},
{
"code": "9h89qqmfh97n",
"impact": "minor",
"message": "This incident has been resolved. All resource classes including Linux, AMD, and Remote Docker are now operating normally with standard queue times. The additional capacity has been successfully deployed and job start delays have been eliminated.\nThank you for your patience while our engineers worked through this issue.",
"name": "Machine and Remote Docker jobs are delayed",
"timestamp": "Nov \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e16:18\u003c/var\u003e - \u003cvar data-var='time'\u003e20:23\u003c/var\u003e UTC"
},
{
"code": "lr070p2scl9l",
"impact": "minor",
"message": "We have resolved the issue which prevented users from creating and modifying projects. Any attempts to create projects will need to be retried. Thank you for your patenience whilst we resolved it.",
"name": "Project creation is currently failing",
"timestamp": "Nov \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e17:38\u003c/var\u003e - \u003cvar data-var='time'\u003e17:56\u003c/var\u003e UTC"
},
{
"code": "pr52byhlns18",
"impact": "none",
"message": "We have identified and applied a workaround for the RAM DIsk issue, which means customers can resume builds using `/mnt/ramdisk`. We appreciate your patience and understanding whilst we worked on resolving this whilst ensuring the security of our platform for all customers.",
"name": "RAM Disk is currently not usable in Docker jobs",
"timestamp": "Nov \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e10:40\u003c/var\u003e - Nov \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e11:24\u003c/var\u003e UTC"
},
{
"code": "wdrhw21z998p",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Deprecation of EoL Xcode Versions",
"timestamp": "Nov \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e - Nov \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e UTC"
},
{
"code": "rbmk21wl8s25",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Emergency Maintenance for Docker Jobs - Breaking Change",
"timestamp": "Nov \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e00:15\u003c/var\u003e - \u003cvar data-var='time'\u003e06:15\u003c/var\u003e UTC"
},
{
"code": "pvmtwwp8sgwv",
"impact": "none",
"message": "Some customers from 15:26:06 UTC to 18:44:16 UTC would have experienced intermittent issues with running docker jobs. We have since rolled back this change.",
"name": "Docker jobs degradation",
"timestamp": "Nov \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e19:26\u003c/var\u003e - \u003cvar data-var='time'\u003e19:26\u003c/var\u003e UTC"
},
{
"code": "908kp226d589",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Deprecation of EoL Xcode Versions",
"timestamp": "Nov \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e - Nov \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e UTC"
},
{
"code": "c3xm3qc9d4qj",
"impact": "minor",
"message": "The macOS resources performance issue has been fully resolved.\n\nAll M1 and M4 Pro medium/large resources are operating normally with standard wait times and network performance. We have monitored the infrastructure for stability and confirmed full recovery of all affected services.\n\nWe apologize for any inconvenience this may have caused. Thank you for your patience during this incident.",
"name": "Network Delays Affecting MacOS Jobs",
"timestamp": "Nov \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e16:57\u003c/var\u003e - \u003cvar data-var='time'\u003e18:59\u003c/var\u003e UTC"
},
{
"code": "f2cgk04qswjg",
"impact": "minor",
"message": "We have identified a workaround for the issue preventing users from adding User Keys via the \"Authorize with GitHub\" option.\n\nWhile the \"Authorize with GitHub\" button is currently experiencing issues, users can successfully add SSH keys to their projects using our fully supported and documented manual process : https://circleci.com/docs/guides/integration/add-ssh-key/#steps-to-add-additional-ssh-keys\n\nThis workaround provides full functionality for adding SSH keys to your projects, effectively resolving the immediate impact. Our engineering team is actively monitoring this issue and will implement a permanent fix to restore the GitHub authorization flow.\n\nPost resolution Update - 17:30 UTC\nThe GitHub authorization functionality for adding User Keys has been fully restored as of 9:21 UTC. The \"Authorize with GitHub\" button is now working as expected in project settings.\n\nThe manual workaround previously provided is no longer necessary, though it remains a valid alternative method for adding SSH keys.\n\nThank you for your patience while we resolved this issue.",
"name": "Unable to add Github Authorized User Keys to Projects",
"timestamp": "Nov \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e23:32\u003c/var\u003e - Nov \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e00:16\u003c/var\u003e UTC"
}
],
"name": "November",
"year": 2025
},
{
"incidents": [
{
"code": "59dv3nb3kntv",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Deprecation of EoL Xcode Versions",
"timestamp": "Oct \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e - Oct \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e UTC"
},
{
"code": "sgplxlrhspf5",
"impact": "major",
"message": "This incident has been resolved. Thank you for your patience.",
"name": "No Linux jobs are running",
"timestamp": "Oct \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e15:04\u003c/var\u003e - \u003cvar data-var='time'\u003e15:24\u003c/var\u003e UTC"
},
{
"code": "vt9ntg2r2gnz",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Deprecation of EoL Xcode Versions",
"timestamp": "Oct \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e - Oct \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e UTC"
},
{
"code": "0y7q12npsl4h",
"impact": "critical",
"message": "This incident has been resolved. All job types are now operating normally with standard queue times. Linux machine and Remote Docker capacity has been fully restored following the AWS incident recovery.\n\nThank you for your patience.",
"name": "Build failures and delays due to upstream service disruption",
"timestamp": "Oct \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e07:49\u003c/var\u003e - \u003cvar data-var='time'\u003e22:15\u003c/var\u003e UTC"
},
{
"code": "lm01kk5xl4fd",
"impact": "minor",
"message": "The incident has been resolved. We appreciate your patience. We will continue to monitor throughout the weekend.",
"name": "Delay in Usage API Data",
"timestamp": "Oct \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e14:34\u003c/var\u003e - \u003cvar data-var='time'\u003e23:25\u003c/var\u003e UTC"
},
{
"code": "r09r2y9jlmfc",
"impact": "minor",
"message": "This incident has been resolved. Wait times are back to normal. We thank you for your patience while our engineers fixed the underlying cause.",
"name": "Delays starting Docker Jobs",
"timestamp": "Oct \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e20:29\u003c/var\u003e - \u003cvar data-var='time'\u003e22:23\u003c/var\u003e UTC"
},
{
"code": "9wr6c3gfn3kv",
"impact": "none",
"message": "This incident has been resolved. Both the Insights page and Approval Job buttons are fully operational. System monitoring confirms stable operation\n\nThank you for your patience while our engineers worked to resolve this issue.",
"name": "Insights Page Loading Errors and Approval Job Button Issues",
"timestamp": "Oct \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e22:45\u003c/var\u003e - \u003cvar data-var='time'\u003e22:57\u003c/var\u003e UTC"
},
{
"code": "9z6s13rbzb74",
"impact": "minor",
"message": "This incident has been resolved. The Insights UI is fully operational and all workflow data is accessible.\n\nThank you for your patience during this incident.",
"name": "Insights UI unresponsive",
"timestamp": "Oct \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e19:44\u003c/var\u003e - \u003cvar data-var='time'\u003e23:04\u003c/var\u003e UTC"
}
],
"name": "October",
"year": 2025
}
],
"start_time": "2025-10-01T00:00:00Z",
"time_zone": "UTC"
}
]
}