Infrastructure Map & Network Topology — d3 force-directed AS graph + Leaflet geo
The Infrastructure Map answers two completely different questions on one screen. Where is the network physically — datacentres, IXP halls, transit POPs, cross-connect terminations? And how is the network topologically — which AS connects to which, via which provider, with what relationship (customer / peer / provider) and what backup path? The geographic view runs on Leaflet with three layers — Infrastructure, GeoIP traffic heatmap and Live flow arcs. The topology view runs on a d3 force-directed graph fed by CAIDA AS-Relationships data plus an IGP + EGP overlay built from live BGP-LS (RFC 7752) and ISIS/OSPF flooding state.
Core routers (Juniper MX, Huawei NE8000) and IXP edge routers (3× MikroTik CCR2004 at SwissIX, MIX-IT, MINAP) appear as nodes with vendor logos, link-state visualised by edge colour and width. Coordinates default to PeeringDB facility data, with GeoIP fallback for entries not present in PeeringDB. An exclusive-IXP-prefix metric shows which prefixes are reachable only via an IXP peer (and not via any transit) — the single best indicator of peering value, and the metric peering managers use to justify renewals. Router vendor detection via SNMP sysDescr identifies Juniper / Huawei / MikroTik for badge rendering, and per-router stats (status dot, vendor badge, IPv4/IPv6 protocol, model, uptime via SNMP sysUpTime, peer count, prefix count) sit alongside the map for instant context.
d3 force-directed AS topology graph
A live d3-force simulation positions every directly-connected AS as a node, edges coloured by CAIDA-classified relationship (customer / peer / provider / sibling). Hovering any node surfaces the AS name, country, PeeringDB facility presence, prefix count, and whether traffic is currently observed — clicking jumps to the per-AS detail page. The same graph supports a 2-hop expansion view that pulls in the next ring of ASes from RIB AS-path data, useful for understanding how a peering choice changes effective reach.
IGP + EGP link-state overlay (BGP-LS, RFC 7752)
BGP Link-State (RFC 7752) is consumed on the same BMP collector port that drives the rest of RoutePulse; the resulting IGP topology (ISIS / OSPF / OSPFv3) is overlaid on the AS-level graph so the operator sees both the eBGP map and the intra-AS link-state at once. Link metrics, SRLG groups, and TE attributes are surfaced when present. This is the same data plane used by traffic-engineering tools — exposed here in a read-only, operator-friendly visualisation.
3 Leaflet geographic layers — Infrastructure · GeoIP heatmap · Live arcs
The Infrastructure layer plots core routers (blue markers) and IXP presences (green markers) with peer-status indicators and interconnection lines. The GeoIP traffic layer renders a city-level MaxMind GeoIP2 Commercial heatmap with country breakdown tables and individual host markers. The Live flow layer animates great-circle arcs of currently-active flows on a world map with pulsing source/destination markers — the same 50-flows/2 s Socket.io stream powering the Flow Analyzer’s Geo Map tab. All three layers refresh every 10 s for a live operational picture.
Key Capabilities
- d3 force-directed AS topology graph — nodes per directly-connected AS, edges coloured by CAIDA-classified relationship (customer / peer / provider / sibling)
- CAIDA AS-Relationships dataset — refreshed monthly, applied to every BGP peer for accurate relationship inference
- BGP Link-State overlay (RFC 7752) — IGP topology (ISIS / OSPF / OSPFv3) consumed on the BMP collector, rendered alongside eBGP graph
- 3 Leaflet geographic layers — Infrastructure topology (blue/green markers), GeoIP traffic heatmap (city-level MaxMind), Live flow great-circle arcs
- Coordinates from PeeringDB facility data with GeoIP fallback (GeoIP2 Commercial City dataset, 117 MB) for entries not registered in PeeringDB
- Exclusive-IXP-prefix metric — counts prefixes reachable only via IXP peers and not via transit; the canonical “is this IXP worth keeping?” KPI
- SNMP
sysDescrvendor detection — Juniper / Huawei / MikroTik logos rendered automatically on each router node - Per-router stats panel — status dot, vendor badge, IPv4/IPv6 protocol, model, uptime (SNMP
sysUpTime), peer count, prefix count - 5 routers in current deployment — 2 core (Juniper MX 40 Gbps + Huawei NE8000 40 Gbps) + 3 IXP edge (CCR2004 at SwissIX / MIX-IT / MINAP, 10 Gbps each)
- Live flow arcs — 50 flows / 2 s Socket.io stream from in-memory buffer; great-circle math via d3-geo, pulsing endpoint markers
- Weathermap cross-link for utilisation overlays; one-click jump from any node to its detail page (per-AS, per-router, per-peer)
- 10-second auto-refresh on every layer — live operational picture without manual reload
Engineered and operated by the GOLINE SOC & Network Engineering team.
Explore all RoutePulse features →