Observed topology
AS57455 FILANCO-LTD-UA Filanco LTD
Unclassified RIPE Route Server
Transit
Upstream networks
Networks observed carrying traffic for AS57455: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 125 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 10 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 3 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 3 |
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 3 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 2 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 2 |
| AS37100 | SEACOM Limited | Unclassified | IPv4 | 2 |
| AS1836 | green.ch AG | Residential | IPv6 | 1 |
| AS12859 | BIT BV | Hosting | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS57455 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51380 | FOP Kovalchuk Igor Vasilevich | Unclassified | IPv4 | 195 |
| AS61371 | Gigabit-Net Ltd. | Unclassified | IPv4 | 135 |
| AS43576 | LTD "KuMIR TELECOM" | Residential | IPv4 | 114 |
| AS34056 | Kyiv Optic Networks ltd | Residential | IPv4 | 102 |
| AS206907 | UAGROUP LLC | Residential | IPv4 | 96 |
| AS34251 | LLC IMC | Residential | IPv4 | 86 |
| AS42546 | UKRANIAN OPTICAL SYSTEMS AND TECHNOLOGIES LLC | Residential | IPv4 | 84 |
| AS34312 | FOP Boyko Oleg Mikhaylovich | Unclassified | IPv4 | 79 |
| AS39848 | CityLan LLC | Residential | IPv4 | 47 |
| AS59956 | PP "Lurenet" | Unclassified | IPv4 | 16 |
Adjacency
Adjacent networks
Every AS seen directly next to AS57455 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,581 |
| AS34251 | LLC IMC | Residential | IPv4 | 1,160 |
| AS34056 | Kyiv Optic Networks ltd | Residential | IPv4 | 998 |
| AS43576 | LTD "KuMIR TELECOM" | Residential | IPv4 | 770 |
| AS51380 | FOP Kovalchuk Igor Vasilevich | Unclassified | IPv4 | 227 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 178 |
| AS61371 | Gigabit-Net Ltd. | Unclassified | IPv4 | 135 |
| AS206907 | UAGROUP LLC | Residential | IPv4 | 134 |
| AS42546 | UKRANIAN OPTICAL SYSTEMS AND TECHNOLOGIES LLC | Residential | IPv4 | 84 |
| AS34312 | FOP Boyko Oleg Mikhaylovich | Unclassified | IPv4 | 79 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.