We are conducting brownouts for the following Linux images, for both ARM64 and AMD64, on CircleCI and will be removing them from our platform on Sept 30, 2024:
We are conducting brownouts for the following Linux images, for both ARM64 and AMD64, on CircleCI and will be removing them from our platform on Sept 30, 2024:
We are conducting brownouts for the following Linux images, for both ARM64 and AMD64, on CircleCI and will be removing them from our platform on Sept 30, 2024:
We are conducting brownouts for the following Linux images, for both ARM64 and AMD64, on CircleCI and will be removing them from our platform on Sept 30, 2024:
We are conducting brownouts for the following Linux images, for both ARM64 and AMD64, on CircleCI and will be removing them from our platform on Sept 30, 2024:
We are conducting brownouts for the following Linux images, for both ARM64 and AMD64, on CircleCI and will be removing them from our platform on Sept 30, 2024:
We are conducting brownouts for the following Linux images, for both ARM64 and AMD64, on CircleCI and will be removing them from our platform on Sept 30, 2024:
Resolved -
This incident has been resolved
Jan 26, 18:12 UTC
Monitoring -
Starting at 15:30UTC some users using contexts saw builds not trigger due to an "Unauthorized" message. We have rolled out a fix for this issue and are monitoring the situation.
Jan 26, 17:56 UTC
Resolved -
We have pushed an update and are seeing approval jobs flowing correctly. If you are unable to approve a current approval job, please rerun the workflow or push an empty commit to trigger a new pipeline.
If you are still seeing errors, please contact CircleCI Support.
Jan 23, 00:06 UTC
Identified -
Some users may experience an issue when trying to approve an approval-type job. We are currently working on a fix.
Jan 22, 23:54 UTC
Resolved -
From 21:08 UTC to 22:21 UTC pipelines utilizing Dynamic Config may have encountered the following error: "Continuation config contains setup stanza whilst not in setup anymore."
This has been rolled back and we are seeing Dynamic Config pipelines pass through correctly. Please contact Support if you are continuing to see this error.
Jan 22, 22:00 UTC