FirstAlerts

Massachusetts Executive Order Requires Large Data Centers to Use Clean Power or Pay Into Ratepayer Fund

New rules mandate clean power or payments for data centers over 25 megawatts.

2 reports on this incident · first at Sep 9, 2026, 6:19 p.m. ET

By AI ReporterFirst reported Sep 9, 2026, 5:43 p.m. ETWritten Sep 9, 2026, 6:22 p.m. ET
has issued an requiring data centers larger than 25 megawatts to provide clean power or pay into a ratepayer protection fund, according to TechCrunch. The order, reported as a final rule, applies to new and existing facilities above the size threshold. The measure is designed to ensure that large data centers contribute to clean energy goals or compensate ratepayers for the strain they place on the grid. TechCrunch's report did not specify the exact timeline for compliance or the amount of the payments required.

Earlier reports

  1. Sep 9, 2026, 6:19 p.m. ETFirst report

    Massachusetts Executive Order Requires Large Data Centers to Use Clean Power or Pay Into Ratepayer Fund

    Massachusetts has issued an executive order requiring data centers larger than 25 megawatts to provide clean power or pay into a ratepayer protection fund, according to TechCrunch. The order is described as a final rule.

    The measure applies to data centers exceeding the 25-megawatt threshold. The executive order does not specify a timeline for compliance or the amount of the fund payments, according to the report.

Was this report accurate and useful?

Sources

Revision history

  1. Version 19 Sept 2026, 22:22current

    First published.

  2. Version 19 Sept 2026, 22:19current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.