asn.dev

Observed topology

AS57455 Filanco-LTD-UA Filanco Ukraine Ltd.

Unclassified RIPE

Upstreams 2 carry this network
Downstreams 9 this network carries
Adjacent (IPv4) 21
Adjacent (IPv6) 0
Upstream graph Who carries AS57455, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS57455 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4128
AS24482SG.GSHostingIPv42

Transit

Downstream networks

inferred

Networks for which AS57455 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS61371Gigabit-Net Ltd.UnclassifiedIPv4141
AS51380FOP Kovalchuk Igor VasilevichUnclassifiedIPv4135
AS43576LTD "KuMIR TELECOM"ResidentialIPv4120
AS34251LLC IMCResidentialIPv492
AS34056Kyiv Optic Networks ltdResidentialIPv490
AS206907UAGROUP LLCResidentialIPv490
AS42546UKRANIAN OPTICAL SYSTEMS AND TECHNOLOGIES LLCResidentialIPv484
AS34312FOP Boyko Oleg MikhaylovichUnclassifiedIPv482
AS39848CityLan LLCResidentialIPv445

Adjacency

Adjacent networks

All 21

Every AS seen directly next to AS57455 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv46,935
AS199995Omega Telecom LLCResidentialIPv43,336
AS34251LLC IMCResidentialIPv41,145
AS34056Kyiv Optic Networks ltdResidentialIPv4916
AS43576LTD "KuMIR TELECOM"ResidentialIPv4796
AS44863STARNET TC LLCUnclassifiedIPv4256
AS51380FOP Kovalchuk Igor VasilevichUnclassifiedIPv4156
AS61371Gigabit-Net Ltd.UnclassifiedIPv4141
AS34549meerfarbig GmbH & Co. KGHostingIPv4132
AS206907UAGROUP LLCResidentialIPv4131

All 21 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.