Observed topology
AS21738 ROZINT - Rozint
Residential ARIN Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS21738: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
Transit
Downstream networks
Networks for which AS21738 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS402247 | flew llc | Hosting | IPv4 IPv6 | 223 |
| AS6517 | LAKENETWORKS | Hosting | IPv4 IPv6 | 187 |
| AS401710 | CloudMesh Labs LLC | Unclassified | IPv4 IPv6 | 152 |
| AS53388 | Tefexia LC | Unclassified | IPv4 IPv6 | 130 |
| AS14923 | Graham Technology Solutions LLC | Unclassified | IPv4 IPv6 | 93 |
| AS151349 | Yuki Network Ltd | Hosting | IPv4 IPv6 | 86 |
| AS398549 | Zero Attack Vector LLC | Unclassified | IPv4 IPv6 | 76 |
| AS214430 | Takahiro Fukushima | Unclassified | IPv6 | 72 |
| AS200242 | Ember Ana Reimer | Unclassified | IPv6 | 68 |
| AS270142 | Castor Networks Mexico | Unclassified | IPv4 | 58 |
Adjacency
Adjacent networks
Every AS seen directly next to AS21738 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,511 |
| AS32097 | WholeSale Internet, Inc. | Hosting | IPv4 IPv6 | 902 |
| AS402247 | flew llc | Hosting | IPv4 IPv6 | 223 |
| AS6517 | LAKENETWORKS | Hosting | IPv4 IPv6 | 217 |
| AS401710 | CloudMesh Labs LLC | Unclassified | IPv4 IPv6 | 152 |
| AS151349 | Yuki Network Ltd | Hosting | IPv4 IPv6 | 139 |
| AS53388 | Tefexia LC | Unclassified | IPv4 IPv6 | 130 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 108 |
| AS14923 | Graham Technology Solutions LLC | Unclassified | IPv4 IPv6 | 93 |
| AS398549 | Zero Attack Vector LLC | Unclassified | IPv4 IPv6 | 76 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.