Loading…
The network's position in the inter-domain routing hierarchy: its customer cone, connectivity, and transit role.
Inferred AS-level relationships: 1 upstream providers, 0 peers and 0 downstream customers. The graph shows the largest few of each; the lists link through.
exchange traffic directly
None recorded.
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, Bangladesh).
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.
47 prefixes currently seen by RIPEstat.
2400:3dc0:5f::/482400:3dc0:51::/482400:3dc0:42::/482400:3dc0:62::/482400:3dc0:4f::/482400:3dc0:41::/482400:3dc0:73::/482400:3dc0:67::/482400:3dc0:6e::/482400:3dc0:59::/482400:3dc0:53::/482400:3dc0:82::/482400:3dc0:55::/482400:3dc0:5d::/482400:3dc0:52::/482400:3dc0:90::/482400:3dc0:4e::/48165.101.13.0/242400:3dc0:96::/482400:3dc0:74::/482400:3dc0:79::/482400:3dc0:91::/482400:3dc0:5e::/482400:3dc0:4d::/482400:3dc0:72::/482400:3dc0:65::/482400:3dc0:97::/482400:3dc0:6b::/482400:3dc0:5c::/482400:3dc0:77::/482400:3dc0:47::/482400:3dc0:76::/482400:3dc0:54::/482400:3dc0:48::/482400:3dc0:63::/482400:3dc0:92::/482400:3dc0:93::/482400:3dc0:6d::/482400:3dc0:56::/482400:3dc0:94::/482400:3dc0:75::/482400:3dc0:64::/482400:3dc0:4a::/482400:3dc0:95::/482400:3dc0:7a::/482400:3dc0:81::/482400:3dc0:50::/48