The data center fight in Brownsville, Texas
As of September 27, 2026, Brownsville, Texas has a data center moratorium under consideration (action taken 2026-09-02).
Status is derived, not stored — a pause with a documented end date flips to Expired on its own — and the source is right next to the claim.
Status today
City commissioners voted to direct the city manager to initiate a 90-day moratorium on high-intensity data processing facilities. Under new Texas state law, the process requires three public hearings with 30 days between the first and second, so the moratorium has not yet taken effect.
SourceNews
read 2026-09-06
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
What to do next
- Questions to ask at the hearing — force specific answers onto the record.
- Estimate the impact — electricity, water, and rate pressure for any facility size in Texas.
- Model CBA clauses — copy-paste language communities have actually won.
- Texas briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Texas
- Harlingen (24 mi) — Enactedfixed term, end date not recorded
- Corpus Christi (131 mi) — Proposedterm not documented
- San Antonio (251 mi) — Rejectedterm not documented
- San Marcos (276 mi) — Enactedno end date — permanent
- Austin County (285 mi) — Enactedterm not documented
- Hays County (288 mi) — Enactedexpires 2026-12-31
- Texas (Abbott directive) (302 mi) — Enactedno fixed end — runs until a condition is met
- Austin (302 mi) — Proposedterm not documented
All 23 tracked actions in Texas are on the state page.
As of August 2026 · changes weekly — re-check before citing
Illustrative rather than exhaustive — dozens of localities churn weekly, and this tracks the ones we have read a source for. **Each row carries its own provenance.** Rows showing a verification date link to the ordinance, the enacting body's own page, or a datable report of the vote, and were read on that date. Rows marked *unverified* came from bulk compilation and have not been checked against a primary source — the locality, the year, and the status may all be off. Verify one of those with the town clerk before citing it as precedent. **Expiry is derived, not asserted.** A row with a documented end date flips to *Expired* on its own once that date passes. A time-limited moratorium whose start date was never documented keeps showing as enacted — that is a known gap, not a claim that it is still in force. Moratoriums are also routinely extended, so an expiry date is the earliest it could have ended, not proof that it did.
Part of the U.S. data center moratorium tracker — open data, CC BY 4.0.