The network's position in the inter-domain routing hierarchy: its customer cone, connectivity, and transit role.
Inferred AS-level relationships: 3 upstream providers, 1 peers and 2 downstream customers. The graph shows the largest few of each; the lists link through.
give this network transit
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, Argentina).
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.
44 prefixes currently seen by RIPEstat.
200.89.9.0/24200.85.236.0/22200.47.173.0/242800:1d0::/3245.162.0.0/24200.85.232.0/22200.47.157.0/24200.47.171.0/24200.47.176.0/24201.220.37.0/24200.89.7.0/24200.47.217.0/24200.89.14.0/24200.89.8.0/242800:24::/32200.47.170.0/24200.89.13.0/24200.47.216.0/24200.89.11.0/24200.85.245.0/24200.47.219.0/24200.85.248.0/22200.47.156.0/24201.220.57.0/24200.85.244.0/24200.89.10.0/24200.85.229.0/24201.220.36.0/22200.47.177.0/24200.85.244.0/22201.220.48.0/20201.220.34.0/24200.47.172.0/24200.85.228.0/22200.85.243.0/24200.47.158.0/24200.47.175.0/24201.220.32.0/22201.220.33.0/24200.85.224.0/22200.89.6.0/24200.85.252.0/22200.85.241.0/24201.220.44.0/22