NETWORK
A network drawn for operators.
Fizp treats routing, handoff and observability as one operating system for connectivity.
Backbone principles
Routing is part of the product.
We publish the boundary, the handoff and the operational signals that matter to the teams running traffic.
Policy, filtering and announcements are explicit parts of delivery.
Port, flow, latency, loss and BGP events form one operational view.
Each facility and upstream path has a documented blast radius.
Upstreams and interconnects
Legible at the level you need.
Route policy
RPKI, IRR and communities are reviewed with the network team.
Interconnect
Public topology is shown only at the level approved for publication.
Events
Maintenance and network status are linked to a clear update path.
ROUTING CONTROLS
Signals that keep a path honest.
The network page should answer what is announced, what is filtered and what an operator can inspect before opening a ticket.
| Control | What it changes | What the operator reviews |
|---|---|---|
| RPKI / ROA | Validates origin authorization for announced prefixes. | Validity state, origin ASN, expiry. |
| IRR filters | Constrains accepted and propagated route objects. | AS-SET, route objects, review date. |
| BGP communities | Expresses local preference and propagation intent. | Community map, prepend and no-export behavior. |
| Blackhole / diversion | Defines the emergency traffic path for protected space. | Trigger, scope, escalation and rollback. |
OBSERVABILITY
Measure the path, not only the port.
Network status
Operations are part of the architecture.
Signal changes
Telemetry identifies a port, path or routing event.
Find boundary
Separate facility, upstream, customer and policy causes.
Share update
Maintenance or incident detail is linked to a timestamp.
Close loop
Capture the route, impact and next engineering action.