Home
Cirrus CI
cirrus-ci.com · 2 records in CI runners, Storage · JSON
Records 2
cirrus-ci.com/CI runnerci-cd-runners/cirrus-ciJSONcomparereport an error
- Free allowance
- None: Cirrus CI shut down effective June 1, 2026
- Verdict
- deadthe offer or the service no longer exists
- Cost
- no price stated
- Identity
- emailno card, no phone
- Binding limit
- per-object-cap2 hours per free task; 16 CPUs on Linux; 8 CPU per task
- Evidence
- documented11 sources; a first-party page was read and the sentence quoted
- Freshness
- checked 2026-11-03checked 2026-11-03 (live)
| Free tier | none: Cirrus CI shut down effective June 1, 2026 unit none; metered on none |
|---|
| Price | none stated |
|---|
| Limits | - per-object-cap (binding) 2 hours per free task source
- request-rate 50 credits a month, equal to 10,000 Linux CPU-minutes source
- per-object-cap (binding) 16 CPUs on Linux; 8 CPU per task source
|
|---|
| Identity | email a GitHub account with the Cirrus app installed |
|---|
| Egress | no charge published |
|---|
| Per-object cap | a hard 2-hour limit on a free task; 16 CPUs on Linux and 8 CPU per task |
|---|
| Retention | credits reset monthly; task artifacts follow the repository configuration |
|---|
| Interface | git, cli a .cirrus.yml pipeline; GitHub App installation is the onboarding |
|---|
| Tooling | Linux, Windows, macOS and FreeBSD images; any shell |
|---|
| Reliability | on 2026-10-30 cirrus-ci.org did not resolve and cirrus-ci.com and api.cirrus-ci.com failed the TLS handshake, after the shutdown the vendor announced for June 1, 2026 |
|---|
| Notes | Cirrus Labs announced on April 7th, 2026 that it is joining OpenAI and that Cirrus CI will shut down effective June 1, 2026. The free allowance for public repositories ended with the service. Cirrus Runners, a separate product of the same vendor, stopped accepting new customers in the same announcement. |
|---|
| Evidence note | documented the shutdown is stated on the vendor's own announcement page, and the unreachable hosts are measured by probe |
|---|
| Parsed numbers | - has-free-tier 0
- per-object-cap 2 hours
- request-rate 50 credits / month
|
|---|
Evidence 11
| date | source | what it proved |
|---|
| 2026-10-22 | probe: https://cirrus-ci.org/faq/ | NXDOMAIN from 1.1.1.1 on 2026-10-22; cirrus-ci.com resolves to 34.117.12.6 but the TLS handshake fails |
| 2026-10-22 | web.archive.org/web/20260419203508/https://cirrus-ci.org/faq | the 2026-04-19 capture states 50 compute credits a month for public repositories, equal to 10,000 CPU-minutes for Linux tasks or 500 minutes for macOS tasks which always use 4 CPUs; a hard 2-hour limit on free tasks; 16 CPUs on Linux and 8 CPU per task |
| 2026-10-30 | cirruslabs.org/ | the vendor shut Cirrus CI down effective 1 June 2026 |
| 2026-10-30 | probe: https://cirrus-ci.org/faq/ | on 2026-10-30 a GET to cirrus-ci.org/faq/ failed at DNS resolution |
| 2026-10-30 | probe: https://cirrus-ci.com/ | on 2026-10-30 a GET to cirrus-ci.com failed the TLS handshake |
| 2026-10-30 | probe: https://api.cirrus-ci.com/graphql | on 2026-10-30 a GET to api.cirrus-ci.com/graphql failed the TLS handshake |
| 2026-10-30 | cirruslabs.org/ | the same announcement closes Cirrus Runners to new customers, a separate product of the vendor |
| 2026-11-03 | web.archive.org/web/20260419203508/https://cirrus-ci.org/faq | before the shutdown the free usage of Cirrus CI was capped at 50 compute credits a month, equal to 10,000 Linux CPU-minutes or 500 macOS minutes (archived copy of 2026-04-19) |
| 2026-11-03 | probe: https://cirrus-ci.org/faq/ | on 2026-11-03 a GET to cirrus-ci.org/faq/ failed at DNS resolution |
| 2026-11-03 | probe: https://cirrus-ci.com/ | on 2026-11-03 a GET to cirrus-ci.com failed the TLS handshake |
| 2026-11-03 | cirruslabs.org/ | the vendor shut Cirrus CI down effective 1 June 2026 |
More fields 1
| death | {"on": "2026-06-01","cause": "dead-service"} |
|---|
api.cirrus-ci.com/v1/task/1/artifactsstorage/cirrus-ciJSONcomparereport an error
- Free allowance
- Could not verify: the API host failed TLS negotiation from this environment, and the docs/pricing pages returned no extractable artifact-storage terms.
- Verdict
- deadthe offer or the service no longer exists
- Cost
- no price stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported4 sources; a third party said so
- Freshness
- checked 2026-11-03checked 2026-11-03 (inherited)
| Free tier | Could not verify: the API host failed TLS negotiation from this environment, and the docs/pricing pages returned no extractable artifact-storage terms. unit none; metered on none |
|---|
| Price | none stated |
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | not recorded |
|---|
| Interface | unknown |
|---|
| Tooling | not recorded |
|---|
| Parsed numbers | |
|---|
Evidence 4
| date | source | what it proved |
|---|
| 2026-10-21 | api.cirrus-ci.com/v1/task/1/artifacts | the text of Free tier, above |
| 2026-10-21 | cirrus-ci.org/pricing | cited as the basis of the rejection: Could not verify: the API host failed TLS negotiation from this environment, and the docs/pricing pages returned no extractable artifact-storage terms. |
| 2026-11-03 | cirruslabs.org/ | the vendor shut the Cirrus CI service down effective 2026-06-01, which ends its artifact storage |
| 2026-11-03 | cirruslabs.org/ | the vendor shut the Cirrus CI service down effective 2026-06-01 |
More fields 2
| dead end | {"failure_class": "quota","why": "Could not verify: the API host failed TLS negotiation from this environment, and the docs/pricing pages returned no extractable artifact-storage terms.","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
| death | {"on": "2026-06-01","cause": "dead-service"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field