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.
14 prefixes currently seen by RIPEstat.
2a01:aea0:df4::/48188.172.199.0/24185.50.234.0/24144.208.192.0/222a01:aea0:dd5::/48144.208.192.0/212a01:aea0:101::/482a01:aea0:100::/482a01:aea0:df5::/48144.208.200.0/222a01:aea0:102::/482a01:aea0:df3::/482a01:aea0:dd4::/482a01:aea0:dd3::/48