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, 0 peers and 5 downstream customers. The graph shows the largest few of each; the lists link through.
give this network transit
exchange traffic directly
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, Vietnam).
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.
45 prefixes currently seen by RIPEstat.
103.173.67.0/24160.30.50.0/23157.66.224.0/23103.173.66.0/23160.191.160.0/24160.250.128.0/23160.250.186.0/23160.250.4.0/23163.61.72.0/24160.22.81.0/24160.191.86.0/23103.67.162.0/23163.61.72.0/23163.223.210.0/23103.116.53.0/242401:37e0::/48160.22.80.0/2436.50.27.0/24160.22.120.0/23103.72.56.0/23160.30.136.0/23103.173.66.0/24161.248.178.0/23160.250.132.0/23103.152.165.0/24157.66.48.0/23103.78.2.0/23161.248.238.0/23157.66.222.0/23161.248.4.0/23163.227.230.0/23160.250.180.0/23103.116.52.0/24103.152.164.0/23160.191.214.0/23163.61.73.0/24160.25.72.0/23103.152.164.0/24103.75.76.0/2336.50.26.0/24103.20.103.0/242401:2be0::/48103.161.172.0/24103.20.102.0/24103.77.208.0/23