CircleCI Status - Incident History

CircleCI Status - Incident History https://status.circleci.com Statuspage Wed, 27 Aug 2025 10:11:05 +0000 GitLab projects are not building <p><small>Aug <var data-var='date'>25</var>, <var data-var='time'>16:32</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>25</var>, <var data-var='time'>14:29</var> UTC</small><br><strong>Monitoring</strong> - On August 21st, GitLab had an incident which meant we did not get refresh tokens, which caused in the invalidation of the credentials we had stored.<br /><br />As a result, any trigger currently resulting in a Failed to get credential will no longer trigger pipelines in CircleCI. However, since the incident with GitLab has been resolved, simply deleting and re-creating the trigger within CircleCI will result in a new valid credential set and ensure pipelines can trigger moving forward.<br /><br />Customer Action Required: Delete and re-create the GitLab trigger within your CircleCI project</p><p><small>Aug <var data-var='date'>25</var>, <var data-var='time'>11:05</var> UTC</small><br><strong>Identified</strong> - We've identified the issue and are working on resolving the issue. For some customers you may need to take action before building resumes, we will follow this update with instructions shortly. Thank you for your patience.</p><p><small>Aug <var data-var='date'>25</var>, <var data-var='time'>09:46</var> UTC</small><br><strong>Investigating</strong> - GitLab jobs are currently not building due to a "Failed to get credential" error. We are currently investigating this issue.</p> Mon, 25 Aug 2025 16:32:39 +0000 https://status.circleci.com/incidents/8f33y7q7hq38 https://status.circleci.com/incidents/8f33y7q7hq38 Degraded workspace performance <p><small>Aug <var data-var='date'>24</var>, <var data-var='time'>22:00</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>24</var>, <var data-v