Loading…
The network's position in the inter-domain routing hierarchy: its customer cone, connectivity, and transit role.
Inferred AS-level relationships: 2 upstream providers, 2 peers and 8 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, Hong Kong SAR China).
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.
9 prefixes currently seen by RIPEstat.
2401:5a0:1001::/482602:fc1d:2::/48103.213.4.0/232602:fc1d:1::/482401:5a0:1000::/48208.99.48.0/242401:5a0:1002::/48103.213.5.0/24103.213.4.0/24