PEYTON, CO · El Paso County
PEYTON PINES Water System
Consumer Confidence Report status
PEYTON PINES must publish a Consumer Confidence Report — the annual drinking water quality report covering calendar year 2026 — by July 1, 2027.
As of August 1, 2026, EPA's federal records show no open violations for PEYTON PINES.
Data sourced from the EPA ECHO database (SDWA bulk download), last refreshed August 1, 2026. This is a record-keeping and public-information tool — it does not replace Colorado’s official records. Always confirm current status with Colorado before making decisions based on this information.
System facts
- System ID (PWSID)
- CO0121610
- System type
- Community Water System
- Population served
- 56
- Service connections
- 22
- Ownership
- privately owned
- Water source
- groundwater (wells)
PEYTON PINES is one of 1,060 community water systems in Colorado in the 500 or fewer people size category, serving 56 people from groundwater.
As of August 1, 2026, its federal record holds 6 entries between 2008 and 2023, all of which EPA lists as closed. Nothing has been added since 2023.
All 6 are monitoring and reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset — rather than findings about the water itself. The record involves the Stage 2 Disinfectants and Disinfection Byproducts Rule, synthetic organic chemicals, and the Total Coliform Rules.
Violation history
Monitoring and Reporting (DBP)
—TTHM
January 1, 2023 – September 22, 2025
ResolvedMonitoring and Reporting (DBP)
—TTHM
January 1, 2020 – October 7, 2021
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
May 1, 2010 – May 31, 2010
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
July 1, 2009 – July 26, 2010
ResolvedMonitoring, Regular
—Dinoseb
January 1, 2008 – December 31, 2010
ResolvedMonitoring, Regular
—Dalapon
January 1, 2008 – December 31, 2010
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2023 – September 22, 2025 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| January 1, 2020 – October 7, 2021 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| May 1, 2010 – May 31, 2010 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| July 1, 2009 – July 26, 2010 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| January 1, 2008 – December 31, 2010 | Monitoring, Regular | Dinoseb | — | Resolved |
| January 1, 2008 – December 31, 2010 | Monitoring, Regular | Dalapon | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- January 26, 2026State Violation/Reminder Notice1 linked violation
- January 26, 2026State Compliance achieved2 linked violations
- January 26, 2026State Public Notification requested1 linked violation
- January 26, 2026State Public Notification requested1 linked violation
- January 26, 2026State Violation/Reminder Notice1 linked violation
- September 22, 2025State Compliance achieved2 linked violations
- November 27, 2024State Compliance achieved1 linked violation
- November 4, 2024State Violation/Reminder Notice1 linked violation
- November 4, 2024State Public Notification requested2 linked violations
- November 4, 2024State Violation/Reminder Notice2 linked violations
- November 4, 2024State Public Notification requested1 linked violation
- January 21, 2024State Compliance achieved1 linked violation
- January 16, 2024State Public Notification requested1 linked violation
- January 16, 2024State Violation/Reminder Notice1 linked violation
- October 7, 2021State Compliance achieved2 linked violations
- July 16, 2021State Boil Water Ordergeneral compliance action — not tied to a specific violation on record
- October 30, 2020State Public Notification requested2 linked violations
- October 30, 2020State Violation/Reminder Notice2 linked violations
- August 28, 2017State Public Notification received1 linked violation
- August 12, 2017State Compliance achieved1 linked violation
- August 11, 2017State Public Notification requested1 linked violation
- August 11, 2017State Violation/Reminder Notice1 linked violation
- March 4, 2015State Compliance achieved5 linked violations
- March 2, 2015State Compliance achieved1 linked violation
- June 23, 2013State Public Notification received2 linked violations
- February 15, 2013State Public Notification requested1 linked violation
- February 15, 2013State Violation/Reminder Notice1 linked violation
- July 11, 2012State Compliance achieved1 linked violation
- June 25, 2012State Public Notification received1 linked violation
- November 7, 2011State Violation/Reminder Notice1 linked violation
- November 7, 2011State Public Notification requested1 linked violation
- July 12, 2011State Public Notification received8 linked violations
- February 9, 2011State Violation/Reminder Notice1 linked violation
- February 9, 2011State Public Notification requested1 linked violation
- February 9, 2011State Violation/Reminder Notice1 linked violation
- February 9, 2011State Public Notification requested1 linked violation
- February 9, 2011State Violation/Reminder Notice1 linked violation
- February 9, 2011State Public Notification requested1 linked violation
- February 9, 2011State Violation/Reminder Notice1 linked violation
- February 9, 2011State Public Notification requested1 linked violation
- February 9, 2011State Violation/Reminder Notice1 linked violation
- February 9, 2011State Public Notification requested1 linked violation
- July 26, 2010State Compliance achieved1 linked violation
- July 12, 2010State Compliance achieved2 linked violations
- June 24, 2010State Public Notification requested1 linked violation
- June 24, 2010State Violation/Reminder Notice1 linked violation
- June 24, 2010State Public Notification requested1 linked violation
- June 24, 2010State Violation/Reminder Notice1 linked violation
- February 5, 2010State Compliance achieved1 linked violation
- February 1, 2010State Compliance achieved1 linked violation
- September 11, 2009State Public Notification requested1 linked violation
- September 11, 2009State Public Notification requested1 linked violation
- September 11, 2009State Violation/Reminder Notice1 linked violation
- September 11, 2009State Violation/Reminder Notice1 linked violation
- July 24, 2009State Violation/Reminder Notice1 linked violation
- July 24, 2009State Public Notification requested1 linked violation
- February 11, 2009State Compliance achieved1 linked violation
- February 3, 2009State Violation/Reminder Notice1 linked violation
- February 3, 2009State Public Notification requested1 linked violation
- August 25, 2008State Compliance achieved4 linked violations
- May 23, 2008State Compliance achieved4 linked violations
- April 4, 2008State Compliance achieved4 linked violations
- February 11, 2008State Violation/Reminder Notice1 linked violation
- February 11, 2008State Public Notification requested2 linked violations
- November 15, 2007State Compliance achieved1 linked violation
- August 10, 2007State Violation/Reminder Notice1 linked violation
- August 10, 2007State Public Notification requested1 linked violation
- May 9, 2007State Public Notification requested1 linked violation
- May 9, 2007State Violation/Reminder Notice1 linked violation
- May 9, 2007State Public Notification requested2 linked violations
- February 14, 2007State Public Notification requested1 linked violation
- February 14, 2007State Violation/Reminder Notice1 linked violation
- October 31, 2006State Compliance achieved2 linked violations
- October 5, 2006State Public Notification requested1 linked violation
- October 5, 2006State Violation/Reminder Notice1 linked violation
- August 18, 2006State Public Notification requested1 linked violation
- August 18, 2006State Violation/Reminder Notice1 linked violation
- June 7, 2006State Public Notification requested1 linked violation
- June 7, 2006State Violation/Reminder Notice1 linked violation
- April 19, 2005State Compliance achieved11 linked violations
- April 19, 2005State Compliance achieved1 linked violation
- February 22, 2005State Public Notification requested12 linked violations
- February 22, 2005State Violation/Reminder Notice11 linked violations
- February 21, 2005State Public Notification requested1 linked violation
- February 21, 2005State Violation/Reminder Notice2 linked violations
- May 10, 2001State Public Notification requested2 linked violations
- May 10, 2001State Formal Notice of Violation issued1 linked violation
- September 22, 2000State Compliance achieved1 linked violation
- June 6, 2000Federal Final Administrative Order issued1 linked violation
- November 24, 1999State Public Notification requested1 linked violation
Common questions
Is PEYTON PINES required to publish a Consumer Confidence Report?
- Yes. PEYTON PINES is a community water system, and federal rules (40 CFR 141 Subpart O) require every community water system to publish a Consumer Confidence Report each year.
When is PEYTON PINES’s next Consumer Confidence Report due?
- PEYTON PINES’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does PEYTON PINES have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for PEYTON PINES.
What is a Consumer Confidence Report?
- A Consumer Confidence Report (CCR) is the annual drinking water quality report that community water systems must provide to the people they serve. It lists the contaminants detected in the system’s water during the year, where the water comes from, and how the results compare with federal limits. EPA’s revised CCR rule takes effect January 1, 2027, and the first reports in the new format are due July 1, 2027.
Contact
DEBAUN, DEBBIE
719-331-6597
PEYTON, CO 80831