Observed topology
AS34251 IMC-AS
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS34251: 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 |
|---|---|---|---|---|
| AS35297 | Dataline LLC | Unclassified | IPv4 | 496 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 162 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 141 |
| AS57455 | Filanco Ukraine Ltd. | Unclassified | IPv4 | 86 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 40 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 39 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 28 |
| AS24482 | SG.GS | Hosting | IPv4 | 9 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 | 5 |
Transit
Downstream networks
Networks for which AS34251 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS44827 | Bravoport Ltd | Unclassified | IPv4 | 814 |
| AS31158 | Asgard LLC | Unclassified | IPv4 | 279 |
| AS198720 | MOBICOM Ltd. | Unclassified | IPv4 | 168 |
| AS42556 | TOV "AirPort" | Unclassified | IPv4 | 125 |
| AS25174 | Osokorky Online LLC | Unclassified | IPv4 | 110 |
| AS29496 | Link-Service Ltd. | Unclassified | IPv4 | 70 |
| AS8461 | Astelnet LLC | Unclassified | IPv4 | 13 |
| AS24593 | Astelnet LLC | Unclassified | IPv4 | 3 |
Adjacency
Adjacent networks
Every AS seen directly next to AS34251 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57455 | Filanco Ukraine Ltd. | Unclassified | IPv4 | 1,132 |
| AS44827 | Bravoport Ltd | Unclassified | IPv4 | 814 |
| AS35297 | Dataline LLC | Unclassified | IPv4 | 515 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 281 |
| AS31158 | Asgard LLC | Unclassified | IPv4 | 279 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 269 |
| AS3255 | LLC EKSINTECH | Unclassified | IPv4 | 189 |
| AS198720 | MOBICOM Ltd. | Unclassified | IPv4 | 168 |
| AS42556 | TOV "AirPort" | Unclassified | IPv4 | 125 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 111 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-23 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.15M 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.