FIZP TRANSIT IP
Internet transit with a route you can explain.
Fizp Transit IP gives operators, cloud platforms and high-volume services a policy-aware internet exit with explicit routing controls.
Specifications
Port options1G / 10G / 100G
RoutingFull or partial table · IPv4 / IPv6
Routing securityRPKI / IRR · BGP communities
Operating modelNOC, maintenance notice, SLA
Architecture
CUSTOMER
FIZP EDGE
Delivery process
Delivery process
01
Design route policy
Engineering confirms the next handoff before the following step begins.
02
Validate facility and port
Engineering confirms the next handoff before the following step begins.
03
Turn up BGP session
Engineering confirms the next handoff before the following step begins.
04
Observe and tune
Engineering confirms the next handoff before the following step begins.
Questions to take to engineering
Bring the right questions.
Which facility and port can we deliver?
Availability is confirmed per site, product and requested bandwidth.
What does the route look like under failure?
Ask for the approved topology, routing policy and escalation path.
What is included in the operating model?
Review monitoring, maintenance notice, NOC and SLA details with engineering.