1U / 100W 1 MW

Put the equipment where the networks meet.

Quad State is built for network-first colocation: routers, transport gear, carrier nodes, peering platforms, and IX participation. Start with a single device or plan a dedicated environment. Enterprise and higher-density compute are welcome too—engineered around the actual load.

Starting footprint1U / 100W
Planned environmentThrough 1 MW
Network fitPeering, IX, transit, transport + cross-connects
What fits best

Built first for networks. Ready for compute.

Our sweet spot is telco colocation and IX participation—equipment that becomes more useful when it sits close to routes, peers, carriers, and handoffs. Standard enterprise workloads fit too. High-density or HPC deployments are treated as engineered power-and-cooling projects, not the default footprint.

01 / Network + interconnection

Telco and IX colocation

Place the router, transport shelf, carrier node, peering platform, or exchange-facing gear at the point where the useful networks meet.

  • Footprints from 1U / 100W
  • Paducah IX participation and regional peering
  • Cross-connects, carrier handoffs, and remote hands
  • BGP, IP transit, private transport, and dark fiber
02 / Enterprise + engineered compute

Planned environments through 1 MW

For servers, storage, edge platforms, and larger contiguous deployments. Unusually dense loads get a custom power-and-cooling plan built around the equipment.

  • Rack, cage, room, or dedicated-site planning
  • Site, utility, power, cooling, and redundancy design
  • Facility, network, and route construction
  • Commissioning and documented acceptance
Built to a delivery month

A schedule you can plan operations around.

Large deployments are not presented as “available someday.” The proposal ties a target delivery month to explicit site, utility, equipment, permitting, and customer assumptions.

Start the capacity review
01

Validate the load

Confirm critical IT power, rack density, cooling approach, footprint, redundancy, access, and requested operations date.

02

Commit the plan

Match the requirement to a site and utility path, then document milestones, responsibilities, commercial terms, and the target month.

03

Build in parallel

Coordinate facility, power, cooling, fiber, transport, carrier access, equipment, and construction as one delivery program.

04

Commission and turn up

Test the environment and network, document acceptance, establish access and escalation, and bring the deployment into operation.

A standard single-site plan runs through 1 MW. Select sites can be engineered toward 2–3 MW only after utility and site validation. Larger requirements become a distributed multi-site architecture or a dedicated infrastructure program. Final timing depends on site control, permits, equipment lead times, construction conditions, and timely customer decisions.

Quad State Internet enterprise network racks
The reason to colocate

Interconnection is the product.

Put equipment close to Paducah IX, regional peers, carrier handoffs, IP transit, private transport, wavelengths, dark fiber, and cross-connects. We can coordinate BGP, optics, VLANs, LOAs, remote hands, and the physical route—not just power and floor space.

AS399788Quad State Internet autonomous system
2 hubsPaducah and Metropolis
100GPublished Paducah IX port capability
Carrier-neutralCross-connect and handoff coordination
Capacity + network review

Start with power, ports, and peers.

Share the footprint, load, handoffs, networks, resilience target, and date. We’ll determine whether current capacity fits or a project build is required.

This starts engineering review. It is not a promise of space, power, or delivery until the project assumptions are validated.

Bring the gear. We’ll build the meeting point.

Start at 1U / 100W, grow through a planned 1 MW, or ask us to design the next layer.

Plan the deployment