Utah ZIP code · Backend-populated CMS water report

84017

ZIP 84017 Utah drinking-water data from the Rails backend: 8 plausible public water providers, reported status, annual reports, freshness, sources, and geographic limitations.

Page source
answer.cloud CMS
Backend snapshot
Confirm provider
Check your water bill

Plain-language summary

What this page means

ZIP 84017 Utah drinking-water data from the Rails backend: 8 plausible public water providers, reported status, annual reports, freshness, sources, and geographic limitations.

This is area-level public water information. Confirm your provider on your water bill, and contact that provider for current notices about your service.

ZIP overview Backend value
ZIP code 84017
County or counties Summit
Plausible public water providers 8
Postal-only area No
Current data date June 30, 2026
Page facts updated August 19, 2026

Confirm your provider: 8 public water systems intersect this area; use an address to narrow the result. Check the provider name and PWSID on your water bill before relying on a system-level result.

Which public water systems may serve ZIP 84017?

The Rails backend identifies the following systems as plausible providers for this ZIP area. A reported system status does not certify water at an individual tap.

Provider 01: COALVILLE CITY WATER SYSTEM

Provider fact Backend value
Public Water System ID UTAH22002
Reported status No reported open violations
Status current through June 30, 2026
Open health-based violations 0
Open monitoring/reporting violations 0
Backend relationship intersects_published_boundary
Boundary coverage 1% of the mapped ZIP area
Match confidence medium

Provider details · Reported-status source

The backend returned no active advisories for this provider. Check the utility directly for the newest local notice.

Provider 02: PINE MEADOW MUTUAL WATER

Provider fact Backend value
Public Water System ID UTAH22079
Reported status No reported open violations
Status current through June 30, 2026
Open health-based violations 0
Open monitoring/reporting violations 0
Backend relationship intersects_published_boundary
Boundary coverage 1% of the mapped ZIP area
Match confidence medium

Provider details · Reported-status source

The backend returned no active advisories for this provider. Check the utility directly for the newest local notice.

Provider 03: BRIDGE HOLLOW WATER ASSOCIATION

Provider fact Backend value
Public Water System ID UTAH22117
Reported status No reported open violations
Status current through June 30, 2026
Open health-based violations 0
Open monitoring/reporting violations 0
Backend relationship intersects_published_boundary
Boundary coverage 1% of the mapped ZIP area
Match confidence medium

Provider details · Reported-status source

The backend returned no active advisories for this provider. Check the utility directly for the newest local notice.

Provider 04: MOUNTAIN REGIONAL WATER SSD

Provider fact Backend value
Public Water System ID UTAH22137
Reported status No reported open violations
Status current through June 30, 2026
Open health-based violations 0
Open monitoring/reporting violations 0
Backend relationship intersects_published_boundary
Boundary coverage 0% of the mapped ZIP area
Match confidence medium

Provider details · Reported-status source

The backend returned no active advisories for this provider. Check the utility directly for the newest local notice.

Provider 05: CLUFF WARD PIPELINE CO

Provider fact Backend value
Public Water System ID UTAH22001
Reported status No reported open violations
Status current through June 30, 2026
Open health-based violations 0
Open monitoring/reporting violations 0
Backend relationship intersects_published_boundary
Boundary coverage 0% of the mapped ZIP area
Match confidence medium

Provider details · Reported-status source

The backend returned no active advisories for this provider. Check the utility directly for the newest local notice.

Provider 06: HOYTSVILLE PIPE WATER CO

Provider fact Backend value
Public Water System ID UTAH22006
Reported status Reported open monitoring or reporting violations
Status current through June 30, 2026
Open health-based violations 0
Open monitoring/reporting violations 1
Backend relationship intersects_published_boundary
Boundary coverage 0% of the mapped ZIP area
Match confidence medium

Provider details · Reported-status source

The backend returned no active advisories for this provider. Check the utility directly for the newest local notice.

Provider 07: WANSHIP MUTUAL WATER CO

Provider fact Backend value
Public Water System ID UTAH22017
Reported status Reported open monitoring or reporting violations
Status current through June 30, 2026
Open health-based violations 0
Open monitoring/reporting violations 1
Backend relationship intersects_published_boundary
Boundary coverage 0% of the mapped ZIP area
Match confidence medium

Provider details · Reported-status source

The backend returned no active advisories for this provider. Check the utility directly for the newest local notice.

Provider 08: WANSHIP WATER CO. LLC

Provider fact Backend value
Public Water System ID UTAH22019
Reported status Reported open monitoring or reporting violations
Status current through June 30, 2026
Open health-based violations 0
Open monitoring/reporting violations 2
Backend relationship intersects_published_boundary
Boundary coverage 0% of the mapped ZIP area
Match confidence medium

Provider details · Reported-status source

The backend returned no active advisories for this provider. Check the utility directly for the newest local notice.

What are the limits of a ZIP-level match?

“No reported open violations” means only that none were reported in the latest imported dataset. It does not mean “safe,” “clean,” or “pass.” Regulatory data can lag local notices.

Where did these facts come from?

Questions residents ask

How do I find the provider for my home?

Use the private address lookup, then confirm the result against the provider and PWSID printed on your water bill.

Are these ZIP results live?

No. Annual reports and regulatory systems update on reporting cycles. Contact the utility for current notices or an abrupt local change.

Backend inventory record: 591 · backend canonical path: /zip-codes/84017/.