Live Domain Check

Is CircleCI Down? Check circleci.com Status and Outages

Run a live reachability check for circleci.com. Compare the regional responses with the problem you see in CircleCI.

Find CircleCI help and reporting links, specific checks, and step-by-step guidance below the live result.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked -

Verdict -

Response Time -

Final URL -

Regional checks 8 regions

Rate:

No ratings yet.

Is CircleCI working for you?

Share a quick update and see what other visitors are experiencing.

Loading community reports…

Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy

Understanding CircleCI connection and service problems

The CircleCI website, queued workflows, executor startup and commands inside a job are different checks.

The checker above requests circleci.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual CircleCI action that failed. A homepage response alone cannot verify an account, app workflow or transaction.

Looking for another service? Browse developer service checks.

CircleCI status information and official help

CircleCI service status

Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.

CircleCI help and reporting

Include the project, workflow/job and executor type.

Open circleci.com

Open the website in your browser and compare it with the result above.

Where to report problems with CircleCI

Open CircleCI help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.

Details to include in your report

Organisation/project, pipeline/workflow/job ID, executor, queue time and first failing log line.

Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to CircleCI.

What to check when CircleCI is not working

These are troubleshooting comparisons, not claims that CircleCI is currently experiencing a particular incident.

Start with the action that failed

Inspect whether a job is queued, cannot start an executor, or starts and fails in a specific command.

Narrow down the affected service

Compare another recent workflow on the same executor type and the relevant status component before rerunning a whole pipeline.

Read the actual checker response

A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.

How to check if CircleCI is down

Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
Run the circleci.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
Check for a service notice. Open CircleCI status and check whether the named service and incident time fit your error.
Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.

If CircleCI Is Not Working Only For You, Start Here

Use these local troubleshooting steps after the down-check workflow when CircleCI seems broken only for you. This section focuses on app, browser, account, and network fixes.

1. Compare browser sessions

Open circleci.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.

2. Preserve a working account session

Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader CircleCI issue.

3. Try another network

If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.

4. Capture support-ready evidence

Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting CircleCI support.

Frequently asked questions about CircleCI problems

Is CircleCI down, or is the problem limited to one feature?

Run the circleci.com check and compare its original timestamps and responses with your actual error. The CircleCI website, queued workflows, executor startup and commands inside a job are different checks.

Where can I report a problem with CircleCI?

Use the community buttons on this page to share whether the service works for you. For help from CircleCI, use the official help/reporting resource linked above. Include the project, workflow/job and executor type.

What should I check first when CircleCI is not working?

Inspect whether a job is queued, cannot start an executor, or starts and fails in a specific command. Compare another recent workflow on the same executor type and the relevant status component before rerunning a whole pipeline.

What information helps CircleCI support investigate?