Loading…
The network's position in the inter-domain routing hierarchy: its customer cone, connectivity, and transit role.
Inferred AS-level relationships: 4 upstream providers, 2 peers and 6 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.
37 prefixes currently seen by RIPEstat.
144.79.158.0/242001:df0:82c0::/48103.167.130.0/24103.55.214.0/24103.102.28.0/24103.168.249.0/24103.55.215.0/24103.174.34.0/242001:df0:e140::/48103.171.201.0/24103.102.30.0/24103.147.121.0/24103.103.91.0/24103.103.90.0/24103.183.25.0/24103.102.31.0/24103.144.65.0/24103.168.248.0/2445.248.17.0/24103.190.14.0/24103.147.120.0/24103.190.15.0/24103.183.24.0/24103.112.121.0/24103.148.63.0/24103.102.29.0/24103.171.200.0/24103.148.62.0/24103.174.35.0/24144.79.159.0/24103.144.64.0/242400:9820::/3245.248.16.0/242402:4120::/32103.167.131.0/24103.124.109.0/242001:df1:25c0::/48