US-DC · United States

District of Columbia data centers and internet exchanges

PeeringDB's 2026-09-07 snapshot records 4 colocation facilities in District of Columbia (US-DC) holding 23 network presences, concentrated in Washington, and 1 internet exchange, the largest being Global Peer Exchange.

Facilities
4
Exchanges
1
Snapshot
2026-09-07
Country
United States (US)
Subdivision code
US-DC
Colocation facilities
4
Network presences
23
Internet exchanges
1 (7 participants)
Largest exchange
Global Peer Exchange, Washington
Main facility city
Washington
Cities with facilities
1
Snapshot
2026-09-07

The 2026-09-07 PeeringDB snapshot records 1 exchanges and 4 facilities in District of Columbia, United States. Their entries sum to 7 exchange participants and 23 facility network presences; the same network can appear more than once.

Internet exchanges in District of Columbia

Exchanges are attributed to the state through the city they sit in, because PeeringDB records a state for facilities but not for exchanges.
Internet exchanges in District of Columbia
ExchangeCityParticipants
Global Peer ExchangeWashington7

Colocation facilities in District of Columbia

Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there.
Colocation facilities in District of Columbia
FacilityCityNetworks present
CoreSite - Washington,DC (DC1)Washington16
CoreSite - Washington,DC (DC2)Washington4
Zayo Washington DC - 2100 M Street NWWashington2
AiNET DC-900SWashington1

What these records establish

This page groups the saved exchange and facility records for District of Columbia. 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

These selected carrier records provide ASN references for further checks. They do not establish a subscriber’s location or regional coverage.

Questions

How many exchanges and facilities are recorded in District of Columbia?
1 exchanges and 4 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 District of Columbia 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.

  1. [1]https://www.peeringdb.com/
  2. [2]https://support.maxmind.com/knowledge-base/articles/maxmind-geolocation-accuracy
  3. [3]https://www.proxies.sx/carriers

These records describe where networks house equipment and interconnect. An IP address that geolocates to District of Columbia does not show that a device is there: mobile carriers route wide areas through shared gateways, and geolocation databases estimate from registration data.