TruthFoundry News
Better tools. Better news.
Tuesday, September 1, 2026 · UTC
246 of 2232 in this edition
tech

Unexpected outage at Costa Sur plant leaves 175,000 Puerto Rico customers without power

An unexpected failure at the Costa Sur power plant left approximately 175,000 customers without electricity in Puerto Rico.

TruthFoundry Desk
from the fact record
Share on X
Stands on 9 placed sources from 3 publishers.
Approximately 175,352 customers in Puerto Rico lost electricity during the late afternoon and evening of Sunday following an unexpected failure of units 5 and 6 at the Costa Sur power plant. [1] Genera PR reported on Tuesday that Unit 6 of the San Juan thermal power plant unexpectedly went offline, causing partial interruptions to electrical service in Puerto Rico. [2] The outage represented approximately 11.9% of the 1,468,223 clients registered in the system. [3] The region of Caguas recorded the highest number of affected customers with 53,875 out of a total of 250,514. [4] According to updated data from LUMA Energy as of 5:55 PM, 35,384 customers remained without electrical service, representing 2.41% of the total reported. [5] Genera PR stated that it does not yet have an estimated time for Unit 6 of the San Juan plant to return to service and will continue to provide updates as the situation develops. [6] Unit 6 of the Costa Sur plant, which went offline on Monday afternoon due to a disturbance in transmission infrastructure, is currently in the startup process. [7] Genera PR stated that it does not currently have an estimated time for when Unit 6 will return to operation and will offer updates as the process advances. [8] Carolina reported 27,298 customers without service out of a total of 141,663, while Mayagüez had 14,313 affected subscribers and Ponce had 10,792. [9]
What this stands on
  1. Approximately 175,352 customers in Puerto Rico lost electricity during the late afternoon and evening of Sunday following an unexpected failure of units 5 and 6 at the Costa Sur power plant. · Periódico La Perla
  2. Genera PR reported on Tuesday that Unit 6 of the San Juan thermal power plant unexpectedly went offline, causing partial interruptions to electrical service in Puerto Rico. · NotiCel - La verdad como es - Noticias de Puerto Rico - NOTICEL -
  3. The outage represented approximately 11.9% of the 1,468,223 clients registered in the system. · Periódico La Perla
  4. The region of Caguas recorded the highest number of affected customers with 53,875 out of a total of 250,514. · Periódico La Perla
  5. According to updated data from LUMA Energy as of 5:55 PM, 35,384 customers remained without electrical service, representing 2.41% of the total reported. · NotiCel - La verdad como es - Noticias de Puerto Rico - NOTICEL -
  6. Genera PR stated that it does not yet have an estimated time for Unit 6 of the San Juan plant to return to service and will continue to provide updates as the situation develops. · NotiCel - La verdad como es - Noticias de Puerto Rico - NOTICEL -
  7. Unit 6 of the Costa Sur plant, which went offline on Monday afternoon due to a disturbance in transmission infrastructure, is currently in the startup process. · NotiCel - La verdad como es - Noticias de Puerto Rico - NOTICEL -
  8. Genera PR stated that it does not currently have an estimated time for when Unit 6 will return to operation and will offer updates as the process advances. · Metro Puerto RicoPuerto Rico
  9. Carolina reported 27,298 customers without service out of a total of 141,663, while Mayagüez had 14,313 affected subscribers and Ponce had 10,792. · Periódico La Perla
The one we could place publishes from Puerto Rico. 2 could not be placed by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · 9 sources · v 001worldrecordwritingfiling

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Tuesday, September 1, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world3 publishers reported the events
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
The one we could place publishes from Puerto Rico. 2 could not be placed by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
The automated line wrote this as TruthFoundry News Desk using a large language model at 2026-09-02T22:21Z.
The prompts, verbatim
System instruction (the grounding rules)


The assignment: persona voice contract + this desk's standing instructions + the numbered facts



4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.


Integrity


Content hash (SHA-256)6672b0118e1173faf9965a4aef350eba6e5ccad423349557875507fb18302418


Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed


Receiptthis revision predates receipt-keeping; the filed row lives on the record


Machine readablethe full proof, JSON


Verify



A signature proves who filed this and that it has not changed since. It never makes a claim true.


Up next in this editionOpenClaw 2.0 Launches with Enterprise Security and Multiplayer Cloud Sessions