What the public evidence can tell you
The public evidence describes two different searches. Baltimore and the BWI corridor have buildings with network listings. Air records at Annapolis Junction, Jessup and Severn name Microsoft and Amazon sites, but do not establish space for another tenant. Begin with the address that fits the requirement, then confirm power and space directly.
Choose the corridor before the operator
Baltimore and BWI
PeeringDB lists network presences at Baltimore facilities and at TierPoint Baltimore BWI in Linthicum Heights. Network listings can share an address or campus, so these are registry entries rather than a deduplicated property survey.
Anne Arundel County
The linked air records name Microsoft on Dorsey Run Road, Amazon LTW060 at Jessup and Amazon LTW062 at Severn. These campuses are distinct from the operator buildings in the interconnection table. The permit record does not show what another customer could lease.
Beltsville and Laurel
AiNET listings extend the network evidence south of Baltimore. Test the actual address against your office, carrier routes and support needs. A Baltimore-wide total cannot establish latency or diverse fiber paths for this corridor.
Separate Maryland searches
Frederick County and Montgomery County are tracked separately. Washington, DC listings remain on the Northern Virginia guide so they are not counted twice.
Air-register evidence, not a construction schedule
These air-register entries have no filing dates in the collected records. The IBM Annapolis entry is marked Permanently Closed. That status stays visible below; its inclusion in the register total is not evidence of operating inventory or current construction.
Air-register records in the Baltimore-Washington corridor, including Microsoft and Amazon sites in Anne Arundel County and a permanently closed entry at Annapolis. Every figure below is a count of filings we collected ourselves, and every row links to the record it came from.
| Measure | Figure | What it means |
|---|---|---|
| Filings we track | 5 | Deduplicated. One source, no dated record to no dated record |
| Distinct addresses | 5 | Separate sites in the record, not separate buildings |
| Operators we can name | 2 | 3 of 5 filings name a recognizable operator. The rest name an engineer, a builder or a holding company |
| Filings with no date published | 5 | The source publishes the facility, not the filing date |
Operators appearing by name: Amazon Web Services (2), Microsoft (1).
Collected from EPA ECHO air facility records for Maryland. A permit or air-register entry documents a site or proposed work. It does not establish current construction or available space, and no public filing anywhere discloses what is contractible at a named building. That answer comes from an operator call, which is the part we do by hand. See how we verify capacity.
Check the underlying records
These public entries were checked against our collected data on 24 September 2026. Each link opens its EPA record. A register status does not establish a current commercial offering.
| Registered applicant and record | Address | Register status |
|---|---|---|
| AMAZON DATA SERVICES INC LTW060 | 7885 SELLNER ROAD, JESSUP 20794 | Operating |
| AMAZON DATA SERVICES INC LTW062 | SANDY FARM ROAD, SEVERN 21144 | Operating |
| CONTROL DATA CORP. | 1726 WHITEHEAD ROAD, WOODLAWN 21207 | Operating |
| IBM ANNAPOLIS DATA CENTER | 2500 RIVA RD, ANNAPOLIS 21401 | Permanently Closed |
| MICROSOFT CORPORATION - YELLOW FACILITY | 8201,8211,8221, & 8321 DORSEY RUN ROAD, ANNAPOLIS JUNCTION 20701 | Operating |
Where network operators list a presence
The following counts are PeeringDB listings. A network listed in more than one building contributes a presence at each; these are not unique regional carrier counts. Multiple registry entries can also refer to the same property. Confirm the required carriers and routes at the exact address.
Who is actually plugged in across Baltimore and the Maryland corridor
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.
| Measure | Figure | What it means |
|---|---|---|
| Buildings listed | 13 | Registered in PeeringDB across Baltimore and the Maryland corridor, by 9 operators |
| Buildings with a network present | 11 | 2 carry no network presence, which usually means single tenant or simply unregistered |
| Network presences | 42 | Counted per building, so a carrier in three buildings counts three times |
| Internet exchange presences | 5 | Where you can reach many networks through one port instead of many cross-connects |
| Carrier presences | 6 | The physical transport choice you can buy without leaving the building |
| In the densest building | 19% | Crown Castle Baltimore (111 Market, 700 E Pratt) holds 8 of the market's network presences |
The most connected buildings here
| Networks | Building | Operator | Exchanges | Carriers |
|---|---|---|---|---|
| 8 | Crown Castle Baltimore (111 Market, 700 E Pratt) | Crown Castle Inc. | 1 | 0 |
| 8 | Zayo Baltimore - 111 Market Pl | Zayo Group | 1 | 1 |
| 7 | TierPoint Baltimore | TierPoint, LLC | 0 | 1 |
| 5 | AINET - Beltsville | AiNET Corporation | 0 | 1 |
| 3 | AiNET WDC11 | AiNET | 0 | 0 |
| 3 | AiNET MD-300L | AiNET | 1 | 0 |
| 2 | AiNET WDC8 | AiNET | 0 | 0 |
| 2 | Lumen Baltimore | Lumen Technologies Inc | 1 | 1 |
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.
Facility inventory coverage
Our committed verified-inventory snapshot has no separate coverage for this region. We therefore publish no inventory count or available-space estimate here. Public air and network records remain separate evidence, with their own limits. See what verified building means.
What has been announced in Baltimore and the Maryland corridor
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 links to a published report that states it, and was checked against at least one other independent report before it was written down.
| Capacity | Operator | Project | What was announced |
|---|---|---|---|
| 150 MW | Security Land and Development LP | Proposed campus at 1500 Woodlawn Drive | WMAR and Data Center Dynamics describe a proposal for the Woodlawn site. Early coverage suggested construction could begin in June or July 2026. This review has not verified that it began, an approved delivery schedule, a utility service commitment or space available to lease. Treat the old start target as unconfirmed. Reported proposed campus capacity; the reports do not establish critical IT load or energized power |
The Woodlawn proposal is separate from the five air-register entries below. Its reported campus figure is not a verified IT-load figure or current supply. No IT-load total is inferred from the backup generators at the Microsoft and Amazon sites. A buyer needs current project approvals and operator confirmation before relying on a delivery date. Read the reporting.
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.
The proposed scale is reported independently by WMAR and Data Center Dynamics. Both describe a proposal, not delivered capacity.
How to compare an actual requirement
For a requirement tied to Baltimore staff or networks, start with the specific buildings above. Compare larger requirements with Northern Virginia and Frederick County using the same usable power, density and delivery milestones. Do not assume that a nearby hyperscale site is an alternative supplier.
Request the sellable IT load, rack density, cooling method, carrier access and ready-for-service date in writing. Distinguish power already delivered from power that depends on utility work. Record whether a quote reserves space and how long that reservation lasts.