Loading…
Where this network meets others — public exchange points, colocation facilities, and declared peering capacity.
The network's position in the inter-domain routing hierarchy: its customer cone, connectivity, and transit role.
Inferred AS-level relationships: 5 upstream providers, 8 peers and 25 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, Taiwan).
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.
2a13:a5c3:3200::/402a13:a5c3:2800::/382a13:a5c3:4100::/412a13:a5c3:4340::/422a13:a5c3:2200::/412a13:a5c3:2800::/402a13:a5c3:2500::/412a13:a5c3:2000::/372a13:a5c3:4240::/422406:840:e27f::/482a13:a5c3:2100::/402a13:a5c3:3000::/362a13:a5c3:3130::/442a13:a5c3:4300::/4223.149.120.0/242a13:a5c3:42c0::/422a13:a5c3:3300::/4044.32.154.0/242406:840:e270::/482a13:a5c3:3080::/412a13:a5c3:3100::/4023.175.24.0/232602:f9f6:e00::/402a13:a5c3:32e0::/442a13:a5c3:3130::/482a13:a5c3:1000::/412a13:a5c3:d000::/362a13:a5c3:4000::/362a13:a5c3:4380::/422a13:a5c3:4000::/4023.175.25.0/242a13:a5c3:3000::/412a13:a5c3:4180::/412a13:a5c3:2900::/402602:f9f6::/402a13:a5c3:2000::/402a13:a5c3:4240::/44