asn.dev

Observed topology

AS8749 REDCOM-AS Redcom, Khabarovsk, Russia

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8749: 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 RostelecomResidentialIPv4 IPv6437
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6419
AS31133PJSC MegaFonMobileIPv4 IPv6378
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6141

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS212414KASAT LLCUnclassifiedIPv4 IPv672
AS204898OOO AvantelecomUnclassifiedIPv436
AS12770Federal State Budgetary Educational University of Higher Education "Pacific National University named after M.P.Danilovskiy"UnclassifiedIPv430
AS201820JSC "Khabarovsky airport"UnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS31133PJSC MegaFonMobileIPv4 IPv6480
AS12389PJSC RostelecomResidentialIPv4 IPv6460
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6434
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6153
AS212414KASAT LLCUnclassifiedIPv4 IPv672
AS204898OOO AvantelecomUnclassifiedIPv436
AS12770Federal State Budgetary Educational University of Higher Education "Pacific National University named after M.P.Danilovskiy"UnclassifiedIPv430
AS201820JSC "Khabarovsky airport"UnclassifiedIPv414

Provenance

Where this comes from

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