Network identity
A public ASN, an accurate PeeringDB profile, and the routing policy you plan to use at the exchange.
Network requirements, handoff details, and routing information for your connection.
Start with your network identity, reach, and capacity needs. These are the details we need to assess a connection.
A public ASN, an accurate PeeringDB profile, and the routing policy you plan to use at the exchange.
Current or planned router locations, carrier handoffs, and transport reach in North or South Carolina.
Expected initial port capacity, growth horizon, and target timing for a connection.
A monitored technical contact for turn-up, routing, maintenance, and incident coordination.
The connection specification will cover the items below. Site-specific values will be published before orders open.
Facility, meet-me-room, demarcation, cross-connect, transport, and authorization details for each connection site.
Available interfaces, optics, link aggregation, MTU, delivery steps, and acceptance testing.
IX ASN and addressing, route-server endpoints and policy, BGP communities, filtering, and prefix limits.
LOA/CFA workflow, NOC and escalation channels, maintenance notices, incident handling, and support boundaries.
The connection guide brings access arrangements, agreements, and turn-up steps together in one place.