Observed topology
AS41820 NOVI-AS
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS41820: 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 |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 610 |
| AS6663 | Euroweb Romania S.R.L. | Unclassified | IPv4 IPv6 | 501 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 378 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 212 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 83 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 34 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 33 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 28 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 28 |
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 28 |
Transit
Downstream networks
Networks for which AS41820 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34204 | Michail Mandryk | Unclassified | IPv4 | 240 |
| AS39043 | PP Info-Center | Unclassified | IPv4 | 240 |
| AS207558 | Sergey Kus | Unclassified | IPv4 IPv6 | 226 |
| AS39307 | Yankovich Yaroslav Yosifovych | Unclassified | IPv4 | 219 |
| AS56622 | DVS-Sat LLC | Unclassified | IPv4 | 120 |
| AS210490 | FOP Matishynets Serhii | Unclassified | IPv4 IPv6 | 93 |
| AS31234 | KRAM Ltd | Unclassified | IPv4 | 66 |
| AS35800 | TV Optimum Ltd. | Unclassified | IPv4 | 61 |
| AS25482 | Private Enterprise "Law Firm "Status" | Unclassified | IPv4 | 60 |
| AS41513 | PP SkyTeleNet | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS41820 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,064 |
| AS6663 | Euroweb Romania S.R.L. | Unclassified | IPv4 IPv6 | 877 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 703 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 367 |
| AS34204 | Michail Mandryk | Unclassified | IPv4 | 300 |
| AS39043 | PP Info-Center | Unclassified | IPv4 | 240 |
| AS207558 | Sergey Kus | Unclassified | IPv4 IPv6 | 226 |
| AS39307 | Yankovich Yaroslav Yosifovych | Unclassified | IPv4 | 219 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 173 |
| AS56622 | DVS-Sat LLC | Unclassified | IPv4 | 120 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.