ERCOT Interconnection Queue Near Data Centers: West Texas
Pecos city is in Reeves County, not Pecos County. A West Texas case shows how to read the ERCOT generation queue without confusing it with data-center load.
July 26, 20267 min read
Revised October 19, 2026. Original publication date retained.
The interconnection queue lists generators and batteries asking to connect to the grid. It does not list data centers, and a county total from it says nothing about computing load or available service.
A search for Microsoft’s announced Pecos data-center campus can lead straight to the wrong cluster. Pecos city is in Reeves County, and Pecos County is a separate geography. The June 2026 ERCOT queue snapshot carried 16,600.58 MW of active proposals in Pecos County and 6,635.56 MW in Reeves. Keep three things apart: the county that holds the place, the generation project asking to connect, and the computing campus with its own power arrangement.
01
Resolve the place before counting megawatts
The Census Bureau’s Texas place gazetteer identifies the Town of Pecos city as GEOID 4873493. The map uses its representative point and Census county boundaries for Reeves and Pecos counties. It is a geography check, not a parcel locator for a campus.
Microsoft’s June 22 campus announcement names Pecos and Reeves County. It describes roughly 2 GW of planned data-center capacity, dedicated on-site supply, behind-the-meter natural gas at launch and a broader grid connection later.
That is Microsoft’s announced plan. It does not turn every generation proposal in neighboring Pecos County into supply contracted to the campus, and county names, facility identity and electrical arrangement all have to match before records can be joined.
02
What the June 2026 ERCOT queue snapshot shows
The source is ERCOT document 1245185620, which covers generator-interconnection activity from June 1 through June 30, 2026. Ask the Grid’s snapshot timestamp is July 1 at 00:00 UTC; that is when the monthly report was captured, not when every project changed.

The table keeps only records with status Active and sums requested capacity once per queue record. Completed and inactive projects are excluded.
These are proposed generation and storage megawatts, not operating generation, expected construction, accredited capacity, utility headroom or data-center service requests.
| County | Active records | Requested generation/storage MW |
|---|---|---|
| Pecos | 37 | 16,600.58 |
| Milam | 20 | 7,069.27 |
| Reeves | 15 | 6,635.56 |
03
A queue project is not a campus
The Giant Arc-II is a 1,300 MW gas-generation queue record. Its point of interconnection and dates describe that supply proposal. A 1,300 MW computing campus would be a different load object, even if both share a round number.
Start from the queue identifier and read the fuel, requested capacity, study stage, proposed connection and publication history. Match a developer announcement to a record only when project identity or a primary document supports it.
A county-centroid symbol is not project geometry, and it cannot show a shared parcel, substation, transmission path or bilateral supply arrangement.
04
Company pages describe different power arrangements
Data-center pins that look alike can carry very different exposure to the public grid, and the statements below should not be added together as one class of new ERCOT demand.
Pacifico’s GW Ranch page describes an off-grid, private-power development. Project Horizon’s site describes a 559-acre Pecos County campus with on-property gas generation for daily operation and a public-grid connection for backup. Both are developer descriptions, not verified energization findings.
Riot’s Rockdale announcement is a different case, an existing site-level grid interconnection with a phased critical-IT lease. The Rockdale dossier follows its capacity and delivery claims through later filings.
| Public record | What to carry forward | Next evidence needed |
|---|---|---|
| Microsoft / Pecos | Reeves County; announced campus and initial on-site supply | Phase-specific service and delivery records |
| GW Ranch | Developer-described private/off-grid supply | Specific phase, counterparties and operating status |
| Project Horizon | Developer-described on-site supply, grid backup | Actual import terms and commissioned phase |
| Rockdale / AMD | Gross site power versus phased critical-IT capacity | Allocation and delivery evidence for the phase |
05
Bring in load and prices after the identities are settled
A weather-zone demand curve describes a regional operating regime, not one campus’s consumption. A hub price describes market exposure without proving a data center caused a spike or that its site is deliverable.
The September 17 congestion reconstruction shows how to work a price event through matched records and estimated constraint exposure. A campus’s load still needs its own load record, and the next useful request is specific: the exact computing phase, parcel and serving arrangement, then the load-service and generation records that connect them. A county total is where that work starts.
The queue analysis stays fixed to the June reporting period, and the company pages were read on October 19, 2026. Their completion dates are prospective and should be treated as claims.