50%
“a 50% decrease in overall production outages”
As published on harness.io, October 2026. Captured by usedby on Oct 7, 2026.
What happened
Ancestry uses Harness to run its CI/CD pipelines with centralized governance, replacing many separate Jenkins instances. This lets the architecture team apply standards and best practices, such as canary deployments, across all pipelines with a single change.
Summary written by usedby from the source page, in English. The figures are those of Harness and Ancestry, not ours.
- 3x“a 3x increase in deployment velocity”
- 97%“Ancestry’s centralized testing tool’s adoption rate rose to 97%”
- 350“onboard 350 systems in the first year”
- 85%“an 85% reduction in effort when compared to Jenkins”
The increase in pipeline governance and consistent usage of best practices enabled by Harness also resulted in a 50% decrease in overall production outages and significantly reduced outages related to deployment issues.
Once teams are using a Harness pipeline, it’s easy to add additional mandatory steps
What the story claims, and what we checked
We compared the story with its live page on Oct 7, 2026.
- The figure: 50%CheckedPrinted word for word on the page, near the name of Ancestry.
- The passage quoted aboveCheckedCopied word for word from the page, near the name of Ancestry.
- The publication dateCheckedRead from the page’s own metadata, never guessed.
- Ancestry uses HarnessCheckedConfirmed line. Latest check across sources: Oct 7, 2026.
- The result itselfNot checkedWe quote it; we did not measure it.
More stories
Same company, same tool or same industry.
