Skip to content

Verify and go live

Run these checks for each tenant once its ports are up and its external Border Gateway Protocol (eBGP) sessions are established. A computing provider runs them for each downstream customer.

Run the checks

The checks cover routing between tenants. This site does not describe routing for internet or Amazon Web Services (AWS) access: if your order includes either, ask your TheHUB contact what you receive for that access before you run the default-route check.

Check What you should see Who runs it
Physical port up The link light is on and the interface is up on both sides, on each leaf port TheHUB confirmed for the tenant You and TheHUB
Port speed matches the order Each delivered port speed is the speed on your order You and TheHUB
Session established Your router shows each eBGP session to TheHUB's Autonomous System Number (ASN) as Established, matching your allocation table You
Only the registered block accepted TheHUB confirms it accepts the tenant's block and nothing else TheHUB
An out-of-list prefix is dropped A prefix outside the tenant's block is not accepted TheHUB, with you announcing
Opposite role's address space received The opposite role's aggregate is in the tenant's received routes You
No default route No default route is received from TheHUB You
DoubleZero endpoints present The user-tunnel endpoints of TheHUB's DoubleZero device (DZD), its node on the DoubleZero private fiber network, are in your received routes You
Same-role isolation No route to a tenant of the same role is in the tenant's routing table. Check the routing table, not only what is advertised You and TheHUB

Reading a traceroute across TheHUB

TheHUB's switches answer traceroute probes, while many edge routers rate-limit theirs. Apparent loss partway along a traceroute usually belongs to your edge router, the one that hands traffic to TheHUB, not to TheHUB's fabric.

A 169.254 address on a peering link

TheHUB keeps link-local space (169.254.0.0/16) off customer-facing links. Automatic Private IP Addressing (APIPA) uses the same range: a host assigns itself an address from it when Dynamic Host Configuration Protocol (DHCP) fails. A 169.254 address on a peering link is a sign of misconfiguration.

Go live

When the checks pass:

  1. You confirm to your TheHUB contact that the service matches the order.
  2. TheHUB sends a provisioning notification, its formal notice that the ordered services are provisioned.
  3. The tenant is service live. Service live is your milestone for that tenant.

See also

  • Onboarding: the onboarding guides that lead to these checks.

Last reviewed 2026-11-16.