Massachusetts / Reports /

Combined sewer overflow (CSO) reported — CITY OF HOLYOKE, Jul 1, 2026

Ended (as reported) · CITY OF HOLYOKE (MassDEP sewage notification portal)

Source: CITY OF HOLYOKE (MassDEP sewage notification portal) via MassDEP CSO API behind the portal, record b417da00-af39-4db8-9c67-2a2f213e1248, published Jul 2, 2026, 10:07 AM EDT, retrieved 2026-11-02 10:58 UTC · Read the original notice

Read the original notice · Report an error

1. Reported wastewater outlet

Operator named in the record: CITY OF HOLYOKE (federal wastewater discharge permit, NPDES, MA0101630). Outlet: HOL02 “PROVIDENCE HOSPITAL”. Location: 42.16752, -72.63017; location source: from the state's or EPA's outfall layer.

Outfall: a pipe or outlet where wastewater enters a water body.

2. Waters named in the notice

The notice names: “CONNECTICUT R.”. DirtyWaterWatch links this report to Connecticut River, MA. Match basis: the water named in the report.

3. Estimated downstream stretch

No downstream estimate is available for this report.

Open on the main map

When it happened and when it was reported

Event and notice times use Eastern Time (EST or EDT). Retrieval times use Coordinated Universal Time (UTC).

Started

Jul 1, 2026, 1:40 AM EDT

Ended

not reported

Detail provided by the source

Times known to the minute

Reported to the source

not given

Published

Jul 2, 2026, 10:07 AM EDT

Source last updated

not given

Last retrieved by DirtyWaterWatch

2026-11-02 10:58 UTC

What and how much

Type

Combined sewer overflow (CSO): sewage mixed with rainwater spills from a shared sewer system.

Status in the record

Ended (as reported)

Material

“CSO – UnTreated”

Volume

volume not reported (not stated whether estimated or measured)

Volume as reported

none

Advice from CITY OF HOLYOKE (MassDEP sewage notification portal)

“Avoid contact with these water bodies for 48 hours after the discharge or overflow ceases due to increased health risks from bacteria and other pollutants. See website for more information on whether specific resource areas, such as bathing beaches, are affected.”

Advice period

48 hours

Basis

314 CMR 16.04(10)(g)

Status history from this report

• No current status shown Connecticut River: End not confirmed, Aug 1, 2026, 10:07 AM EDT to Sep 30, 2026, 10:07 AM EDT
• No current status shown Connecticut River: End not confirmed, Aug 1, 2026, 10:07 AM EDT to Sep 30, 2026, 10:07 AM EDT

Source: DirtyWaterWatch calculations using this report and the published status rules. Updated 2026-11-02 16:21 UTC.

Source and versions

Source

MassDEP CSO API behind the portal

Source record number

b417da00-af39-4db8-9c67-2a2f213e1248

Original notice

Read the original notice

Earlier version

None: this is the first record

Later versions

None

{
  "incidentId": "b417da00-af39-4db8-9c67-2a2f213e1248",
  "incidentNumber": "26016481",
  "incidentDate": "2026-07-01T00:00:00",
  "incidentTime": "01:40",
  "amPm": null,
  "reporterClass": "Public Notification Report",
  "eventType": "CSO – UnTreated",
  "permiteeClass": "CSO",
  "permiteeName": "CITY OF HOLYOKE",
  "permiteeId": "MA0101630",
  "outfallId": "HOL02",
  "municipality": "HOLYOKE",
  "reportingType": "Initial-Ceased",
  "location": "PROVIDENCE HOSPITAL",
  "latitude": null,
  "longitude": null,
  "waterBody": "CONNECTICUT R.",
  "waterBodyDescription": null,
  "volumnOfEvent": "",
  "rainfallData": "",
  "hours": "",
  "minutes": "",
  "month": null,
  "year": null,
  "additionalInformation": null,
  "submittedDate": "2026-07-02T10:07:34.453",
  "parentIncidentId": null,
  "_report_class": "Public Notification Report",
  "_tz_assumed": "America/New_York (portal gives local clock time without zone)",
  "_ended_note": "reported ceased; the portal gives no cessation time",
  "_coords": "MassDEP CSOs layer DEP_OUTFL_ HOL02 (locations are estimates)",
  "_water": {
    "via": "crosswalk on portal waterbody",
    "text": "CONNECTICUT R.",
    "confidence": "high"
  },
  "_advice_source": "required wording of 314 CMR 16.04(10)(g); the permittee's own advisory is only in an attachment the portal will not serve"
}