Loading…
The network's position in the inter-domain routing hierarchy: its customer cone, connectivity, and transit role.
Inferred AS-level relationships: 6 upstream providers, 29 peers and 2 downstream customers. The graph shows the largest few of each; the lists link through.
give this network transit
exchange traffic directly
buy transit from it
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.
Measured share of this network's users reaching the Internet over IPv6 (APNIC end-user measurement, Netherlands).
Has working IPv6 connectivity, even if it isn't always chosen.
IPv6 wins when a destination is dual-stacked — the real-world usage rate.
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.
42 prefixes currently seen by RIPEstat.
150.40.118.0/24150.40.103.0/2477.242.152.0/242a0e:bfc1::/32150.40.105.0/24150.40.124.0/24150.40.119.0/2445.95.169.0/24102.206.51.0/24150.40.96.0/242a0e:bfc3::/32150.40.104.0/24150.40.107.0/242a0e:bfc7:300::/40150.40.126.0/242a0e:bfc6::/32150.40.98.0/2445.95.170.0/242a0e:bfc7:1000::/38150.40.115.0/24102.206.48.0/2445.9.156.0/242a0e:bfc2::/32150.40.113.0/24150.40.114.0/24150.40.108.0/2445.9.168.0/242a0e:bfc4::/32102.206.49.0/24150.40.125.0/242a0e:bfc0::/32150.40.102.0/24150.40.106.0/242a0e:bfc5::/32150.40.121.0/24150.40.127.0/242a0e:bfc7::/4045.95.168.0/242a0e:bfc7:100::/40150.40.101.0/24102.206.50.0/24150.40.123.0/24