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: 3 upstream providers, 122 peers and 30 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, Mexico).
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.
2806:319::/482806:319:2::/482806:319:10::/482806:319:1::/482806:319:3::/482806:319:4000::/36170.78.209.0/2469.171.215.0/242806:319:26::/482806:319:f000::/362806:3c7:2000::/3645.168.237.0/2445.168.238.0/24170.78.210.0/2438.65.174.0/2469.171.212.0/242806:319:4::/4882.152.138.0/242806:319:3000::/3645.177.179.0/2482.152.139.0/242806:319:400::/382806:319:a::/482806:3c7:1000::/3645.168.236.0/242806:3c7::/3638.65.175.0/2469.171.213.0/2445.177.178.0/242806:319:32::/4845.168.239.0/2482.152.133.0/2482.153.2.0/242806:319:9::/48170.78.211.0/24170.78.208.0/2482.153.3.0/24