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: 1 upstream providers, 3 peers and 0 downstream customers. The graph shows the largest few of each; the lists link through.
exchange traffic directly
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, United States).
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.
44 prefixes currently seen by RIPEstat.
2602:fd37:302::/48151.244.214.0/242602:fd37:313::/48170.39.20.0/24144.225.247.0/242602:fd37:30a::/482602:fd37:308::/482602:fd37:303::/48169.128.159.0/24108.186.51.0/242602:fd37:300::/482602:fd37:307::/482602:fd37:309::/48169.128.158.0/2469.176.84.0/242602:fd37::/4823.161.112.0/242602:fd37:301::/48107.149.33.0/242602:fd37:305::/48166.88.232.0/242602:fd37:400::/4074.117.196.0/22144.225.246.0/242602:fd37:316::/482602:fd37:500::/4023.185.72.0/242602:fd37:314::/482602:fd37:100::/402602:fd37:312::/48204.197.160.0/222602:fd37:304::/482602:fd37:200::/402602:fd37:310::/482602:fd37:311::/482602:fd37:2::/482602:fd37:fff::/482602:fd37:4::/48108.186.146.0/24144.225.246.0/232602:fd37:1::/482602:fd37:315::/48104.250.236.0/222602:fd37:306::/48