Field guide

How often should data center coolant be tested?

Quarterly for chemistry, monthly for the quick checks, and a full baseline at commissioning. Here is the practical schedule, the parameters that matter, and why the interval is shorter than most operators assume.

The short answer: test coolant chemistry quarterly, perform quick visual and pressure checks monthly, and capture a full laboratory baseline at commissioning, because every future result is only meaningful against that day-one record. Tighten the cadence for the first six months of a new loop and after any fluid addition.

What should be tested quarterly?

A quarterly laboratory panel for a propylene glycol (PG25) secondary loop should cover: pH, glycol concentration, corrosion inhibitor reserve, conductivity, dissolved metals (copper and iron are the tell-tales), particulate counts, and bacterial activity. The Open Compute Project's guidance for PG25 loops places acceptable pH between roughly 8.0 and 10.5; a reading drifting toward the bottom of that window is an early warning, not a passing grade.

What should be checked monthly?

Monthly checks need no laboratory: fluid level and make-up volume (rising make-up is a leak talking), visual clarity and colour against a retained reference sample, loop pressure and differential pressure trends, and a walk of leak-detection points. Fifteen minutes a month catches a remarkable share of problems while they are still cheap.

Why does the interval matter so much?

Because coolant fails by trend, not by event. Corrosion inhibitors are consumed continuously; once the reserve is exhausted, metal loss begins immediately and particles travel to the narrowest point in the system, which in a direct-to-chip loop is a cold-plate channel finer than a human hair. Between a good reading and a fouling event there is no alarm, only the test you did or did not run.

What does a testing program cost against the alternative?

A disciplined quarterly program for a mid-size loop runs in the low thousands per year. A single fouling or corrosion event above a populated rack row can consume hundreds of thousands of dollars in hardware and weeks of remediation. The arithmetic is not subtle, which is why equipment manufacturers increasingly make documented fluid quality control a warranty condition.

The schedule, in one table

CadenceChecks
CommissioningFull lab baseline: chemistry, cleanliness, bacteria. The reference record for the life of the loop.
MonthlyLevel and make-up volume, clarity, pressure and ΔP trend, detection walk.
QuarterlyLab panel: pH, glycol %, inhibitor reserve, conductivity, metals, particulates, bacteria.
After any fluid eventRe-test two weeks after top-up, mixing, or component replacement.
AnnuallyProgram review: trend analysis, detection re-test, warranty file update.

References: Open Compute Project cooling environments guidance for propylene glycol loops; ASHRAE TC 9.9 datacom series; equipment manufacturers' fluid quality requirements. Specific limits vary by fluid and OEM: your loop's specification governs.

Want your baseline?

A Loop Health Audit gives you the day-one record every future test is measured against.

Get in touch