asn.dev

Observed topology

AS31257 ORIONNET-KRK Orion Telecom LLC

Residential APNIC

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS31257: 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
AS12389PJSC RostelecomResidentialIPv41,422
AS31133PJSC MegaFonMobileIPv41,116
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6759
AS31500Global Network Management IncUnclassifiedIPv4188
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv4124
AS50673Serverius Holding B.V.UnclassifiedIPv488
AS49673Truenetwork LLCUnclassifiedIPv466
AS37721Virtual Technologies & SolutionsResidentialIPv464
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv464
AS8447A1 Telekom Austria AGResidentialIPv460

Transit

Downstream networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS208221Orion telecom ltdUnclassifiedIPv4520
AS59696Municipality of Krasnoyarsk CityUnclassifiedIPv465
AS6098045KA LLC.UnclassifiedIPv465
AS201970LLC Komandor-HoldingUnclassifiedIPv465
AS209867LLC Security Agency "Scorpion"UnclassifiedIPv465
AS204137Orion telecom ltdResidentialIPv4 IPv657
AS201786OOO ComLineResidentialIPv451
AS58351IE Dudin Dmitriy ViktorovichUnclassifiedIPv450
AS60575LTD SibServisSvyazUnclassifiedIPv438
AS50427Orion Telecom LLCResidentialIPv426

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv41,777
AS31133PJSC MegaFonMobileIPv41,396
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6860
AS208221Orion telecom ltdUnclassifiedIPv4520
AS31500Global Network Management IncUnclassifiedIPv4188
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv4146
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4133
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4115
AS50673Serverius Holding B.V.UnclassifiedIPv4109
AS49673Truenetwork LLCUnclassifiedIPv483

Provenance

Where this comes from

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