Power gets diligenced.
Land gets diligenced.
Fiber gets assumed.
Connectivity is the last unpriced risk in a data center deal — and the one that strands capital when the answer arrives late. Connectbase moves that answer to the front of your site screen, then carries the same location through quoting, ordering and reconciliation.
Address · Coordinate · A-to-Z path · Route diversity · Facility context
Connectbase never buys or sells connectivity. You transact directly with the provider.
Same location object flows into Quote → Order → Inventory → Financial.
Values shown are an illustrative archetype, not live platform output.
400+ US · 350+ INTERNATIONAL
LANDING STATIONS1
20K+ EDGE · 20K+ CENTRAL OFFICES1
CONNECTBASE LOCATION GRAPH2
PARTICIPATE ON THE PLATFORM3
Connectbase never buys or sells connectivity. Not a broker, not a reseller, never a party to your transaction. No margin on the circuit you choose, no supplier who paid for placement, no reason to steer you.
Read the full position →You will not buy a site you cannot power. You will absolutely buy one you cannot connect.
Substation queue position, interconnect studies and megawatt availability are modelled to the month. The fiber question is usually answered by a handful of emails to whoever the team happens to know — after the site is already on the shortlist, and often after the option is signed.
You asked three operators. There were eleven.
Coverage knowledge is relationship-shaped. The routes you learn about are the ones belonging to people already in your address book — which is not the same as the routes that pass the site.
"Diverse" meant two strands in one conduit.
Two providers on the paperwork can share a single physical path, a single bridge crossing, a single duct bank. Diversity asserted in a proposal is not diversity evidenced on a route.
The lateral quote came back at week seven.
Serviceability, pricing and build cost arrive on the provider's calendar, not yours. By the time the number lands, the site decision has already been made on an assumption.
The spreadsheet stopped at signature.
The diligence work dies at the LOI. Nothing carries into ordering, nothing reconciles against the invoice, and eighteen months later nobody can say what is installed at the campus or what it costs.
Three jobs, three different answers. Which one is yours?
A developer siting a campus, a fund underwriting someone else's, and a network team connecting an estate that already exists are asking related questions with very different stakes. Switching role changes the problem framing, the deliverable, the site archetype below, and the economics in the model.
Grade a site on connectivity before you grade it on anything else.
Four campus archetypes we see repeatedly in AI and data center development. Select one to see what a connectivity screen returns — and what the delay it exposes is worth against your own capital assumptions.
deferred = MW × rev/MW/month × months
exposure = carry + deferred
Transparent arithmetic on inputs you control. Connectbase does not shorten construction or provisioning. It removes the weeks spent discovering whether a site can be connected at all — and moves that answer to the point in the diligence where acting on it is still cheap.
One location object, carried from site screen to installed estate.
The reason this is not a map subscription: the parcel you screened is the same record that gets quoted, ordered, inventoried and reconciled. Nothing is re-keyed, and nothing is lost between stages.
The physical layer, assembled once — so a site screen takes minutes.
Route geometry, facility footprints and provider serviceability are separate data problems that every developer otherwise solves alone, per site, from scratch. Toggle a layer to see what it contributes to a decision.
This is the working surface.
The Connected World is the map interface your team uses directly. Search an address or coordinate, drop a path between two points, open the provider table for a location, export routes to KMZ for the design package.
Live platform view · fiber routes, subsea systems and building footprints across the graph · source: cw.connectbase.com
Before you send us a site, see what comes back.
Asking a developer to disclose a shortlist without showing the deliverable is a bad trade. This is the format of a Site Connectivity Readout — one page per site, redacted here.
SITE Site reference ......... [REDACTED] Resolved coordinates ... [REDACTED] Location ID (GLID) ..... CB-••••-••••-•••• Screened ............... [DATE] Analyst: Connectbase SE SERVING OPERATORS — 7 IDENTIFIED OPERATOR STATUS MEDIUM DIST BUILD Operator A ..... ON-NET Fiber 0.31 mi Lit Operator B ..... ON-NET Fiber 0.44 mi Lit Operator C ..... ON-NET Fiber 0.62 mi Lit Operator D ..... NEAR-NET Fiber 0.90 mi Lateral required Operator E ..... NEAR-NET Fiber 1.41 mi Lateral required Operator F ..... NEAR-NET Fiber 1.88 mi Lateral required Operator G ..... ADJACENT HFC 0.20 mi Serviceable PATH DIVERSITY Path 1 → [INTERCONNECT POINT] ... 32.4 route mi · Operators A, D Path 2 → [INTERCONNECT POINT] ... 41.7 route mi · Operators B, F Physically separate ................. YES — no shared structures identified Shared crossings reviewed ........... 3 (rail, river, interstate) FACILITY CONTEXT — 25 MILE RADIUS Third-party data centers ... 6 Edge facilities ....... 11 Telco central offices ...... 4 Cable landing station . none <200 mi QUOTING READINESS Suppliers connected for structured quoting at this location ... 9 Next action ....... request pricing on Paths 1 and 2, and the Operator D lateral, in a single quote set Every figure above carries a source and a date in the delivered version. Operator names, coordinates and interconnect points are redacted in this sample.
Same question. Two very different answers.
“Can this site be connected, by whom, on what paths, at roughly what cost, by when?” — asked at the point in the process where the answer still changes the decision.
| Dimension | How it gets answered today | On Connectbase |
|---|---|---|
| Who you ask | Whoever is already in the team’s address book | Every operator with route geometry or serviceability at the location |
| Time to a first answer | Days to weeks, dependent on who replies | The same session — search, path, provider table |
| Geographic reach | Strong where you have relationships; blind everywhere else | 400+ US and 350+ international route operators, subsea and CLS worldwide |
| Diversity evidence | Asserted in a proposal; verified after commissioning, if ever | A-to-Z path search with route geometry and KMZ export into the design package |
| Pricing basis | Whatever the responding parties choose to send | Structured quotes requested across connected suppliers, in comparable form |
| Position in the outcome | Whoever answers may also have a position in the deal | Connectbase holds no position — you contract directly with the provider, with or without an advisor |
| What happens next | The spreadsheet is emailed onward and re-keyed at every stage | The same location moves into order, inventory and invoice reconciliation |
| Auditability | An inbox | A record with source, date and confidence — usable in an IC memo |
Why a capital allocator should trust the data
Connectbase does not buy or sell connectivity. It is not a broker, not a reseller, and never a party to your transaction. There is no margin on the circuit you select, no preferred supplier who paid for placement, and no incentive to route you toward one answer over another.
The business is the accuracy of the location record and the speed of the workflow. That is the entire alignment — and it is the reason 30 of 30 of the largest US networks and the suppliers connected through the Federated Ecosystem Fabric are willing to expose serviceability on the platform in the first place. A party with a position in the deal could not have assembled this data, because no operator would supply it.
Advisors and consultancies run on this too. Connectbase is the data and workflow layer underneath the advice, not a substitute for it. If you are already working with an advisor on site selection, subsea strategy or capital diligence, bring them — the readout is theirs to use, and the judgment stays where it belongs.
Quotes processed across the Connectbase platform — the transaction density that keeps supplier serviceability and response behaviour current rather than static.
Countries covered, with participation spanning carriers, fiber operators, cable and data center operators. Avant and Granite Telecommunications are among the customers cleared for external reference.
Revenue earned on the connectivity you buy. Connectbase is paid for the platform, never for the transaction — which is what makes the serviceability data available to supply in the first place.
The Connectivity Diligence Checklist for AI & Data Center Site Selection — twelve questions to answer before an LOI. No site details required.
Take the checklist instead →Take the checklist instead.
The Connectivity Diligence Checklist for AI & Data Center Site Selection — twelve questions to answer before an LOI, and what an acceptable answer looks like for each.
- How many operators actually pass the parcel, and how you find out
- What "diverse" has to mean before it belongs in an IC memo
- The three shared structures that quietly collapse two paths into one
- When to price a lateral build versus when to walk from the site
- What to put in the schedule when the provider will not commit a date
Site Connectivity Diligence Review
Send up to five candidate sites — address or coordinate. We return the readout you saw above on each one and walk you through it. No obligation, no circuit sold, no intermediary inserted.
Request a site review
Reviewed by a connectivity commerce specialist, not an automated report.
Prototype form — not wired to HubSpot. Properties on submit:
cb_content_asset_id · cb_traffic_source · cb_utm_campaign · cb_persona_track · cb_site_archetype · cb_exposure_modeled · cb_cloud_interest
Route operator counts and facility layers reflect The Connected World data inventory. Location Graph and platform figures are Connectbase platform metrics. Each figure carries a source and an as-of date in the published version of this page.
Two counts that are often confused. Mapped route operators counts operators whose terrestrial fiber route geometry is carried in the platform. Connected suppliers counts suppliers reachable for structured quoting through the Federated Ecosystem Fabric. They are different populations and should not be added together.
Illustrative content is labeled as such. The site archetypes, the exposure model and the sample readout are constructed to show the shape of the question and the format of the deliverable. They are not platform output and carry no performance claim.