Loading…
The network's position in the inter-domain routing hierarchy: its customer cone, connectivity, and transit role.
Inferred AS-level relationships: 1 upstream providers, 0 peers and 0 downstream customers. The graph shows the largest few of each; the lists link through.
exchange traffic directly
None recorded.
buy transit from it
None recorded.
Relationships are inferred from BGP by CAIDA and refreshed monthly. Transit links are well captured; some private and IXP peering is under-observed, so peer counts are a lower bound.
How well this network secures and documents its BGP announcements — RPKI origin validation, IRR registration, and an overall hygiene score.
Currently announced prefixes, live from RIPEstat.
Invalid announcements have a ROA on file but the origin AS or prefix length doesn't match it — usually a stale ROA or misconfiguration rather than an active hijack.
12 prefixes currently seen by RIPEstat.
2a0f:1cc5:f01::/482a0f:1cc5:f06::/482602:f92a:a47d::/482a0f:1cc5:f09::/482a0f:1cc5:fff::/482a0f:1cc5:f03::/482a0f:1cc5:f02::/48193.233.49.0/242406:840:9178::/482a0f:1cc5:f04::/482a0f:1cc5:f05::/482a0f:1cc5:f07::/48