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, 15 peers and 0 downstream customers. The graph shows the largest few of each; the lists link through.
exchange traffic directly
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.
17 prefixes currently seen by RIPEstat.
2a02:2278:ffff::/48185.158.209.0/242a02:2278:ff00::/402a02:2278:fffd::/482a02:2278:fffe::/48185.158.208.0/22185.158.211.0/242a02:2278:fffb::/48195.234.112.0/24195.234.113.0/24185.158.208.0/242a02:2278:fffa::/48195.234.114.0/2491.223.19.0/242a02:2278:fffc::/48195.234.112.0/22185.158.210.0/24