asn.dev

Observed topology

AS57277 LLC Zero Kilometer

Unclassified RIPE

Upstreams 0 carry this network
Downstreams 11 this network carries
Adjacent (IPv4) 22
Adjacent (IPv6) 7
Upstream graph Who carries AS57277, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS57277 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57277: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS5547JSC Orient-TelecomResidentialIPv41,237
AS47909BAIKAL TELECOM LLCUnclassifiedIPv4 IPv6544
AS59616Baikal Teleport LtdUnclassifiedIPv4324
AS42971INTERFONICA LLCUnclassifiedIPv4 IPv6244
AS61406Zavod RTA Ltd.UnclassifiedIPv4189
AS201135Dream Net LtdUnclassifiedIPv4186
AS57737Joint Stock Company Angarsk Electrolysis Chemical ComplexUnclassifiedIPv4185
AS21087Electronniy gorod, Ltd.UnclassifiedIPv4183
AS48586LLC Zero KilometerUnclassifiedIPv4 IPv696
AS58304NPF KTS Ltd.UnclassifiedIPv462

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv62,449
AS5547JSC Orient-TelecomResidentialIPv41,299
AS47909BAIKAL TELECOM LLCUnclassifiedIPv4 IPv6726
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6643
AS59616Baikal Teleport LtdUnclassifiedIPv4324
AS42971INTERFONICA LLCUnclassifiedIPv4 IPv6245
AS61406Zavod RTA Ltd.UnclassifiedIPv4189
AS201135Dream Net LtdUnclassifiedIPv4186
AS57737Joint Stock Company Angarsk Electrolysis Chemical ComplexUnclassifiedIPv4185
AS21087Electronniy gorod, Ltd.UnclassifiedIPv4183

Provenance

Where this comes from

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