Utah's data centers are building their own power plants, because the utility could not serve them.

Why Salt Lake City is a market at all

Salt Lake City sits in a genuinely useful place on the map. It is the natural western interior position: far enough from the coast to be a real disaster recovery pair for Silicon Valley or Los Angeles, close enough on fibre to serve both, and outside the seismic and wildfire exposure profile that makes California underwriters nervous. Power has historically been cheap, the climate allows a lot of free cooling, and land along the Wasatch Front is available in a way that coastal land is not.

What makes it unusual is how flat the interconnection map is. Most markets have one dominant carrier hotel that everything else orbits. This one does not: no single building holds even a quarter of the metro's network presences, and the top half dozen facilities are within striking distance of each other. That is a mixed blessing. It means real competition between operators, and it means no single building where everyone you need to reach already is.

The constraint here is not land, zoning or fibre. It is electricity, and it has been for several years.

Who is actually plugged in across Salt Lake City and the Wasatch Front

A building existing and a building being connected are different facts, and only one of them decides whether your traffic can get where it needs to go cheaply. These figures come from PeeringDB, which the network operators themselves maintain, so every row below links to the building's own public entry.

The most connected buildings here

From PeeringDB, which is maintained by the network operators present in these buildings rather than by the landlords, which is what makes it worth more than a directory. Two limits. Entries are voluntary, so a building showing no networks may be single tenant or may simply never have registered. And a network being present says nothing about whether the building has space, power or a price for you: that is still a call.

What has been announced in Salt Lake City and the Wasatch Front

Announcements are not filings. Nobody has to build what they announce, the figure is the one the developer chose to publish, and the date moves. They are here because megawatts are what a requirement is measured in, and because the size of what is coming changes who will take your call. Every figure below was read on the page it links to.

Announced capacity is collected by hand from trade reporting and company statements, and each figure links to the report it came from. It is kept apart from the permit record above and never added to it: one is a document a jurisdiction issued, the other is a plan a company published. Neither is availability.

Announced capacity is collected by hand from trade reporting and company statements, and every figure links to the report it came from and was read in that report before it was written down. It is never added to the interconnection count above: one is a plan a company published, the other is a building a network registered itself into. Neither is availability.

Power is the whole story, and the answer was to stop asking the utility

Rocky Mountain Power serves most of the Wasatch Front and has not been able to keep up with data center demand. Novva, which operates the largest campus in the state, was told the utility could not provide the full amount of energy it needed until 2031, and that even that was not guaranteed. Novva's response was to build its own generation: a natural gas plant intended to supply 200 megawatts, which would itself take until 2027, backed in the meantime by a fleet of diesel and gas fired generators.

Those generators run on a permit, not on demand. The Utah Division of Air Quality capped the emissions volume of the gas fired units and limited the diesel units to 42 hours a year. If you are evaluating a Utah building whose power story includes on-site generation, that permit condition is a hard operational ceiling and it belongs in your due diligence, not in a footnote.

Senate Bill 132 then rewrote the rules around all of this. It modifies Rocky Mountain Power's duty to serve, defines a large load as 100 megawatts or more within five years, and lets such customers negotiate separate large load contracts. The utility gets 90 days to evaluate a large load request and determine whether it can meet the demand without significant investment. If it cannot, the law allows the customer to go and source its own energy, either connected to the grid or entirely separate from it behind the meter. Utah's argument for this is that it protects existing ratepayers, and the state points to a projection that for every new gigawatt of data center load, rates could fall as much as 2 percent.

In February 2026 Governor Cox, legislative leadership and Rocky Mountain Power announced the first major agreement under that law, part of the state's Operation Gigawatt programme. The utility said it moved from introductory conversations to delivering a firm large load request in under a year, with the data center customer fully covering the costs of service. That is a fast timeline by national standards. It is also a bespoke, negotiated arrangement rather than a published queue you can join.

What this means if you are buying colocation rather than building

Almost none of the above applies to you directly, and all of it applies to your operator. A colocation tenant taking a cage or a few hundred kilowatts is nowhere near the 100 megawatt threshold and will never negotiate a large load contract. But the building you are moving into is downstream of one, and its power supply may be partly or wholly self-generated. That changes the questions worth asking: not just how much power is available, but where it comes from, what permit governs it, and what happens in the hours when the permitted generation is unavailable.

Where the market actually is, submarket by submarket

When this market is right, and when it is the wrong choice

Salt Lake City is the right answer for a western disaster recovery position, for enterprises headquartered along the Wasatch Front, and for workloads that want the interior west without Phoenix's heat or Denver's altitude. The flat interconnection map means you can negotiate: several operators can plausibly serve the same requirement, which is not true in most markets this size.

It is the wrong choice if you need a deep peering fabric. The whole metro carries fewer network presences than a single building in Seattle or Silicon Valley, and if your requirement is network-led rather than compute-led, this market will not satisfy it.

It is also the wrong choice if your power requirement is large and your date is fixed. The state's own legislation exists because the utility could not serve large loads on demand, and a bespoke negotiated contract is not a schedule you can hold anyone to. Two physical factors belong in the same conversation: the Wasatch Fault runs along the eastern edge of this valley, and the valley's winter inversions have periodically put it among the worst air quality in the country, which is precisely the context in which generator permits get tightened. Ask for the seismic design basis of the specific building and the current air permit conditions on any on-site generation, rather than the operator's regional narrative about either.