Observed topology
AS200019 ALEXHOST
Unclassified DROP-listed space RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS200019: 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 | 1,957 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,599 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 1,568 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 871 |
| AS8926 | Moldtelecom SA | Residential | IPv4 IPv6 | 633 |
| AS49434 | FBW NETWORKS SAS | Unclassified | IPv4 IPv6 | 468 |
| AS4849 | S3 Company Ltd | Hosting | IPv4 IPv6 | 443 |
| AS206170 | Yelles AB | Unclassified | IPv4 IPv6 | 405 |
| AS58453 | China Mobile International Limited | Unclassified | IPv4 IPv6 | 399 |
| AS53340 | VegasNAP, LLC | Hosting | IPv4 IPv6 | 234 |
Transit
Downstream networks
Networks for which AS200019 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48753 | AVA HOST SRL | Hosting | IPv4 IPv6 | 1,165 |
| AS201670 | S.C. INFOTECH-GRUP S.R.L. | Unclassified | IPv4 IPv6 | 279 |
| AS215290 | Bezhin Evgenii Alekseevich | Unclassified | IPv6 | 204 |
| AS205828 | Vyshegorodtseva Alla Alekseevna | Unclassified | IPv6 | 102 |
| AS207636 | ALEXHOST S.R.L. | Unclassified | IPv4 | 66 |
| AS204909 | Zimnitskaya Irina Nikolaevna | Unclassified | IPv6 | 35 |
Adjacency
Adjacent networks
Every AS seen directly next to AS200019 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,488 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 2,444 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 1,593 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 1,182 |
| AS48753 | AVA HOST SRL | Hosting | IPv4 IPv6 | 1,165 |
| AS8926 | Moldtelecom SA | Residential | IPv4 IPv6 | 864 |
| AS49434 | FBW NETWORKS SAS | Unclassified | IPv4 IPv6 | 468 |
| AS4849 | S3 Company Ltd | Hosting | IPv4 IPv6 | 443 |
| AS206170 | Yelles AB | Unclassified | IPv4 IPv6 | 405 |
| AS58453 | China Mobile International Limited | Unclassified | IPv4 IPv6 | 399 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.