Observed topology
AS215730 H2NEXUS-AS
Unclassified Spamhaus ASN-DROP RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS215730: 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 AS215730 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS201988 | VPSPay Networks LTD | Unclassified | IPv4 IPv6 | 998 |
| AS218731 | Andris Jakovlevs | Unclassified | IPv4 IPv6 | 771 |
| AS202226 | Emil Vitukhnovskii trading as Great Flower | Unclassified | IPv4 | 680 |
| AS200823 | MHost LLC | Unclassified | IPv4 IPv6 | 166 |
| AS219443 | Ints Danebergs | Unclassified | IPv4 IPv6 | 137 |
| AS219336 | Olha Popsuiko | Unclassified | IPv4 IPv6 | 97 |
| AS199277 | Maksims Doronkins | Unclassified | IPv6 | 64 |
| AS205563 | Marc Gomez | Unclassified | IPv6 | 64 |
| AS201269 | Ivans Lavrentjevs | Hosting | IPv4 | 60 |
| AS201861 | Aleksejs Pinajevs | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS215730 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS30823 | aurologic GmbH | Hosting | IPv4 IPv6 | 2,369 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,018 |
| AS201988 | VPSPay Networks LTD | Unclassified | IPv4 IPv6 | 1,248 |
| AS203446 | SMARTNET Germany GmbH | Unclassified | IPv4 IPv6 | 1,084 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 1,021 |
| AS218731 | Andris Jakovlevs | Unclassified | IPv4 IPv6 | 771 |
| AS202226 | Emil Vitukhnovskii trading as Great Flower | Unclassified | IPv4 | 680 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 IPv6 | 237 |
| AS200823 | MHost LLC | Unclassified | IPv4 IPv6 | 166 |
| AS219443 | Ints Danebergs | Unclassified | IPv4 IPv6 | 137 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.94M 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.