Skip to content

Your ASN, your prefixes, two or more carriers

BGP Colocation: Bring Your Own ASN, Your Own IP Space and Full Routing Control

BGP colocation is colocation where you announce your own IP addresses from your own autonomous system number (ASN), over BGP sessions with two or more carriers, instead of using the provider’s addresses. You need an ASN, at least a /24 of IPv4 or a /48 of IPv6, a router and a cross-connect to each carrier. If you take full routes, your router holds about 1.09 million IPv4 prefixes (CIDR Report, November 2026).

Updated November 2026 · Bob Spiegel, Founder, QuoteColo

A carrier-grade router in a colocation rack with yellow single-mode fiber patched into its line cards
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

$275
a year for your own ASN from ARIN in 2026, plus $50 once; a /48 of IPv6 at no extra fee
$25.62
median price per address for an ARIN /24, July–November 2026: about $6,500 for the block
1.09 million
IPv4 prefixes in the global routing table (CIDR Report, 17 November 2026)
71.6%
of IPv4 routes are RPKI-valid; major carriers drop the invalid ones (NIST, 16 November 2026)

From ARIN’s 2026 fee schedule and policy manual, IPv4.Global’s public sales record, the CIDR Report and NIST’s RPKI Monitor, read 17 November 2026.

What BGP colocation is (and what it isn’t)

With standard colocation the provider gives you addresses from its own space and routes them for you. With BGP colocation you bring your own ASN and IP space, set up BGP sessions with your upstreams and decide what you announce to whom. The facility provides the rack, the power and the cross-connects.

Standard colocationBGP colocation
IP addressesThe provider’s; they change when you moveYour own provider-independent space; it moves with you
ASNThe provider’sYour own
RoutingThe provider decidesYou set the policy per upstream
When a carrier failsYou wait for the provider’s networkTraffic moves to your other carrier
Who it’s forMost single-site deploymentsISPs, hosting companies, CDNs, VPN networks and SaaS teams that need multi-homing

Provider-independent (PI) vs provider-aggregatable (PA) space

Before you run BGP, decide what address space you’ll announce. Real multi-homing across two independent carriers usually needs your own space, and a /24 of IPv4 or a /48 of IPv6 is the smallest block most networks accept.

Provider-independent (PI)Provider-aggregatable (PA)
Who issues itARIN, to your organizationYour upstream provider, from its own block
When you change providersIt moves with youUsually returned to the provider
Multi-homing to two carriersYes: announce it to bothOnly with that provider’s consent, and still tied to it
What you needAn ARIN agreement and your own ASNA contract with the provider

Getting an ASN and addresses from ARIN in 2026

ResourceCostHow it works
Your own ASN$275 a year in 2026, $288.75 in 2027, plus $50 once to set up your organizationThe same fee for ISPs and end users. Any organization can get one ASN on request; ARIN aims to review it within two business days.
A /48 of IPv6No extra feeCovered by the same annual fee if you multi-home with your own ASN.
A /24 of IPv4, boughtAbout $25.62 per address in late 2026, roughly $6,500, plus ARIN’s $187.50 transfer feeYour first /24 needs no usage justification. ARIN’s free pool ran out in 2015, so this is the usual route.
A /24 of IPv4, waiting listThe annual fee onlySlow: the oldest open request that would take a /24 dates from 31 October 2025.
A /24 for IPv6 transitionThe annual fee onlyFrom ARIN’s reserved pool (12,764 /24s left), if it serves IPv6 deployment such as NAT64.
IPv4, leasedAbout $0.35–0.60 per address a month, roughly $90–150 for a /24Marketplace rates. Or use a /24 from your transit provider, which is PA space.

Sources: ARIN’s 2026 and 2027 fee schedules and policy manual; IPv4.Global’s public sales record (ARIN /24 sales, July–16 November 2026); leasing rates from IPXO and IPv4.Center. The /24 and /48 limits are in RFC 7454 and carriers’ routing policies.

What an ARIN /24 sold for, median price per address

  • First half of 202557 sales
    $34.56
  • Second half of 202556 sales
    $30.00
  • First half of 202679 sales
    $23.00
  • July–November 202660 sales
    $25.62

Completed sales of ARIN /24 blocks in IPv4.Global’s public sales record, read 17 November 2026. Multiply by 256 for the price of the block.

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

BGP session setup: what you’re actually configuring

Once you have an ASN, address space and a cross-connect to each upstream, three things decide how your routing behaves.

  1. Sessions

    One eBGP session per upstream

    What you set

    Your prefixes go out to each carrier; routes come back. Take a default route if you only need failover, or full routes, about 1.09 million IPv4 prefixes, if you want to choose paths per destination.

    Watch for

    Full routes need a router with the memory and forwarding table to hold them, with room to grow.

  2. Filtering

    Route objects and RPKI

    What you set

    Register a route object in an internet routing registry and sign a Route Origin Authorization (ROA) for each prefix in ARIN’s RPKI, which is free once your space is under an ARIN agreement.

    Watch for

    A ROA that doesn’t match your announcement makes the route invalid, and Lumen, Arelion, NTT and Zayo drop invalid routes. 71.6% of IPv4 routes were valid in November 2026.

  3. Steering

    Communities and preference

    What you set

    Local preference picks your outbound carrier; AS-path prepending and each carrier’s BGP communities shape how traffic comes in.

    Watch for

    Two ports on the same carrier aren’t multi-homing. You need two different networks.

What the colocation facility needs to support

Not every facility suits a BGP deployment. Check these before you sign.

What you needWhyWhat to ask
Independent carriers on-netMulti-homing needs two networks reachable by cross-connect, not two services from the facility’s own network.Which carriers are in the meet-me room, and can I announce my own prefixes to each? See carrier hotel colocation.
An internet exchangePeering takes traffic to big content and access networks off paid transit.Which exchanges have a switch in the building, and what do the port and the cross-connect cost?
Diverse physical pathsRouting redundancy fails if both uplinks share one conduit.Do the two cross-connects use separate pathways and building entries?
Your own routerYou need full control of the BGP configuration.Can I install customer-owned routers, and which port speeds can you hand off?
A+B power to the routerTwo upstreams don’t help if the router loses power.Are independent A and B feeds delivered to my cabinet? See A+B power colocation.
Remote hands with console accessA misconfigured session can lock you out of your own router.Can on-site staff connect a console cable and work through your runbook, and at what rate?

BGP colocation pricing: what you’re actually paying for

BGP colocation costs more than standard colocation because of the network around the rack, not the rack. Here is one rack in Dallas with two upstream carriers.

One rack with two upstreams, per month

  • The rack quoteFull 48U, 5 kW, 1 Gbps, Dallas
    $1,500–1,750
  • Plus two cross-connectsOne to each carrier
    $1,900–2,950
  • The monthly billPlus two 1 Gbps transit commits
    $2,300–4,950

Ranges, not a quote: built from the line items below.

The line items

Line item$/monthWhere the number comes from
Rack: full 48U, 5 kW, with a 1 Gbps port$1,500–1,750Our November 2026 price sheet for Dallas. If your own carriers replace the facility’s port, ask for the rack without bandwidth.
Two cross-connects$400–1,200$200–600 each at premium interconnection hubs; install fees on published rate cards run $500–1,000 each.
Two 1 Gbps transit commits$400–2,000About $200–1,000 per carrier (Hurricane Electric’s starting price; Equinix’s own 1 Gbps billing example). Smaller commits cost less in total but more per Mbps.
Exchange port (optional)From about $104$1,250 a year for 10G at a community exchange such as FL-IX; commercial exchanges quote on request.
Monthly bill$2,300–4,950Before the router, ARIN fees and any exchange port.

Transit has fallen for years: TeleGeography puts 10G ports in New York and Los Angeles at about $0.18 per Mbps (2024) and 100G in New York near $0.10 (Q2 2026). Quotes of $2–8 per Mbps are out of date.

BGP colocation markets: where to be and why

BGP works in any carrier-neutral facility, but the depth of carriers and exchanges in a metro decides how far you can take it. PeeringDB lists 240 active exchanges in the US and Canada; these are the largest in the main metros.

Networks on each metro’s largest exchange (PeeringDB, November 2026)

  • SeattleSeattle Internet Exchange (SIX)
    365 networks
  • Ashburn, VAEquinix Ashburn
    346 networks
  • New YorkDE-CIX New York
    264 networks
  • Los Angeles and Silicon ValleyAny2West
    262 networks
  • ChicagoEquinix Chicago
    256 networks
  • TorontoTorIX
    233 networks
  • DallasEquinix Dallas
    210 networks
  • MiamiFL-IX
    199 networks
  • AtlantaDigital Realty Atlanta
    145 networks
  • DenverIX-Denver
    90 networks
  • PhoenixNinja-IX Phoenix
    57 networks

Networks with a port on the exchange. By peak traffic the order differs: Equinix Ashburn is the busiest US exchange (6.39 Tb/s in the 30 days to 17 November 2026), ahead of Equinix Chicago, SIX, Equinix Dallas and DE-CIX New York.

Where BGP buyers land

MetroExchanges (networks)Why BGP buyers pick it
SeattleSeattle Internet Exchange (SIX) (365)The US exchange with the most members, plus Pacific and Asia routes from the Westin Building.
Ashburn, VAEquinix Ashburn (346); NVIX (61)Exchange depth next to the largest cloud regions; BGP transit and cloud on-ramps from one building.
New YorkDE-CIX New York (264); NYIIX (186)Two large exchanges and the carrier hotels at 60 Hudson and 111 8th Avenue.
Los Angeles and Silicon ValleyAny2West (262); Equinix San Jose (182)Trans-Pacific routes through One Wilshire, and Silicon Valley’s cloud campuses.
ChicagoEquinix Chicago (256); DE-CIX Chicago (85)The Midwest’s main interconnection point at 350 East Cermak.
TorontoTorIX (233); ONIX (176)Canada’s largest exchanges, for Canadian networks and data residency.
DallasEquinix Dallas (210); DE-CIX Dallas (163)Central US reach and two large exchanges at the Infomart; often a lower-cost first PoP.
MiamiFL-IX (199); Equinix Miami (174)Latin America and Caribbean routes at the NAP of the Americas.
AtlantaDigital Realty Atlanta (145); CIX-ATL (120)The Southeast’s main carrier hub at 56 Marietta Street.
DenverIX-Denver (90); Any2Denver (74)Mountain West reach for regional ISPs.
PhoenixNinja-IX Phoenix (57); DE-CIX Phoenix (37)A growing market where exchanges are smaller; check the carriers you need.

Exchange size is one signal. Check the specific carriers you need against each building’s on-net list; our carrier hotel guide lists the networks per building.

Who uses BGP colocation and what they’re deploying

The same protocol, very different deployments.

WhoWhat they deployWhat they need from the facility
ISP or regional network1–10 racks: routers, transit from several carriers, exchange peering; announces its own space to customersTier 1 carriers on-net, an exchange, customer-owned routers, carriers that filter with RPKI
Hosting company10–100+ racks and a large address block; traffic engineering across upstreamsCarrier depth, exchange peering and enough volume to negotiate transit
CDN or anycast operatorNodes in several metros announcing the same prefixUpstreams in each metro that accept the anycast prefix without filtering it
SaaS team adding multi-homing2–10 racks, its own /24 or /23, two upstreams for failoverTwo independent carriers, diverse paths, A+B power; active/passive is enough
VPN or security networkSmall points of presence in many metrosAnycast support and clean routing in every market
Trading infrastructureRouters next to exchange connectivity, with its own stable addressesPhysical path diversity between upstreams

Minimum viable BGP colocation: what you actually need

BGP colocation sounds bigger than it is. A first deployment needs this much, and no carrier hotel.

In the rack

  • A BGP-capable router, or a server running FRRouting or BIRD
  • A half or full rack for the rest of your equipment
  • A+B power to the router

Addresses and registration

  • An ASN
  • At least a /24 of IPv4 and a /48 of IPv6
  • Route objects and a signed ROA for each prefix

Connectivity

  • Two transit carriers on different networks
  • One cross-connect to each
  • An exchange port later, once your traffic justifies it

Why “BGP supported” on a facility’s website doesn’t answer the question

Most facilities will let you run BGP. Whether you get two independent upstreams at a price that works is a different question.

THE DIY WAY

You ask if they support BGP

They say yes, then sell you a session on their own blended network. That’s BGP with one upstream: if their network has a problem, so do you.

THE DIY WAY

You pick the building, then the carriers

The two carriers you want may not both be on-net. One arrives as an off-net circuit that takes months.

THE DIY WAY

You compare rack quotes

Transit, cross-connects and the exchange port are billed apart from the rack, often by different companies.

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: BGP colocation

What's the difference between BGP colocation and standard colocation?

In standard colocation the provider gives you addresses from its own space and routes them from its own ASN. In BGP colocation you bring your own ASN and provider-independent addresses, run BGP sessions with your upstream carriers over cross-connects, and set your own routing policy. The facility supplies the rack, power and cross-connects; the routing is yours.

Do I need my own ASN for BGP colocation?

Yes, to announce your own prefixes to several carriers. From ARIN it costs $275 a year in 2026 ($288.75 in 2027) plus $50 once to set up your organization, the same for ISPs and end users, and any organization can get one on request. If a provider announces your space from its ASN instead, that’s a managed BGP service, not your own routing.

What is a /24 and why do I need at least one?

A /24 is a block of 256 IPv4 addresses, the smallest block most networks accept in BGP; for IPv6 it’s a /48. Your first ARIN /24 needs no usage justification. Most organizations buy one on the transfer market, about $25.62 per address or roughly $6,500 in late 2026, plus a $187.50 ARIN fee, or lease addresses at about $0.35–0.60 each a month.

What is RPKI and why does it matter for BGP colocation?

RPKI lets you sign a Route Origin Authorization (ROA) saying which ASN may announce your prefixes. Large carriers including Lumen, Arelion, NTT and Zayo drop routes that are RPKI-invalid, and 71.6% of IPv4 routes were valid in November 2026. Create ROAs in ARIN’s RPKI, free once your space is under an ARIN agreement, before your first announcement.

How long does BGP convergence take when an uplink fails?

With default timers, up to 90 seconds by the standard and on Juniper, or 180 seconds on Cisco, before the dead session is noticed and routes move. With BFD running alongside BGP, failures are detected in about 0.3–0.9 seconds. Run BFD with each upstream that supports it if failover time matters.

Can I do BGP anycast from multiple QuoteColo-matched facilities?

Yes. Anycast means announcing the same prefix from several metros. We match facilities in each market you need, ask whether their upstream carriers accept the anycast announcement without filtering it, and send the options by email within 48 hours once the requirements are clear. Tell us it’s for anycast in your requirements.

What's the minimum commitment for a BGP colocation deployment?

There’s no BGP-specific minimum: you sign the facility’s standard term, often 12 months or more, and each carrier’s minimum transit commit. As a guide, one 5 kW rack in Dallas with two cross-connects and two 1 Gbps transit commits comes to about $2,300–4,950 a month on our numbers, before the router and ARIN fees.

Can a facility block my BGP announcements?

Not if it gives you real cross-connects to independent carriers: the BGP session runs between your router and the carrier, over fiber the facility only provides. A facility that routes you through its own network instead can limit what you announce, which is why we confirm direct carrier access before a facility goes on your shortlist.

Does QuoteColo charge for BGP colocation matching?

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