asn.dev

Observed topology

AS42632 MNOGOBYTE-AS Moscow, Russia

Hosting RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS42632: 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
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6738
AS8359MTS PJSCMobileIPv4631
AS6939Hurricane Electric LLCTransitIPv4 IPv6299
AS207351Transroute Telecom LTDUnclassifiedIPv434
AS49673Truenetwork LLCUnclassifiedIPv429
AS57304JSC "RetnNet"UnclassifiedIPv427
AS9002RETN LimitedUnclassifiedIPv426
AS24482SG.GSHostingIPv4 IPv626
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv612
AS25091IP-Max SAUnclassifiedIPv47

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS41349Limited Liability Company MVM TechnologyUnclassifiedIPv433
AS203391Cloud DNS LtdHostingIPv46

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6810
AS8359MTS PJSCMobileIPv4631
AS6939Hurricane Electric LLCTransitIPv4 IPv6299
AS6697Republican Unitary Telecommunication Enterprise BeltelecomResidentialIPv645
AS49673Truenetwork LLCUnclassifiedIPv438
AS207351Transroute Telecom LTDUnclassifiedIPv434
AS41349Limited Liability Company MVM TechnologyUnclassifiedIPv433
AS9002RETN LimitedUnclassifiedIPv429
AS57304JSC "RetnNet"UnclassifiedIPv427
AS24482SG.GSHostingIPv4 IPv626

All 17 adjacent →

Provenance

Where this comes from

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