Observed topology
AS397373 H4Y-TECHNOLOGIES - H4Y Technologies LLC
Hosting DROP-listed space APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS397373: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,469 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,784 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,311 |
| AS40676 | Psychz Networks | Hosting | IPv4 IPv6 | 739 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 728 |
| AS53340 | VegasNAP, LLC | Hosting | IPv4 IPv6 | 612 |
| AS14935 | Monticello Networks, Inc. | Hosting | IPv4 IPv6 | 106 |
| AS17216 | DC74 LLC | Hosting | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS397373 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS399122 | VPS House Technology Group LLC | Unclassified | IPv4 IPv6 | 901 |
| AS199856 | Ping Technology Labs LTD | Unclassified | IPv4 IPv6 | 288 |
| AS39798 | MivoCloud SRL | Hosting | IPv4 IPv6 | 243 |
| AS55082 | WINK Streaming LLC | Unclassified | IPv4 | 192 |
| AS399114 | Hyonix | Hosting | IPv4 | 185 |
| AS137571 | arebz.com | Unclassified | IPv4 | 177 |
| AS215286 | IXROOT LTD | Unclassified | IPv4 | 118 |
| AS14935 | Monticello Networks, Inc. | Hosting | IPv4 IPv6 | 66 |
Adjacency
Adjacent networks
Every AS seen directly next to AS397373 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 5,040 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 4,812 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,724 |
| AS399122 | VPS House Technology Group LLC | Unclassified | IPv4 IPv6 | 901 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 811 |
| AS40676 | Psychz Networks | Hosting | IPv4 IPv6 | 739 |
| AS53340 | VegasNAP, LLC | Hosting | IPv4 IPv6 | 676 |
| AS199856 | Ping Technology Labs LTD | Unclassified | IPv4 IPv6 | 288 |
| AS39798 | MivoCloud SRL | Hosting | IPv4 IPv6 | 243 |
| AS55082 | WINK Streaming LLC | Unclassified | IPv4 | 192 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.