The numbers
don't share.
avg one-way latency
Loop A — Chicago to Aurora
uptime SLA
contractually guaranteed, all metro rings
lower cost-per-bit
vs. lit services at year three
max throughput per strand
limited only by your transponders
Dark fiber vs.
everything else.
Watch the gap build. Every row reveals a metric where shared infrastructure can't compete.
* Latency figures measured Q4 2025, Chicago metro ring. Cost-per-bit analysis based on 10G sustained traffic over 36-month IRU term versus carrier Ethernet and AWS Direct Connect pricing.
Built for the
architects.
1,400+ route miles
Dense metro rings across Chicago, New York, Dallas, and Los Angeles — with intercity backhaul connecting 23 carrier-neutral facilities.
Single-mode OS2
G.652.D compliant. Minimal attenuation over 50km+ spans. DWDM-ready with 96-channel C-band support on every route segment.
Fusion-spliced, zero connectors
Every route segment is fusion-spliced end-to-end. No patch panels in the path. Connector-induced reflections are an MPLS problem.
Geographically diverse paths
Every metro ring ships with at least two physically diverse routes in separate conduit systems — different streets, different manholes.
Dark pairs available now
We do not provision to 90% utilization and call it full. Current build has 40% dark strand inventory held for immediate lease.
Spec your
route.
Tell us your endpoints and bandwidth tier. We respond with available strand inventory, route options, and IRU pricing within one business day.
Build your
business case.
The Strand Versus Report is a 14-page cost-per-bit analysis comparing dark fiber ownership against carrier Ethernet, MPLS, and public cloud interconnect over a 36-month horizon. Built for CTOs making the case internally.
- ◆3-year TCO model (dark vs lit vs cloud)
- ◆Latency benchmarks, 8 metro markets
- ◆IRU vs flex-lease decision framework
- ◆Sample RFP language for procurement