asn.dev

Observed topology

AS31499 YCC-AS Ekaterinburg-2000 LLC

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31499: 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
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6269
AS1299Arelion Sweden ABTransitIPv4 IPv6102
AS3216PJSC "Vimpelcom"MobileIPv4 IPv669
AS31500Global Network Management IncUnclassifiedIPv4 IPv663
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS49673Truenetwork LLCUnclassifiedIPv48
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv48
AS50673Serverius Holding B.V.UnclassifiedIPv42
AS56655Gigahost ASUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS58310"TELEPORT" LLCUnclassifiedIPv463

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6299
AS1299Arelion Sweden ABTransitIPv4 IPv6114
AS3216PJSC "Vimpelcom"MobileIPv4 IPv678
AS31500Global Network Management IncUnclassifiedIPv4 IPv671
AS58310"TELEPORT" LLCUnclassifiedIPv463
AS24482SG.GSHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv49
AS49673Truenetwork LLCUnclassifiedIPv49
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv49
AS50673Serverius Holding B.V.UnclassifiedIPv42

All 11 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.