A different kind of interconnection market

Bring us two endpoints. We’ll build the middle.

Colocation should not start with square footage. Start with where traffic lives and where it needs to go. We combine racks, cross-connects, transit, IX access, private transport, and new fiber into one regional network design.

Map your A and Z See available space
Endpoint A Your network Premises · facility · carrier · tower
The regional core Paducah + Metropolis Colocation · cross-connect · transport · Paducah IX
Endpoint Z Where you need to reach Network · cloud path · market · second site
1U / 100WEntry point for network gear
2 hubsPaducah + Metropolis
100GPublished Paducah IX port AS399788Registered autonomous system

Change the buying order

Space is a component. The path is the product.

The conventional buying journey makes customers assemble the facility, carrier, local loop, handoff, and route plan one vendor at a time. Quad State starts with the complete traffic path, then fits the physical deployment to it.

Conventional rack-first journey

Buy the room. Then solve the network.

  1. Choose a facility and cabinet footprint
  2. Find a carrier already inside the building
  3. Source the last mile and cross-connects
  4. Reconcile the vendors when the route changes

The topology inherits the limits of the real estate.

Quad State endpoint-first journey

Design the path. Place only what it needs.

  1. Give us endpoint A and endpoint Z
  2. Choose the handoff, capacity, and resilience target
  3. Use the rack, route, transit, or IX components that fit
  4. Extend with private transport or build-by-demand fiber

One regional design conversation, from endpoint to endpoint.

The Ohio River regional core

A meeting point that can move.

Meet the network in Paducah or Metropolis, then keep going. The same conversation can cover the equipment, the handoff, the upstream, and the physical route beyond the hub.

Bring traffic in

Enterprise premises
Carrier handoff
Regional facility
New fiber lateral

Meet in the core

Hub 01 Paducah Colocation, transport, transit, BGP, and Paducah IX access
Hub 02 Metropolis Regional colocation, interconnection, and route extension

Start with as little as 1U / 100W for network equipment, or plan capacity toward a larger deployment.

Take traffic out

Private transport
Internet transit
Paducah IX peers
Custom market route

Use only what the path needs

Four ways through the core.

These are not four separate sales funnels. They are building blocks that can work together around the endpoints, capacity, resilience, and handoff you specify.

01 / MEET

Cross-connects

Create private handoffs between customer equipment, Quad State Internet, carriers, transport providers, and Paducah IX participants.

Understand cross-connects
02 / MOVE

Private transport

Carry traffic between facilities with Ethernet, wavelengths, dark fiber, protected paths, and regional or long-haul transport.

Explore private transport
03 / REACH

Transit, BGP + IX

Reach upstream Internet providers and regional peers with IP Transit, BGP-ready designs, and access to the Paducah IX ecosystem.

Explore Internet transit
04 / EXTEND

Custom routes

Extend the hub toward a premises, carrier meet point, service provider, or new market with custom laterals and build-by-demand fiber.

Plan a custom route

Start with the network question

Where is endpoint A? Where should endpoint Z be?

Send the locations, capacity target, handoff, timeline, and resilience requirement. We’ll evaluate the path through the Paducah–Metropolis core.

Put endpoints on the map View colocation options