Delivered over Layer 2 or Layer 3. RPKI-ROV and IRR filtering by default. Rich BGP communities for traffic engineering, optional Flowspec and RTBH.
Schematic — simplified.
| Delivery | Layer | Use case | Notes |
|---|---|---|---|
| Cross-connect (same DC) | L2 or L3 | Direct hand-off | Standard lead time (LOA required) |
| NNI / VLAN hand-off | L2 | Aggregating multiple services | QinQ available |
| Wave / DWDM | L1/L2 | Private long-haul | Project-based |
| Tunnel (temporary) | L3 | Expedite turn-up | By exception (GRE) |
Example starting prices for typical profiles — final quotes depend on capacity, site and term.
Physical port in the same DC. Lowest latency, full policy control.
Aggregate multiple services over one physical link (QinQ available).
Fast turn-up over your existing connectivity. Great for trials or remote POPs.
router bgp 65001
neighbor 203.0.113.1 remote-as 47263
neighbor 203.0.113.1 description AS47263 v4
neighbor 203.0.113.1 password <md5-optional>
!
address-family ipv4
neighbor 203.0.113.1 activate
maximum-prefix 200000 90 restart 5
exit-address-family
!
router bgp 65001
address-family ipv6
neighbor 2001:db8::1 remote-as 47263
neighbor 2001:db8::1 activate
maximum-prefix 200000 90 restart 5
exit-address-family
Use RFC5737 / 3849 example addresses above. Real peering IPs provided at turn-up.
policy-options {
policy-statement TRANSIT-OUT { then accept; }
}
protocols {
bgp {
group AS47263-v4 {
type external;
peer-as 47263;
neighbor 203.0.113.1;
family inet { unicast { prefix-limit maximum 200000 teardown 90; } }
authentication-key "<md5-optional>";
}
group AS47263-v6 {
type external;
peer-as 47263;
neighbor 2001:db8::1;
family inet6 { unicast { prefix-limit maximum 200000 teardown 90; } }
}
}
}
| Community | Action | Scope |
|---|---|---|
| 47263:100 | Increase LocalPref | AS47263 |
| 47263:200 | Decrease LocalPref | AS47263 |
| 47263:65000 | No-export | to peers/upstreams |
| 47263:666 | RTBH (IPv4) | network-wide |
| 47263:667 | RTBH (IPv6) | network-wide |
| 47263:999 | Blackhole /32 or /128 | with BH next-hop |
Full sheet provided with contract; IRR/RPKI validation required.
Capacity, ports, locations, SLA — send your requirements.
We issue LOA; you order the cross-connect with the DC.
We build filters, assign peering IPs, and schedule turn-up.
BGP comes up, routes verified, traffic migrates.
| Plan | Availability | Latency/Jitter | Response (NOC) | Extras |
|---|---|---|---|---|
| Advanced | on request | targets per POP | 24/7, defined | Runbooks, escalation |
| Premium | on request | stricter targets | 24/7, priority | Live logs, named contacts |
SLOs/KPIs aligned to your workload during scoping.
Yes. VLAN hand-off (802.1Q), QinQ on request. We can deliver L3 on top of private L2.
RTBH communities are available; Flowspec can be enabled for granular filtering.
GRE adds overhead (~24 bytes). We’ll agree an MTU to avoid fragmentation for your paths.
Depends on capacity/site. GRE can be same-day; cross-connects follow DC timelines.
Send your port speed, location(s), and billing model. We’ll reply with a tailored quote and LOA if needed.
Prefer direct email? sales@example.com