AS 53292 IP transit across our own fiber across Southeast Michigan, up to 100Gbps per port. 100% uptime SLA on every dedicated circuit. 30+ network partnerships globally, so the routes you need land short.
Lit fiber to the building, wholesale eBGP transit on AS 53292, and private circuits between your sites. Same engineering team behind each shape, same SLA scope on the segments we operate.
Dedicated fiber circuits from 100Mbps through 100Gbps, terminated on AS 53292. Built across our own fiber across Southeast Michigan, so the route to your building is one we own, light, and operate.
Tell me moreSingle or dual-homed eBGP transit with route filtering, communities, blackhole tagging, and BFD. 30+ network partnerships globally, with direct peering at the exchanges we sit on.
Tell me moreLayer 2 EVPL, EPL, VPLS, and DWDM wavelengths between two or more sites across Southeast Michigan, or extended off-net to a partner backbone where you need to reach further. Fixed Wireless on a clear line of sight where a radio link makes more sense than fiber.
Tell me moreFiber to the building is the right long-term answer. When the build needs time, or when one path is not enough, three faster shapes stand up alongside it as a bridge or as a second circuit.
Licensed-spectrum radio between buildings on a clear line of sight. Stands up in days while a fiber build runs underneath, and stays available as a diverse second circuit afterward.
Cellular uplink on a managed CPE that takes over when the primary drops. Quick to provision where carrier coverage works, paired with a dedicated circuit as the steady path.
A second circuit on a different fiber path, or from a nearby site you already occupy, so a fault on one segment does not take both down. Covered under our Point-to-Point product.
The autonomous system, the peering footprint, and the capacity behind every circuit we sell.
Our autonomous system. Full eBGP transit, peering, communities, MD5, BFD, route filtering.
Network partnerships globally, including direct peering at the major exchanges we sit on.
Per-port capacity available where the build warrants it.
What we'll commit to in writing and what's behind the commitment.
Uptime SLA on every dedicated circuit. Measured at the egress port, credited against monthly recurring.
Our autonomous system. Full eBGP with the BGP hygiene you'd expect.
Per-port capacity available where the build warrants it.
Network partnerships globally. Direct peering at the major exchanges.
Owned fiber across the region, lit and operated by our team.
Operating continuously. Same engineering team across all of it.
Three workloads, three customer profiles, three case studies. Names withheld; the engineering is what we'll talk about.
A Fortune 500 manufacturer runs corporate WAN across three regions through circuits we provision, with our team handling routing and the SLA on the segments we own.
Read the case studyA global VoIP carrier sits with us for transit and floor space, with peering that reaches the operators on the other end of the calls.
Read the case studyA multi-continent cloud security platform announces anycast IP space out of sites we operate, with the routing-policy coordination the design needs.
Read the case studyThe ones we get on the first call from someone comparison-shopping transit. If yours aren't here, the answer is on the other end of the phone.
The SLA measures availability at the customer-facing egress port on our equipment. Anything past that sits outside the SLA scope: your CPE, your LAN, an upstream we don't own, a peer's outage downstream of us. We'll say so plainly in the contract. Inside that scope, any minute of downtime on a dedicated circuit credits proportionally against the month's MRC. The math is in the agreement so you know what you're signing.
30+ network partnerships globally. A mix of direct peering at the major exchanges where we have a presence, private interconnects to large content and cloud networks, and selective wholesale relationships with backbones whose routes converge better than the cheapest path. The full list goes out under NDA when a specific build calls for it; the public portion is visible on the AS 53292 IRR record.
Yes. Full-table eBGP for customers who want it, partial-table or default-only for the ones who'd rather not carry the whole DFZ. Communities for traffic engineering, MD5 session authentication, BFD with vendor-supported timers, inbound and outbound prefix filtering against IRR or an explicit list you maintain, max-prefix limits with reasonable reset thresholds, source-address validation per BCP38. ASN, MD5, BFD timers, and max-prefix get exchanged in writing before turn-up.
On-net lit fiber in a building we already serve is typically a few business days from signed order to live port. A new build into a building off-net depends on the path: where the entrance is, what permits the route needs, whether the right-of-way already has dark fiber we can light. We'd rather quote the realistic date in the proposal than promise a fast one and miss it.
Yes, and none of it is optional or upcharged. BFD with vendor-supported timers for sub-second convergence where the platform supports it. MD5 session authentication on every BGP session by default. Inbound and outbound filtering against IRR or against an explicit prefix list you maintain. Max-prefix limits and AS-path filtering on transit. It's what well-run BGP transit looks like.
Tell us the build: the buildings, the capacity, the routes you need to land where. We'll quote what fits. If that's not us, we'll point you to who.
Get in Touch