Skip to content

Outage tracker / CircleCI

Is CircleCI down?

I'm having a problem

Vendor reports no incidentWhat CircleCI reports

CircleCI reports no incident on its status page.

As of the last successful poll, 2026-10-23 16:43 UTC.

CircleCI's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of CircleCI pass from all 10 regions we check.

As of Oct 23, 2026, 4:50 PM UTC, RealUptime's checks of CircleCI passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 23, 2026, 4:50 PM UTC
US-East118 msChecks passing
US-West140 msChecks passing
Europe141 msChecks passing
Asia-Pacific248 msChecks passing
US-Central168 msChecks passing
Canada152 msChecks passing
UK127 msChecks passing
Southeast Asia320 msChecks passing
Australia366 msChecks passing
South America307 msChecks passing
their status pagetheir claim, not our reading

CircleCI reports: All systems operational (“All Systems Operational”)

from CircleCI's own status page, checked Oct 23, 2026, 4:41 PM UTC
CircleCI's own status page shows no incident, and our checks of CircleCI pass right now.

CircleCI's own component breakdown, as they publish it

  • AWSOperational
  • Atlassian Bitbucket APIOperational
  • Docker JobsOperational
  • Atlassian Bitbucket Source downloadsOperational
  • Google Cloud Platform Google Cloud DNSOperational
  • Machine JobsOperational
  • Atlassian Bitbucket SSHOperational
  • Google Cloud Platform Google Cloud NetworkingOperational
  • macOS JobsOperational
  • Atlassian Bitbucket WebhooksOperational
  • Google Cloud Platform Google Cloud StorageOperational
  • Windows JobsOperational
  • Docker HubOperational
  • Google Cloud Platform Google Compute EngineOperational
  • Pipelines & WorkflowsOperational
  • CircleCI APIOperational
  • GitHub Git OperationsOperational
  • mailgun APIOperational
  • CircleCI UIOperational
  • GitHub Pull RequestsOperational
  • mailgun Outbound DeliveryOperational
  • ArtifactsOperational
  • GitHub API RequestsOperational
  • mailgun SMTPOperational
  • GitHub PackagesOperational
  • OpenAIOperational
  • RunnerOperational
  • Auth0 User AuthenticationOperational
  • CircleCI WebhooksOperational
  • GitHub WebhooksOperational
  • CircleCI InsightsOperational
  • GitLabOperational
  • CircleCI ReleasesOperational
  • Docker RegistryOperational
  • Docker AuthenticationOperational
  • Notifications & Status UpdatesOperational
  • Anthropic api.anthropic.comOperational
  • Billing & AccountOperational
  • packagecloud.ioOperational

These are CircleCI's components, named and scored by CircleCI. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is CircleCI's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

CircleCI response time, by region

US-East
434msp95 · latest
500ms250ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 355ms2026-09-25 UTC: p95 224ms2026-09-26 UTC: p95 218ms2026-09-27 UTC: p95 178ms2026-09-28 UTC: p95 198ms2026-09-29 UTC: p95 177ms2026-09-30 UTC: p95 190ms2026-10-01 UTC: p95 192ms2026-10-02 UTC: p95 190ms2026-10-03 UTC: p95 182ms2026-10-04 UTC: p95 176ms2026-10-05 UTC: p95 205ms2026-10-06 UTC: p95 356ms2026-10-07 UTC: p95 266ms2026-10-08 UTC: p95 346ms2026-10-09 UTC: p95 228ms2026-10-10 UTC: p95 185ms2026-10-11 UTC: p95 188ms2026-10-12 UTC: p95 188ms2026-10-13 UTC: p95 251ms2026-10-14 UTC: p95 194ms2026-10-15 UTC: p95 200ms2026-10-16 UTC: p95 192ms2026-10-17 UTC: p95 212ms2026-10-18 UTC: p95 227ms2026-10-19 UTC: p95 195ms2026-10-20 UTC: p95 253ms2026-10-21 UTC: p95 245ms2026-10-22 UTC: p95 230ms2026-10-23 UTC: p95 434ms
Sep 24Oct 8Oct 23
US-West
322msp95 · latest
500ms250ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 330ms2026-09-25 UTC: p95 237ms2026-09-26 UTC: p95 281ms2026-09-27 UTC: p95 249ms2026-09-28 UTC: p95 189ms2026-09-29 UTC: p95 312ms2026-09-30 UTC: p95 320ms2026-10-01 UTC: p95 290ms2026-10-02 UTC: p95 250ms2026-10-03 UTC: p95 210ms2026-10-04 UTC: p95 318ms2026-10-05 UTC: p95 257ms2026-10-06 UTC: p95 291ms2026-10-07 UTC: p95 342ms2026-10-08 UTC: p95 194ms2026-10-09 UTC: p95 227ms2026-10-10 UTC: p95 276ms2026-10-11 UTC: p95 301ms2026-10-12 UTC: p95 280ms2026-10-13 UTC: p95 309ms2026-10-14 UTC: p95 233ms2026-10-15 UTC: p95 295ms2026-10-16 UTC: p95 270ms2026-10-17 UTC: p95 264ms2026-10-18 UTC: p95 322ms2026-10-19 UTC: p95 247ms2026-10-20 UTC: p95 276ms2026-10-21 UTC: p95 413ms2026-10-22 UTC: p95 303ms2026-10-23 UTC: p95 322ms
Sep 24Oct 8Oct 23
Europe
239msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 287ms2026-09-25 UTC: p95 266ms2026-09-26 UTC: p95 281ms2026-09-27 UTC: p95 268ms2026-09-28 UTC: p95 258ms2026-09-29 UTC: p95 333ms2026-09-30 UTC: p95 370ms2026-10-01 UTC: p95 351ms2026-10-02 UTC: p95 255ms2026-10-03 UTC: p95 310ms2026-10-04 UTC: p95 285ms2026-10-05 UTC: p95 266ms2026-10-06 UTC: p95 243ms2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 246ms2026-10-09 UTC: p95 248ms2026-10-10 UTC: p95 266ms2026-10-11 UTC: p95 253ms2026-10-12 UTC: p95 252ms2026-10-13 UTC: p95 276ms2026-10-14 UTC: p95 255ms2026-10-15 UTC: p95 274ms2026-10-16 UTC: p95 269ms2026-10-17 UTC: p95 300ms2026-10-18 UTC: p95 432ms2026-10-19 UTC: p95 313ms2026-10-20 UTC: p95 244ms2026-10-21 UTC: p95 277ms2026-10-22 UTC: p95 307ms2026-10-23 UTC: p95 239ms
Sep 24Oct 8Oct 23
Asia-Pacific
652msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 382ms2026-09-25 UTC: p95 501ms2026-09-26 UTC: p95 464ms2026-09-27 UTC: p95 422ms2026-09-28 UTC: p95 452ms2026-09-29 UTC: p95 444ms2026-09-30 UTC: p95 560ms2026-10-01 UTC: p95 487ms2026-10-02 UTC: p95 520ms2026-10-03 UTC: p95 822ms2026-10-04 UTC: p95 712ms2026-10-05 UTC: p95 580ms2026-10-06 UTC: p95 582ms2026-10-07 UTC: p95 694ms2026-10-08 UTC: p95 532ms2026-10-09 UTC: p95 536ms2026-10-10 UTC: p95 546ms2026-10-11 UTC: p95 398ms2026-10-12 UTC: p95 399ms2026-10-13 UTC: p95 558ms2026-10-14 UTC: p95 546ms2026-10-15 UTC: p95 646ms2026-10-16 UTC: p95 692ms2026-10-17 UTC: p95 410ms2026-10-18 UTC: p95 744ms2026-10-19 UTC: p95 581ms2026-10-20 UTC: p95 647ms2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 652ms
Sep 24Oct 8Oct 23
US-Central
267msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 266ms2026-09-25 UTC: p95 175ms2026-09-26 UTC: p95 206ms2026-09-27 UTC: p95 192ms2026-09-28 UTC: p95 195ms2026-09-29 UTC: p95 177ms2026-09-30 UTC: p95 957ms2026-10-01 UTC: p95 183ms2026-10-02 UTC: p95 194ms2026-10-03 UTC: p95 169ms2026-10-04 UTC: p95 163ms2026-10-05 UTC: p95 225ms2026-10-06 UTC: p95 366ms2026-10-07 UTC: p95 312ms2026-10-08 UTC: p95 184ms2026-10-09 UTC: p95 174ms2026-10-10 UTC: p95 189ms2026-10-11 UTC: p95 208ms2026-10-12 UTC: p95 201ms2026-10-13 UTC: p95 204ms2026-10-14 UTC: p95 207ms2026-10-15 UTC: p95 181ms2026-10-16 UTC: p95 209ms2026-10-17 UTC: p95 229ms2026-10-18 UTC: p95 171ms2026-10-19 UTC: p95 194ms2026-10-20 UTC: p95 202ms2026-10-21 UTC: p95 353ms2026-10-22 UTC: p95 251ms2026-10-23 UTC: p95 267ms
Sep 24Oct 8Oct 23
Canada
224msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 306ms2026-09-25 UTC: p95 221ms2026-09-26 UTC: p95 201ms2026-09-27 UTC: p95 243ms2026-09-28 UTC: p95 229ms2026-09-29 UTC: p95 204ms2026-09-30 UTC: p95 250ms2026-10-01 UTC: p95 208ms2026-10-02 UTC: p95 222ms2026-10-03 UTC: p95 228ms2026-10-04 UTC: p95 214ms2026-10-05 UTC: p95 209ms2026-10-06 UTC: p95 239ms2026-10-07 UTC: p95 206ms2026-10-08 UTC: p95 226ms2026-10-09 UTC: p95 232ms2026-10-10 UTC: p95 230ms2026-10-11 UTC: p95 191ms2026-10-12 UTC: p95 217ms2026-10-13 UTC: p95 198ms2026-10-14 UTC: p95 177ms2026-10-15 UTC: p95 240ms2026-10-16 UTC: p95 200ms2026-10-17 UTC: p95 240ms2026-10-18 UTC: p95 205ms2026-10-19 UTC: p95 189ms2026-10-20 UTC: p95 197ms2026-10-21 UTC: p95 284ms2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 224ms
Sep 24Oct 8Oct 23
UK
241msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 266ms2026-09-25 UTC: p95 231ms2026-09-26 UTC: p95 251ms2026-09-27 UTC: p95 266ms2026-09-28 UTC: p95 332ms2026-09-29 UTC: p95 221ms2026-09-30 UTC: p95 245ms2026-10-01 UTC: p95 263ms2026-10-02 UTC: p95 264ms2026-10-03 UTC: p95 273ms2026-10-04 UTC: p95 240ms2026-10-05 UTC: p95 249ms2026-10-06 UTC: p95 236ms2026-10-07 UTC: p95 314ms2026-10-08 UTC: p95 237ms2026-10-09 UTC: p95 231ms2026-10-10 UTC: p95 248ms2026-10-11 UTC: p95 247ms2026-10-12 UTC: p95 243ms2026-10-13 UTC: p95 180ms2026-10-14 UTC: p95 196ms2026-10-15 UTC: p95 172ms2026-10-16 UTC: p95 172ms2026-10-17 UTC: p95 169ms2026-10-18 UTC: p95 357ms2026-10-19 UTC: p95 240ms2026-10-20 UTC: p95 179ms2026-10-21 UTC: p95 250ms2026-10-22 UTC: p95 265ms2026-10-23 UTC: p95 241ms
Sep 24Oct 8Oct 23
Southeast Asia
589msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 766ms2026-09-25 UTC: p95 727ms2026-09-26 UTC: p95 760ms2026-09-27 UTC: p95 680ms2026-09-28 UTC: p95 866ms2026-09-29 UTC: p95 617ms2026-09-30 UTC: p95 634ms2026-10-01 UTC: p95 592ms2026-10-02 UTC: p95 627ms2026-10-03 UTC: p95 495ms2026-10-04 UTC: p95 542ms2026-10-05 UTC: p95 550ms2026-10-06 UTC: p95 677ms2026-10-07 UTC: p95 831ms2026-10-08 UTC: p95 596ms2026-10-09 UTC: p95 579ms2026-10-10 UTC: p95 548ms2026-10-11 UTC: p95 623ms2026-10-12 UTC: p95 722ms2026-10-13 UTC: p95 713ms2026-10-14 UTC: p95 512ms2026-10-15 UTC: p95 504ms2026-10-16 UTC: p95 552ms2026-10-17 UTC: p95 637ms2026-10-18 UTC: p95 609ms2026-10-19 UTC: p95 552ms2026-10-20 UTC: p95 634ms2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 507ms2026-10-23 UTC: p95 589ms
Sep 24Oct 8Oct 23
Australia
528msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 625ms2026-09-25 UTC: p95 648ms2026-09-26 UTC: p95 583ms2026-09-27 UTC: p95 551ms2026-09-28 UTC: p95 718ms2026-09-29 UTC: p95 749ms2026-09-30 UTC: p95 685ms2026-10-01 UTC: p95 544ms2026-10-02 UTC: p95 598ms2026-10-03 UTC: p95 493ms2026-10-04 UTC: p95 600ms2026-10-05 UTC: p95 718ms2026-10-06 UTC: p95 562ms2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 548ms2026-10-09 UTC: p95 512ms2026-10-10 UTC: p95 471ms2026-10-11 UTC: p95 497ms2026-10-12 UTC: p95 488ms2026-10-13 UTC: p95 638ms2026-10-14 UTC: p95 491ms2026-10-15 UTC: p95 557ms2026-10-16 UTC: p95 444ms2026-10-17 UTC: p95 534ms2026-10-18 UTC: p95 527ms2026-10-19 UTC: p95 530ms2026-10-20 UTC: p95 479ms2026-10-21 UTC: p95 520ms2026-10-22 UTC: p95 521ms2026-10-23 UTC: p95 528ms
Sep 24Oct 8Oct 23
South America
336msp95 · latest
1s500ms0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 501ms2026-09-25 UTC: p95 631ms2026-09-26 UTC: p95 528ms2026-09-27 UTC: p95 555ms2026-09-28 UTC: p95 555ms2026-09-29 UTC: p95 508ms2026-09-30 UTC: p95 543ms2026-10-01 UTC: p95 481ms2026-10-02 UTC: p95 592ms2026-10-03 UTC: p95 513ms2026-10-04 UTC: p95 507ms2026-10-05 UTC: p95 478ms2026-10-06 UTC: p95 403ms2026-10-07 UTC: p95 522ms2026-10-08 UTC: p95 452ms2026-10-09 UTC: p95 487ms2026-10-10 UTC: p95 514ms2026-10-11 UTC: p95 535ms2026-10-12 UTC: p95 515ms2026-10-13 UTC: p95 467ms2026-10-14 UTC: p95 728ms2026-10-15 UTC: p95 481ms2026-10-16 UTC: p95 503ms2026-10-17 UTC: p95 462ms2026-10-18 UTC: p95 470ms2026-10-19 UTC: p95 347ms2026-10-20 UTC: p95 538ms2026-10-21 UTC: p95 534ms2026-10-22 UTC: p95 493ms2026-10-23 UTC: p95 336ms
Sep 24Oct 8Oct 23

Check your own site while you wait on CircleCI

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not CircleCI. It cannot diagnose CircleCI's own systems.

Email me when CircleCI reports an incident on its status page, and again when it reports it resolved.

Get an email when CircleCI reports an incident

Email me when CircleCI reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is CircleCI's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 118msstatus code: 401checked: Oct 23, 2026, 4:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach CircleCI normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 140msstatus code: 401checked: Oct 23, 2026, 4:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach CircleCI normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 168msstatus code: 401checked: Oct 23, 2026, 4:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach CircleCI normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 152msstatus code: 401checked: Oct 23, 2026, 4:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach CircleCI normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 307msstatus code: 401checked: Oct 23, 2026, 4:50 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach CircleCI normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 141msstatus code: 401checked: Oct 23, 2026, 4:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach CircleCI normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 127msstatus code: 401checked: Oct 23, 2026, 4:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach CircleCI normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 248msstatus code: 401checked: Oct 23, 2026, 4:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach CircleCI normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 320msstatus code: 401checked: Oct 23, 2026, 4:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach CircleCI normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 366msstatus code: 401checked: Oct 23, 2026, 4:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach CircleCI normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using CircleCI, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for CircleCI yet, which is not evidence that nothing is wrong.

Recent probe events

Increased Docker gen2 wait times, 1h 24mdeclared on their status page2026-10-21
Increased wait times for macOS jobs on m4pro.large, 2h 16mdeclared on their status page2026-10-20
Delays starting macOS jobs that use Xcode 26.6.0, 1h 13mdeclared on their status page2026-10-14
Delay in data appearing in UI and API, 14h 36mdeclared on their status page2026-10-09
Elevated wait times for machine jobs, 3h 35mdeclared on their status page2026-10-08
Increased task wait times for Docker Gen2, 1h 11mdeclared on their status page2026-10-07
Elevated level of infra fails on customer jobs, 54mdeclared on their status page2026-10-07
Delay on starting Machine Job Tasks, 26mdeclared on their status page2026-10-07

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring CircleCI since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for CircleCI covering any window you pick, with our check readings and CircleCI's own claim at the time, side by side.

Full check history for CircleCI: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

CircleCI uptime by RealUptime's checksLive, from this page's own readings.
[![CircleCI uptime by RealUptime's checks](https://realuptime.io/outages/circleci/badge.svg?days=30)](https://realuptime.io/outages/circleci)
<a href="https://realuptime.io/outages/circleci"><img src="https://realuptime.io/outages/circleci/badge.svg?days=30" alt="CircleCI uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is CircleCI down?", https://realuptime.io/outages/circleci. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional
https://circleci.com/api/v2/me
secondary
https://status.circleci.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: circleci.com

RealUptime is not affiliated with CircleCI; the name identifies what we checked, and nothing here speaks for CircleCI's own team. We send a single web request to CircleCI from 10 regions on our own schedule and time the response. We do not see inside CircleCI's systems, do not use an account or real transaction, and are not the same signal CircleCI's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for CircleCI is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.