Skip to content

Several markets, one requirement, the same line items

Multi-City Colocation Quotes: Compare Prices Across Markets Without Running Separate Procurement Processes

Send one set of requirements and compare colocation in several cities on the same line items: rack, usable kW, A+B power, cross-connects, bandwidth, remote hands, setup fees and term. On our November 2026 price sheet a full 48U rack with 5 kW costs $1,500–1,800 a month across 26 US and Canadian markets, so the gap between cities is smaller than most buyers expect. Availability and the line items outside the rack decide more.

Updated November 2026 · Bob Spiegel, Founder, QuoteColo

Aerial view of a suburban data center campus: two windowless buildings, a substation and a row of generators beside a highway
Bob Spiegel

“Tell me what you’re deploying; I’ll come back with real options from a network built over 20 years.”

— Bob Spiegel, Founder, QuoteColo

From our desk, November 2026

$1,500–1,800
full 48U rack, 5 kW, across 26 markets on our sheet
$1,500–1,750
the same rack in 8 markets, including Dallas, Houston and Boston
$1,600–1,800
in 18 markets, including Ashburn, New York, Chicago and Los Angeles
0.2%
vacancy in Northern Virginia, the tightest major market (CBRE, H1 2026)

Prices from Bob’s City Price Sheet, November 2026, per cabinet per month. Vacancy from CBRE’s North America Data Center Trends H1 2026.

Why teams need multi-city colocation

Most multi-city deployments come from one of these needs, and each one points to a different kind of market pair.

NeedWhat it means for market choiceTypical answer
Primary site and disaster recoveryThe DR site has to be far enough away to avoid shared risks, and close enough for your replication to keep up.An East Coast primary with a Central or Southeast DR site
Users in several regionsSome applications can’t serve both coasts from one site within their latency budget.Two or three sites, with users routed to the nearest
Room to grow when one market is tightIn constrained markets, a second site can be the only way to add capacity this year.A second facility in a market with power available
Leaving the cloud in several regionsEach cloud region’s workloads move to a nearby colocation market.Markets near the cloud regions you use today
Canadian data residencyCanadian data stays in Canada; the rest can stay in the US.A US primary with Toronto

The multi-city quote problem: why you can’t compare what providers send you

The problem isn’t finding providers. It’s that their quotes don’t line up.

Each quote includes different things.

One includes bandwidth, A+B power and some remote-hands hours; the next lists power “at standard facility rates” and says nothing about cross-connects.

kW doesn’t always mean usable kW.

One provider quotes 10 kW usable; another quotes a 12.5 kW circuit at the same price. Only one of them is 10 kW you can actually draw.

Bandwidth is billed four different ways.

Unmetered, 95th percentile with a commit, a flat dedicated port and a monthly transfer cap can differ by hundreds of dollars a month for the same traffic.

Setup fees and terms show up late.

An install fee waived in one city and charged in another changes the 36-month total, and it often appears only in the contract.

Want these numbers for your own deployment? and we’ll reply with the providers that fit, with their prices.

Which US markets work well together for multi-city deployments

Two things decide a pair: the round trip between the sites, which limits how you replicate, and whether the second market has room. Bob’s price sheet also pairs every market with the Plan B markets he quotes next to it.

Pairings buyers ask about most

PrimarySecond siteRound tripWhy it works
AshburnDallas35–37 msEast and Central, on separate power grids and storm paths. Dallas lists a 5 kW rack at $1,500–1,750 on our sheet.
AshburnChicago19–22 msEast Coast and Midwest, both with deep carrier choice; close enough for low-lag asynchronous replication.
San Jose (Bay Area)Phoenix9–19 msA different seismic zone and grid, close enough for tight replication.
San Jose (Bay Area)Dallas31–44 msCoast and Central, with wide geographic separation.
New York or New JerseyAtlantaAbout 17 msEast Coast primary with a Southeast DR site.
ChicagoColumbusAbout 12 msA Midwest pair, near AWS us-east-2 and Google us-east5 in Ohio.
Ashburn or New YorkToronto16–18 msAdds Canadian data residency at short distance.

Round trips: Microsoft’s published Azure backbone medians (July 2026) and WonderNetwork pings (November 2026); where they differ, both ends are shown. Your carrier and route can change them.

Vacancy by market (CBRE, H1 2026)

  • New York Tri-State
    7.2%
  • Silicon Valley
    4.2%
  • Dallas–Fort Worth
    2.8%
  • Chicago
    2.2%
  • Atlanta
    1.6%
  • Phoenix
    1.1%
  • Northern Virginia
    0.2%

Share of built capacity that is vacant. Across CBRE’s eight primary markets it was 1.4% in the first half of 2026, a record low (North America Data Center Trends H1 2026, August 2026).

Multi-city pricing reference: a full rack across key markets

Bob’s City Price Sheet, November 2026: the monthly price per cabinet in each market, with 100 Mbps–1 Gbps. For single cabinets, the spread between cities is narrow: $1,500–1,750 in 8 markets and $1,600–1,800 in 18 markets for a 5 kW full rack.

MarketHalf rack 24U, 2 kWFull rack 48U, 5 kWFull rack, 15 kWFull rack, 30 kWPlan B markets
Ashburn$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999Atlanta, New Jersey, Dallas
Dallas$750–1,200$1,500–1,750$4,500–6,750$9,000–9,750Houston, Austin, Virginia
Chicago$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999Houston, Virginia, Dallas
Atlanta$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999Miami, Virginia, Dallas
Phoenix$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999Salt Lake City, San Jose (Bay Area), Dallas
San Jose (Bay Area)$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999Los Angeles, Sacramento, Dallas
New York$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999Boston, New Jersey, Dallas
New Jersey$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999New York, Virginia, Dallas
Los Angeles$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999Sacramento, San Jose (Bay Area), Dallas
Denver$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999Salt Lake City, Los Angeles, Dallas
Seattle$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999Los Angeles, Sacramento, Dallas
Toronto$1,000–1,500$1,600–1,800$4,800–5,400$9,500–9,999Boston, New Jersey, Dallas

Per cabinet per month. Cross-connects, extra bandwidth, remote hands and setup fees come on top, and they differ more between facilities than the rack does. That’s what we line up for you across cities.

From 100 kW: listed $/kW per month by state

  • Texas12 listings, largest 36 MW
    $165–250
  • Virginia3 listings, largest 72 MW
    $185–250
  • Georgia2 listings, largest 12 MW
    $165–205
  • Illinois2 listings, largest 800 kW
    $165–250
  • Pennsylvania6 listings, largest 100 MW (10 MW minimum)
    $200–275
  • Ohio1 listing, largest 500 kW
    $185–205
  • Utah2 listings, largest 800 kW
    $185–240
  • Washington5 listings, largest 1.6 MW
    $200–320
  • California7 listings, largest 6 MW
    $205–325
  • New York3 listings, largest 500 kW
    $200–380

Space and power per kW per month, from Bob’s HD Availability & Pricing list (November 4, 2026): listings, not confirmed offers, shown by state. Texas also has build-to-suit listings at $95–185.

What normalized multi-city quotes look like

We ask every provider in every city for the same line items, in the same format. You get one table with a column per city.

Line itemWhat each provider has to stateWhy it differs between cities
RackMonthly price for the cabinet or cage, and what’s includedSome markets bundle bandwidth or power; some don’t.
Usable kWkW you can draw continuously, after the 80% ruleBreaker size is often quoted instead.
A+B powerIncluded, extra per circuit, or not to the cabinetSee A+B power colocation.
Power billingFlat per circuit, per kW committed, or metered per kWhMetered power changes with your load and local rates.
Cross-connectsMonthly and install fee per carrier, cloud on-ramp and exchangeRate cards vary more between facilities than racks do.
BandwidthPort speed and billing model: unmetered, commit with burst, or cappedDefaults differ by provider and market.
Remote handsIncluded hours and the hourly rate after them, business hours and after-hoursOften left out of the first quote.
Setup and termInstall fee, term options and the price at each termA waived fee in one city can decide a 36-month total.

Where a provider bundles items differently, we adjust so each city shows a comparable all-in monthly figure.

Single provider across cities vs a different provider in each

Large operators run facilities in many markets and will sign one agreement for all of them. Picking the best facility in each city is the other way. Both have a place.

  1. One provider

    One contract for every city

    Upside

    One agreement, one account team, one invoice and the same SLA terms everywhere; possible volume pricing; cheaper links between their own sites.

    Usually wins when

    Under about 5 racks per city and no one dedicated to procurement.

  2. Best in each city

    A different provider per market

    Upside

    The best availability, price and carriers in each market; no single-provider risk at renewal; network diversity between sites.

    Usually wins when

    More than about 5 racks per city, or carrier needs that differ by market.

Latency math: what RTT between sites means for your architecture

The round-trip time between your sites decides which replication and failover designs you can run. Synchronous replication adds at least one round trip to every write, so it stays within a metro; between cities, the normal pattern is asynchronous.

Round trip between US regions (Microsoft Azure backbone, July 2026)

  • Virginia – Toronto
    18 ms
  • Virginia – Chicago
    19 ms
  • Chicago – Toronto
    19 ms
  • Arizona – California
    19 ms
  • Virginia – Texas
    35 ms
  • Texas – California
    35 ms
  • Chicago – Texas
    38 ms
  • Virginia – California
    67–69 ms

Medians between Azure regions over the 30 days to 30 July 2026, as published by Microsoft. Public internet paths between colocation facilities in the same metros can be a little faster or slower.

Round tripExample pairsReplication you can runFailover
Under 5 msTwo facilities in one metroSynchronous: Oracle flags impact above about 2 ms and treats under 5 ms as the limit; Microsoft Storage Replica asks for 5 ms or lessActive/active or zero-data-loss failover, but no geographic separation
15–25 msVirginia–Chicago, Virginia–Toronto, New York–AtlantaAsynchronous with small lag; synchronous slows high-write applicationsActive/passive with a short recovery point
30–40 msVirginia–Texas, Texas–CaliforniaAsynchronousActive/passive; the usual primary-and-DR pattern
60–70 msVirginia–CaliforniaAsynchronous; lag grows with write volumeWarm or cold DR
Over 80 msUS to Europe or AsiaAsynchronous or backup replicationCold DR; see international colocation

No US rule sets a minimum distance between primary and DR sites. HIPAA requires backup and disaster-recovery plans, and bank examiners and the SEC ask for geographic diversity: in practice, a second site outside the first one’s grid, flood zone and storm path.

Typical multi-city deployment profiles

Common shapes we see, and what drives each.

ProfileTypical marketsTypical scaleWhat decides it
SaaS, East and Central coverageAshburn and Dallas5–20 racks per siteCoverage of East and Central users; separate grids
Financial services, primary and DRNew York or New Jersey, with Chicago or Atlanta5–30 racks primary, a smaller DR siteExchange connectivity at the primary, separation at DR
Leaving the cloudMarkets next to the cloud regions you use: Ashburn (AWS us-east-1, Google us-east4), Ohio (AWS us-east-2, Google us-east5), Dallas (Google us-south1, Azure South Central US)10–50 racks per siteShort, cheap paths to the cloud you keep
Healthcare with a DR requirementAn East Coast primary and a DR site in another region3–10 racks, A+B powerHIPAA backup and DR plans; any US site meets the health-record location rules in Florida and Texas
National coverageAshburn, Dallas and Los Angeles or Silicon Valley3–15 racks per siteUsers on both coasts and in the middle
US primary with Canadian dataAshburn or New Jersey, with Toronto2–10 racks in TorontoCanadian data stays in Canada
GPU primary with a lighter DR siteGPU capacity where it’s listed, DR in a secondary market (see high-density colocation)1–10 GPU racks primaryWhere GPU power is available now

Single-provider footprints, from the operators’ own sites: Equinix and Digital Realty about 15 US metros each, DataBank 25+, Flexential 18, CoreSite 11, Cologix 9 US and 4 Canadian markets.

Why multi-city quotes take weeks when you collect them yourself

Finding providers in each city is the easy part. Making their quotes comparable is the work.

THE DIY WAY

You run a sales process per city

Each provider has its own intake, its own questions and its own quote format. Three cities means three of everything.

THE DIY WAY

You compare totals that aren’t the same thing

One quote includes bandwidth and A+B, another bills power by the kWh and leaves out cross-connects. The cheaper-looking one often isn’t.

THE DIY WAY

You find the setup fee at contract stage

Install fees, remote-hands rates and term discounts appear late, after you’ve already picked a favorite city.

How it works

You send the specs. We find the options. You decide.

STEP 1

Send your requirements.

Tell us what you're deploying, where you want it, and when you need it. Send the specs you have; we'll help with the rest.

HardwareRacks & kWLocationStart date

Estimates are fine. No perfect RFP needed.

STEP 3

Take the next step. On your terms.

Like the options? Contact the providers directly. Need more detail? Call or email us. We're here to help, not push you.

  • Go directly to the providers you like
  • Ask us questions whenever you need

Get 2–4 qualified options in 48 hours

Free for buyers

Your price is the same as going direct.

Comparable prices by email

Review the options before deciding on a call.

Trusted service since 2004

5,000+ clients helped.

By clicking here, I state that I have read and understood the Terms and Conditions

Case studies

See how we helped teams secure colocation with the right power, pricing, and providers.

Leonard Roszkowski

CEO Elemental Energy Solutions

Problem: Needed to source ASIC servers domestically. Skeptical about working with a new organization.

What we did: Connected them to buyers, sellers, and infrastructure partners across deployments. Removed procurement and logistics overhead entirely.

Result: Rapid organizational growth in a short period. Now uses QuoteColo as an ongoing procurement interface across hardware and infrastructure.

Noel Frutasio

CEO FSN Services and Communications

Problem: Regularly needed colocation space across multiple US states and time zones. Difficult to navigate the market without deep industry knowledge.

What we did: Defined requirements in one meeting, then delivered proposals with multiple carrier and data center options across every target market.

Result: Placed in 4 cities. Contracts signed quickly. Multi-state colocation needs resolved through a single point of contact.

Tim Mandell

DC Mining / MDI Access

Problem: Needed reliable options for crypto mining containers and equipment, along with industry partners who could support real deployment requirements.

What we did: Connected the project with relevant mining infrastructure and equipment resources through the QuoteColo network, simplifying the search and evaluation process.

Result: Gained a clearer path to suitable mining infrastructure, equipment and industry contacts without having to source every option independently.

5,000+

Clients helped since 2004

No Cost

to Buyers

500+

Worldwide providers

Quotes

in 48 h

Frequently asked questions: multi-city colocation quotes

Can I get quotes for multiple cities in a single request to QuoteColo?

Yes. Send your footprint (racks and kW per rack), your list of cities, or just the use case such as primary plus DR, and any constraints. We match each city at the same time and send the options on one template by email, within 48 hours once the requirements are clear for a standard two- or three-city request.

Is it better to use one provider across multiple cities or a different provider in each city?

One provider usually wins below about 5 racks per city, when one contract, one invoice and one account team save more than a lower price would. Above that, or when carrier needs differ by market, the best facility in each city is often a different operator. We can quote both ways so you compare the all-in cost.

Which two US markets are the most common pairing for primary + DR?

Ashburn and Dallas: East and Central, on separate power grids, about 35 ms apart, which suits asynchronous replication. On our November 2026 sheet a 5 kW full rack is $1,600–1,800 a month in Ashburn and $1,500–1,750 in Dallas. On the West Coast, Silicon Valley with Phoenix is the common equivalent, about 9–19 ms apart.

What RTT do I need between sites for synchronous database replication?

Usually under 5 ms, which means the same metro. Synchronous replication adds at least one round trip to every write: Oracle flags impact above about 2 ms and Microsoft’s Storage Replica asks for 5 ms or less. Between cities, 15–70 ms apart, the normal pattern is asynchronous replication to the DR site.

How do you normalize quotes from different providers so I can actually compare them?

We ask every provider for the same line items: rack price, usable kW after the 80% rule, A+B power, power billing, cross-connect fees per circuit, bandwidth model and port speed, remote-hands rates, setup fee and term options. Where a provider bundles items differently, we adjust so each city shows a comparable all-in monthly figure.

If I need quotes for four cities, does that take longer?

Sometimes. Two or three markets with a defined footprint move at the same pace as one. Four or more markets, compliance requirements or high-density GPU racks in several cities take longer, because confirming availability takes longer. We tell you what to expect when you send the request.

What information do you need to start a multi-city request?

Your list of cities or the use case, racks and kW per rack at each site, bandwidth, term, any compliance needs, and whether you’d consider one provider for every city. The more specific the requirement, the more useful the comparison.

Does QuoteColo charge for multi-city quotes?

No. You don’t pay us, however many cities you compare. Providers share their existing standard sales commission with QuoteColo, so there’s no added fee or markup on your provider quote.