[ Connectivity · Partners ]

Carriers and partners in The Hague.

DFDC is carrier-neutral by structure. We own the colocation and the BareFABRIC fabric, but we do not own the dark fiber underneath and we do not have an upstream we are pushing. Several independent carriers terminate inside THG1; tenants pick the contract structure, the route and the term that fits. One canonical page per partner with the public facts — role at DFDC, AS number where applicable, integration model.

Dark fiber carriers
7
IP carriers
4
Native peering
LSIX
Exchanges
2 · via fabric
[ In-building dark fiber ]

Independent dark-fiber carriers in THG1.

Each terminates inside the meet-me area on redundant building entries. Tenants pick the carrier and the contract structure; DFDC issues the LOA and pulls the cross-connect at the patch panel.

[ IP carriers ]

Global IP carriers reachable from THG1.

Major Tier-1 and regional IP networks present in the THG1 meet-me area. Provision a direct cross-connect, or take IP transit on the BareFABRIC blend — the BGP best-path selects whichever upstream gives the shortest AS_PATH for each destination.

[ Internet exchanges ]

Exchanges peering at THG1.

Peering, delivered by LSIX (the LayerSwitch Internet Exchange), is native on every BareFABRIC Port. The exchanges below are reachable on the same fabric without a separate cross-connect.

[ IP transit at THG1 ]

Transit providers selling in the building.

Four networks sell IP transit directly at THG1 — order a cross-connect, or reach them over any BareFABRIC Port. The Internet Port from DF stays the one-stop option; these are the routes for networks that prefer to pick their own upstreams.

[ How the partner layer is structured ]

Carrier-neutral by structure, not by claim.

Carrier-neutral means more than a marketing line. Data Facilities owns the colocation and the BareFABRIC fabric. We do not own the dark fiber underneath, and we do not have an upstream we are pushing. Multiple independent carriers terminate inside THG1; tenants pick the one whose contract structure, route, IRU and term fits.

For IP, BareFABRIC offers a transit product on every port — useful for tenants who want a single invoice and a single SLA. For tenants who already buy transit from a specific carrier, the same carrier is reachable as a direct cross-connect at the patch panel. We are not in the middle of that relationship.

The practical effect for tenants: real choice at every layer, no hosting provider sitting in the middle of the carrier relationship, no rebill markup on the underlying fiber.

  • Independent dark-fiber carriers in-building, redundant paths each
  • LOA workflow through the BareFABRIC portal
  • OS2 single-mode hand-off in the meet-me room
  • Direct cross-connects to global IP carriers
  • Native peering on every BareFABRIC port
  • AMS-IX reachable via partners in the building
[ Connect ]

Quotes across every in-building carrier.

A request specifies the endpoints, the term and any diversity requirements. The response returns per-pair, per-route, term-based pricing across the selected carriers, with a BareFABRIC IP transit option where it applies.