US-UT · United States
Utah data centers and internet exchanges
PeeringDB's 2026-09-07 snapshot records 25 colocation facilities in Utah (US-UT) holding 212 network presences, concentrated in Salt Lake City, and 3 internet exchanges, the largest being SLIX - Salt Lake City Internet Exchange.
- Facilities
- 25
- Exchanges
- 3
- Snapshot
- 2026-09-07
- Country
- United States (US)
- Subdivision code
- US-UT
- Colocation facilities
- 25
- Network presences
- 212
- Internet exchanges
- 3 (66 participants)
- Largest exchange
- SLIX - Salt Lake City Internet Exchange, Salt Lake City
- Main facility city
- Salt Lake City
- Cities with facilities
- 10
- Snapshot
- 2026-09-07
The 2026-09-07 PeeringDB snapshot records 3 exchanges and 25 facilities in Utah, United States. Their entries sum to 66 exchange participants and 212 facility network presences; the same network can appear more than once.
Internet exchanges in Utah
| Exchange | City | Participants |
|---|---|---|
| SLIX - Salt Lake City Internet Exchange | Salt Lake City | 37 |
| SUPRnet | Saint George | 18 |
| Mountain West Internet Exchange | Salt Lake City | 11 |
Colocation facilities in Utah
| Facility | City | Networks present |
|---|---|---|
| DataBank Salt Lake City (SLC1) | Salt Lake City | 47 |
| Flexential - Salt Lake City/Downtown (SLC04) | Salt Lake City | 25 |
| DataBank Salt Lake City (SLC2) | Bluffdale | 25 |
| FIBERSTATE Salt Lake City (SLC1) | Draper | 24 |
| EdgeConneX Salt Lake City (EDCSLC01) | Salt Lake City | 18 |
| DataBank Salt Lake City (SLC3) | Bluffdale | 15 |
| Level(3) Salt Lake City | Salt Lake City | 10 |
| Tonaquint Data Center - Saint George | Saint George | 9 |
| Aligned Salt Lake (SLC-01) | South West Jordan | 6 |
| XMission - Salt Lake City - Utah | Salt Lake City | 5 |
| Flexential - Salt Lake City/Lindon (SLC03) | Lindon | 4 |
| Voonami SLC2 | West Valley City | 4 |
| UFN Kearns | Salt Lake City | 3 |
| Flexential - Salt Lake City/Fairpark (SLC07) | Salt Lake City | 3 |
| Flexential - Salt Lake City/South Valley (SLC09) | West Jordan | 3 |
Showing the 15 facilities with the most networks, of 25 recorded.
What these records establish
This page groups the saved exchange and facility records for Utah. A sum of participant or facility counts is not a count of unique networks, traffic volume, available capacity or service coverage.
PeeringDB is user-maintained. Its records describe reported interconnection infrastructure; they do not trace a particular request or locate a subscriber. A missing record in this snapshot is not proof that an operator has no presence or private connection in the area.
An IP geolocation result is a separate estimate. MaxMind documents accuracy limits and explains that its location data cannot identify a specific household, person or street address. This registry does not perform a geolocation lookup or measure where an individual device is located.
Mobile carriers in the United States
Questions
- How many exchanges and facilities are recorded in Utah?
- 3 exchanges and 25 facilities appear in the 2026-09-07 snapshot. The tables show the saved records and link to the publisher for current details.
- Are the totals unique networks?
- No. Participant entries are summed across exchanges and network presences across facilities. A network listed at several locations contributes to several entries.
- Does a Utah IP label prove that a device is there?
- No. These infrastructure records do not establish a device location. Consult the geolocation provider’s accuracy information and the specific network record for the claim you are evaluating.
Sources
PeeringDB supplies the facilities, network presence and exchange participants (snapshot 2026-09-07); MaxMind documents the limits of IP geolocation; the PROXIES.SX carrier registry lists the operators routing mobile addresses in this country.
These records describe where networks house equipment and interconnect. An IP address that geolocates to Utah does not show that a device is there: mobile carriers route wide areas through shared gateways, and geolocation databases estimate from registration data.