District of Columbia · network infrastructure
PeeringDB records four facilities in the District of Columbia, all in Washington, holding 23 network presences. CoreSite - Washington,DC (DC1) accounts for 16 of them, with CoreSite DC2 on four, Zayo at 2100 M Street NW on two and AiNET DC-900S on one. The district has one exchange, Global Peer Exchange, with seven participants.
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.
| Exchange | City | Participants |
|---|---|---|
| Global Peer Exchange | Washington | 7 |
Colocation facilities
Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there.
| Facility | City | Networks present |
|---|---|---|
| CoreSite - Washington,DC (DC1) | Washington | 16 |
| CoreSite - Washington,DC (DC2) | Washington | 4 |
| Zayo Washington DC - 2100 M Street NW | Washington | 2 |
| AiNET DC-900S | Washington | 1 |
What a District of Columbia IP address tells you
All four recorded facilities in the District of Columbia are in Washington itself, which makes the city and the state-level entry the same footprint. CoreSite - Washington,DC (DC1) carries 16 of the 23 network presences, and the second CoreSite building, DC2, carries four. Zayo's 2100 M Street NW site lists two and AiNET DC-900S one. Global Peer Exchange, with seven participants, is where networks in the district can meet without leaving it, though most networks in these buildings are counted at facilities rather than on that exchange.
A District of Columbia IP address tells you what the operator registered, not where the person using it stands. Geolocation databases read the address block's published record, and an operator with a Washington registration can serve customers well outside the district. AT&T, T-Mobile and Verizon run mobile traffic through regional gateways on five, five and seven ASNs respectively, so a phone in Washington often resolves to a neighboring state, and a phone in that state can resolve to Washington.
Check the origin ASN and the netname on the prefix before trusting a district label. A block announced from one of the carrier mobile ASNs behaves differently from one registered to a tenant in a CoreSite building, even when both report Washington. The registration record names the holder, while a geolocation lookup only estimates a position for it. The two disagree often enough that the netname on the exact prefix is the better answer.
Mobile carriers in the United States
A mobile address anywhere in District of Columbia is routed by one of the country's operators. Each entry lists the operator's ASNs so you can check which network an address belongs to.
Questions
How many data centers are in Washington, DC?
The snapshot records four facilities, all inside Washington, holding 23 network presences. CoreSite - Washington,DC (DC1) has 16 of those. The second CoreSite building has four, Zayo's 2100 M Street NW site two and AiNET DC-900S one.
Is there an internet exchange in the District of Columbia?
Yes. Global Peer Exchange operates in Washington with seven participants in the snapshot. Networks in the district that want more peers than that reach exchanges in nearby states, since the district's own facility count is four buildings in a single city.
Can I get an IP address in the District of Columbia?
Placement follows the operator's address registration rather than a customer's choice. A block reports Washington when the network that holds it registered a Washington address. Mobile blocks follow carrier gateways, and AT&T, T-Mobile and Verizon each aggregate subscribers behind gateways that reach past the district's borders.
Sources
- PeeringDB - facilities, network presence and exchange participants, snapshot 2026-09-07
- PROXIES.SX carrier and ASN registry - the operators routing mobile addresses in this country