Edenton, Town of
PWSID: NC0421010
System Details
| Population Served | 5,500 |
| Service Connections | 2,400 |
| Water Source | Groundwater |
| System Type | Community Water System |
| Owner | Local Government |
| Status | Active |
| City | Edenton |
| Zip Code | 27932 |
Lead & Copper Testing
| Contaminant | Level | EPA Action Level | Status |
|---|
| Lead (90th percentile) | 0.0050 mg/L | 0.015 mg/L | Below Action Level |
| Lead (90th percentile) | 0.0000 mg/L | 0.015 mg/L | Below Action Level |
| Lead (90th percentile) | 0.0000 mg/L | 0.015 mg/L | Below Action Level |
| Lead (90th percentile) | 0.0000 mg/L | 0.015 mg/L | Below Action Level |
| Lead (90th percentile) | 0.0000 mg/L | 0.015 mg/L | Below Action Level |
1 Active Violations
| Contaminant | Violation | Date | Health-Based | Status |
|---|
| | 2016-08-29 | | Open |
Violation History (53 total)
| Contaminant | Violation | Date | Health-Based | Status |
|---|
| | 2024-10-17 | Yes | Returned to Compliance |
| | 2024-10-17 | | Returned to Compliance |
| | 2020-09-18 | | Returned to Compliance |
| | 2020-07-01 | Yes | Returned to Compliance |
| | 2020-04-01 | Yes | Returned to Compliance |
| | 2020-01-01 | Yes | Returned to Compliance |
| | 2019-10-01 | Yes | Returned to Compliance |
| | 2019-07-01 | Yes | Returned to Compliance |
| | 2019-07-01 | | Returned to Compliance |
| | 2019-04-01 | Yes | Returned to Compliance |
| | 2019-03-18 | | Returned to Compliance |
| | 2019-01-01 | Yes | Returned to Compliance |
| | 2018-12-15 | | Returned to Compliance |
| | 2018-10-01 | Yes | Returned to Compliance |
| | 2018-07-01 | Yes | Returned to Compliance |
| | 2018-06-17 | | Returned to Compliance |
| | 2018-04-01 | Yes | Returned to Compliance |
| | 2018-01-01 | Yes | Returned to Compliance |
| | 2017-11-26 | | Returned to Compliance |
| | 2017-10-01 | Yes | Returned to Compliance |
| | 2017-07-01 | Yes | Returned to Compliance |
| | 2017-05-21 | | Returned to Compliance |
| | 2017-04-01 | Yes | Returned to Compliance |
| | 2017-01-01 | Yes | Returned to Compliance |
| | 2016-10-01 | Yes | Returned to Compliance |
| | 2016-10-01 | | Returned to Compliance |
| | 2016-07-01 | Yes | Returned to Compliance |
| | 2016-05-23 | | Returned to Compliance |
| | 2016-04-01 | Yes | Returned to Compliance |
| | 2016-01-01 | Yes | Returned to Compliance |
| | 2015-12-04 | | Returned to Compliance |
| | 2015-10-01 | Yes | Returned to Compliance |
| | 2015-07-01 | Yes | Returned to Compliance |
| | 2015-06-06 | | Returned to Compliance |
| | 2015-04-01 | Yes | Returned to Compliance |
| | 2015-04-01 | | Returned to Compliance |
| | 2015-01-01 | Yes | Returned to Compliance |
| | 2014-10-01 | Yes | Returned to Compliance |
| | 2008-04-02 | | Returned to Compliance |
| | 2008-03-21 | | Returned to Compliance |
| | 2008-03-21 | | Returned to Compliance |
| | 2007-08-20 | | Returned to Compliance |
| | 2007-02-11 | | Returned to Compliance |
| | 2006-10-23 | | Returned to Compliance |
| | 2006-08-11 | | Returned to Compliance |
| | 2005-07-01 | | Returned to Compliance |
| | 2004-07-01 | | Returned to Compliance |
| | 2003-10-01 | | Returned to Compliance |
| | 2003-07-01 | | Returned to Compliance |
| | 2002-07-01 | | Returned to Compliance |
Showing 50 of 52 historical violations.