Loading…
The network's position in the inter-domain routing hierarchy: its customer cone, connectivity, and transit role.
Inferred AS-level relationships: 3 upstream providers, 4 peers and 37 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, India).
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.
41 prefixes currently seen by RIPEstat.
2001:df4:88c0::/48160.19.35.0/2443.230.132.0/24103.162.74.0/24103.109.223.0/24103.172.56.0/24103.109.221.0/242001:df2:23c0::/48103.110.245.0/24103.147.93.0/2443.228.167.0/24103.225.70.0/24160.191.125.0/24103.162.75.0/24103.157.163.0/242001:df3:29c0::/48160.191.124.0/242401:19a0::/32103.110.244.0/24103.239.13.0/24103.239.12.0/2438.196.187.0/2443.230.133.0/24103.109.222.0/242001:978:b00::/4843.228.166.0/24103.115.131.0/24165.99.142.0/242401:a8a0::/322001:df2:9640::/48160.187.207.0/24154.22.138.0/24103.216.99.0/24103.155.207.0/24103.157.162.0/24165.99.143.0/242001:df5:9cc0::/4838.196.186.0/24103.109.220.0/24103.115.128.0/24151.158.178.0/24