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.
Measured share of this network's users reaching the Internet over IPv6 (APNIC end-user measurement, Peru).
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.
148.102.16.0/20186.160.60.0/22148.102.73.0/24200.110.12.0/22190.187.176.0/20190.187.128.0/20148.102.112.0/20148.102.96.0/20190.187.160.0/20200.110.26.0/24190.187.0.0/20190.187.64.0/20186.160.72.0/22148.102.48.0/20200.110.25.0/24148.102.72.0/24190.187.208.0/20186.160.88.0/22200.110.40.0/22190.187.48.0/20148.102.32.0/20190.187.192.0/20200.110.20.0/22190.187.224.0/20190.187.112.0/20148.102.80.0/20200.31.112.0/20190.187.32.0/20148.102.0.0/20190.187.80.0/20148.102.64.0/20148.102.71.0/24200.110.27.0/24190.8.128.0/20200.110.16.0/22190.187.240.0/20200.110.36.0/24190.187.96.0/20200.31.96.0/20190.187.16.0/20200.110.32.0/22190.8.144.0/20190.187.144.0/20200.110.44.0/22