Public water system record

OAKLEY CITY OF

Federal records show 2 health-based violations and 11 monitoring/reporting issues for OAKLEY CITY OF in the last ten years. The most serious issue in this window was a resolved Consumer Confidence Report violation.

  • ID5160035
  • OAKLEY
  • ID
  • 821 served

System profile

Source water Groundwater
ZIP 83346
Acute record in 10 years No

Verify this system on EPA ECHO →

Health-based records
2
Last 10 years
Monitoring issues
11
Last 10 years
Resolved vs. unresolved
8 resolved • 5 unresolved
PWSID
ID5160035
EPA public water system identifier

Check your address

Check whether your address is served by this system.

Use the normal Tap Truth address lookup to verify whether a specific home resolves to OAKLEY CITY OF.

Runs the same address-to-system lookup used on the homepage. Address suggestions by Mapbox

Health-based violations

Violation data reflects EPA records through March 2026. For the most current status, visit the EPA ECHO database.

Contaminant Rule family Start date Status Acute
Consumer Confidence Report
Treatment technique failure
110 Nov 28, 2024 Resolved No
LEAD AND COPPER RULE REVISIONS
Treatment technique failure
350 Oct 17, 2024 Resolved No

Monitoring and reporting issues

Monitoring violations are administrative records. They mean required testing or reporting was missed, not that a contaminant was found above a safe level.

Issue Start date Status
Lead and Copper Rule
Monitoring and reporting
Oct 1, 2025 Unresolved
LEAD AND COPPER RULE REVISIONS
RPT
Jul 2, 2025 Unresolved
Monitoring and Reporting
OTHER
Mar 3, 2025 Unresolved
LEAD AND COPPER RULE REVISIONS
RPT
Oct 17, 2024 Resolved
Chlorine
Monitoring and reporting
Oct 1, 2024 Resolved
E. coli
Monitoring and reporting
Jun 16, 2024 Unresolved
Chlorine
Monitoring and reporting
Jul 1, 2023 Resolved
E. coli
Monitoring and reporting
Feb 7, 2023 Resolved
Lead and Copper Rule
Monitoring and reporting
Dec 30, 2022 Unresolved
Chlorine
Monitoring and reporting
Jul 1, 2018 Resolved
Consumer Confidence Report
Monitoring violation
Jun 1, 2017 Resolved