asn.dev

Observed topology

AS42773 INTELCOM-UPSTREAM Nemerov Evgeniy Vladimirovish PE

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42773: 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
AS210756EdgeCenter LLCHostingIPv436
AS39785Axioma, LLCResidentialIPv420
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv42
AS13094JSC "ER-Telecom Holding"UnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57251LLC IntelcomUnclassifiedIPv4854
AS43605Severo-Eniseysk-Telecom LLCUnclassifiedIPv462
AS51838Krasnoyarsklespromproekt OJSCUnclassifiedIPv461
AS41831PRAVOVED LLCUnclassifiedIPv455

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS57251LLC IntelcomUnclassifiedIPv4854
AS210756EdgeCenter LLCHostingIPv4767
AS39785Axioma, LLCResidentialIPv4213
AS43605Severo-Eniseysk-Telecom LLCUnclassifiedIPv462
AS51838Krasnoyarsklespromproekt OJSCUnclassifiedIPv461
AS41831PRAVOVED LLCUnclassifiedIPv455
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv421
AS24482SG.GSHostingIPv418
AS37721Virtual Technologies & SolutionsResidentialIPv418
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv418

All 15 adjacent →

Provenance

Where this comes from

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