CircleCI is a continuous integration and delivery platform.
Real-time check from multiple global locations
--
Response Time
--
Status Code
--
Region
Use our status checker above to confirm whether the issue is with CircleCI or your local connection.
Visit CircleCI's status page for official updates, or see our CircleCI Status Page guide.
Get instant alerts for future CircleCI outages with PerkyDash's free uptime monitoring.
If your app depends on CircleCI, create an emergency status page to keep your users informed.
Set up free monitoring for CircleCI and get instant alerts via email, Slack, or webhooks when it goes down.
Builds stuck in queue can indicate CircleCI capacity issues or outages. Check our status above and CircleCI's Build Processing component. If CircleCI is up, check if you've exceeded your resource class limits or if specific executors are affected.
Yes, webhooks to GitHub/Bitbucket may fail during outages, preventing builds from triggering. Status updates to your VCS may also be delayed. Once service resumes, you may need to manually re-trigger affected builds.
Unexpected failures during outages may show as infrastructure errors rather than test failures. Check the job output for CircleCI-specific error messages. Infrastructure failures typically don't consume build credits.
Self-hosted runners still require CircleCI's control plane to receive jobs. During outages, runners will be idle even if healthy. Jobs queue on CircleCI and dispatch once service resumes.