Observed topology
AS48729 HOSTKEY-FI-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48729: 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 |
|---|---|---|---|---|
| AS57043 | HOSTKEY B.V. | Hosting | IPv4 IPv6 | 416 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 192 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 186 |
| AS395839 | HOSTKEY | Unclassified | IPv4 | 116 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 67 |
| AS49559 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 23 |
| AS202580 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 9 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 8 |
Transit
Downstream networks
Networks for which AS48729 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS41745 | Baykov Ilya Sergeevich | Unclassified | IPv4 IPv6 | 3,649 |
| AS216475 | NKtelecom INC | Unclassified | IPv4 IPv6 | 1,149 |
| AS215305 | Mastersoft S.R.L. | Unclassified | IPv4 | 638 |
| AS214798 | Digital City FZE | Unclassified | IPv4 IPv6 | 614 |
| AS198178 | 365.partners INC | Unclassified | IPv4 IPv6 | 324 |
| AS216129 | SEBEK sp. z o.o | Unclassified | IPv4 IPv6 | 301 |
| AS207461 | HOSTING INDUSTRY LIMITED | Unclassified | IPv4 IPv6 | 151 |
| AS216139 | Iron Hosting Centre LTD | Hosting | IPv4 | 82 |
| AS208112 | ROMAN EMPIRE BV | Hosting | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48729 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57043 | HOSTKEY B.V. | Hosting | IPv4 IPv6 | 5,241 |
| AS41745 | Baykov Ilya Sergeevich | Unclassified | IPv4 IPv6 | 3,649 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 1,469 |
| AS216475 | NKtelecom INC | Unclassified | IPv4 IPv6 | 1,149 |
| AS215305 | Mastersoft S.R.L. | Unclassified | IPv4 | 638 |
| AS214798 | Digital City FZE | Unclassified | IPv4 IPv6 | 614 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 484 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 358 |
| AS198178 | 365.partners INC | Unclassified | IPv4 IPv6 | 324 |
| AS216129 | SEBEK sp. z o.o | Unclassified | IPv4 IPv6 | 301 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.