Observed topology
AS204490 ASKONTEL Kontel LLC
Unclassified Spamhaus ASN-DROP RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS204490: 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 |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 1,764 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 1,405 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 394 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 40 |
| AS59796 | StormWall s.r.o. | Unclassified | IPv4 | 20 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS204490 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS206766 | Travchis LLC | Unclassified | IPv4 | 264 |
| AS205866 | Vyshegorodtsev Roman Valerevich | Unclassified | IPv6 | 210 |
| AS215330 | Chernenko Denis Evgenevich | Unclassified | IPv6 | 175 |
| AS208360 | Pushkarev Nikolai Aleksandrovich | Unclassified | IPv6 | 144 |
| AS204909 | Zimnitskaya Irina Nikolaevna | Unclassified | IPv6 | 140 |
| AS204968 | Volkov Andrey Vladimirovich | Unclassified | IPv6 | 36 |
| AS213294 | Shestavina Alevtina Vitalevna | Unclassified | IPv6 | 35 |
Adjacency
Adjacent networks
Every AS seen directly next to AS204490 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 2,558 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 1,417 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 592 |
| AS206766 | Travchis LLC | Unclassified | IPv4 | 264 |
| AS205866 | Vyshegorodtsev Roman Valerevich | Unclassified | IPv6 | 210 |
| AS215330 | Chernenko Denis Evgenevich | Unclassified | IPv6 | 175 |
| AS208360 | Pushkarev Nikolai Aleksandrovich | Unclassified | IPv6 | 144 |
| AS204909 | Zimnitskaya Irina Nikolaevna | Unclassified | IPv6 | 140 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 40 |
| AS204968 | Volkov Andrey Vladimirovich | Unclassified | IPv6 | 36 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M 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.