CircleCI Status

Resolved: GitHub API error rates have recovered to normal levels.

During 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.

• You should re-push commits or use the UI to manually trigger pipelines that didn't start.
• Pipelines in a stuck running state should be canceled and rerun.

If you encounter any issues please contact CircleCI support.

Monitoring: We are seeing signs of recovery from the GitHub API.

We will stay in a monitoring state to verify that the API error rate has recovered.

Identified: We are also seeing errors processing push event webhooks due to the upstream API outage.

Users may need to retry pipelines for these push events.

Identified: We have identified an issue with GitHub API requests that may cause some customers to see workflows stuck in a running state or workflows fail to start.

GitHub has reported incidents on the APIs

https://www.githubstatus.com/incidents/ph5nns5y4gxj https://www.githubstatus.com/incidents/8vfyvq16hzh9

We are monitoring the stability of GitHub APIs and will update this page as more information is available.

Resolved: 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.

Customers 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.

We thank you for your patience.

Monitoring: What's happening The upstream incident affecting GitHub has been mitigated and is now being monitored on GitHub's side. You can follow GitHub's status at https://www.githubstatus.com/.

What can you expect Access to the CircleCI web app, sign-in, and pipeline and workflow processing are returning to normal. You may still see intermittent errors or delayed scheduled pipelines and workflows as systems stabilize. Thank you for your patience while we monitor for full recovery.

Identified: We are continuing to see high failure rates from GitHub APIs which are impacting login and workflow processing.

We will continue to monitor the GitHub API for recovery.

Investigating: We're investigating an issue where customers may see errors loading the CircleCI web app and signing in, along with pipelines and scheduled workflows failing to start or running late. This is related to an ongoing incident affecting GitHub. You can follow GitHub's status at https://www.githubstatus.com/incidents/gxycch3076xk. Our engineers are actively investigating.

We will provide another update as soon as we have more information to share.

Resolved: 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.

We thank you for your patience while our team worked on implementing a fix.

Monitoring: A subset of customers may have experienced errors loading app.circleci.com starting at 03:18 UTC. A fix has been deployed and we are monitoring for full recovery.

Thank you for your patience while our engineers confirm recovery. We will provide another update shortly.

Resolved: GitHub API error rates have recovered to normal levels.

During 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.

• You should re-push commits or use the UI to manually trigger pipelines that didn't start.
• Pipelines in a stuck running state should be canceled and rerun.

If you encounter any issues please contact CircleCI support.

Monitoring: We are seeing signs of recovery from the GitHub API.

We will stay in a monitoring state to verify that the API error rate has recovered.

Identified: We are also seeing errors processing push event webhooks due to the upstream API outage.

Users may need to retry pipelines for these push events.

Identified: We have identified an issue with GitHub API requests that may cause some customers to see workflows stuck in a running state or workflows fail to start.

GitHub has reported incidents on the APIs

https://www.githubstatus.com/incidents/ph5nns5y4gxj https://www.githubstatus.com/incidents/8vfyvq16hzh9

We are monitoring the stability of GitHub APIs and will update this page as more information is available.

Resolved: GitHub API error rates have recovered to normal levels.

During 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.

• You should re-push commits or use the UI to manually trigger pipelines that didn't start.
• Pipelines in a stuck running state should be canceled and rerun.

If you encounter any issues please contact CircleCI support.

Monitoring: We are seeing signs of recovery from the GitHub API.

We will stay in a monitoring state to verify that the API error rate has recovered.

Identified: We are also seeing errors processing push event webhooks due to the upstream API outage.

Users may need to retry pipelines for these push events.

Identified: We have identified an issue with GitHub API requests that may cause some customers to see workflows stuck in a running state or workflows fail to start.

GitHub has reported incidents on the APIs

https://www.githubstatus.com/incidents/ph5nns5y4gxj https://www.githubstatus.com/incidents/8vfyvq16hzh9

We are monitoring the stability of GitHub APIs and will update this page as more information is available.