Observed topology
AS47169 HPC-MVM-AS Pro-M Zrt.
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS47169: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,355 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 445 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 317 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 66 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 24 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 8 |
| AS12301 | One Hungary Ltd. | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS47169 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS42232 | PARISAT Tavkozlesi es Szolgaltato Korlatolt Felelossegu Tarsasag | Unclassified | IPv4 | 595 |
| AS54253 | Oracle Corporation | Unclassified | IPv4 IPv6 | 548 |
| AS1955 | KIFU (Governmental Info Tech Development Agency) | Unclassified | IPv4 IPv6 | 272 |
| AS210114 | HungaroControl Pte.Ltd.Co. | Unclassified | IPv4 | 245 |
| AS43928 | MVM Information Technology Private Company Limited by Shares | Unclassified | IPv4 IPv6 | 191 |
| AS31297 | Axian Kft. | Unclassified | IPv4 | 149 |
| AS200076 | Klapka Gyorgy Lakasfenntarto Szovetkezet | Unclassified | IPv4 IPv6 | 149 |
| AS51438 | Boly Varos Onkormanyzat | Unclassified | IPv4 IPv6 | 148 |
| AS197523 | DV Info Informatikai kft. | Unclassified | IPv4 | 116 |
| AS25539 | Hungarian Power System Operator Co. | Unclassified | IPv4 | 58 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47169 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,925 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 952 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 737 |
| AS42232 | PARISAT Tavkozlesi es Szolgaltato Korlatolt Felelossegu Tarsasag | Unclassified | IPv4 | 597 |
| AS54253 | Oracle Corporation | Unclassified | IPv4 IPv6 | 548 |
| AS1955 | KIFU (Governmental Info Tech Development Agency) | Unclassified | IPv4 IPv6 | 407 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 354 |
| AS210114 | HungaroControl Pte.Ltd.Co. | Unclassified | IPv4 | 245 |
| AS43928 | MVM Information Technology Private Company Limited by Shares | Unclassified | IPv4 IPv6 | 191 |
| AS31297 | Axian Kft. | Unclassified | IPv4 | 149 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.