asn.dev

Observed topology

AS35526 MASTERBIT-AS

Unclassified RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS35526: 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 RostelecomResidentialIPv4306
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4168
AS31500Global Network Management IncUnclassifiedIPv4114
AS3216PJSC "Vimpelcom"MobileIPv463
AS6939Hurricane Electric LLCTransitIPv4 IPv638
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv629
AS31133PJSC MegaFonMobileIPv427
AS50673Serverius Holding B.V.UnclassifiedIPv418
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv614
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv614

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49238Doctor Web LLCUnclassifiedIPv4120
AS51932FGUP Goskorporatsiya po OrVDUnclassifiedIPv47
AS48223Senator Telecom Ltd.UnclassifiedIPv43

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4306
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4238
AS31500Global Network Management IncUnclassifiedIPv4148
AS49238Doctor Web LLCUnclassifiedIPv4120
AS3216PJSC "Vimpelcom"MobileIPv463
AS6939Hurricane Electric LLCTransitIPv4 IPv650
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv629
AS31133PJSC MegaFonMobileIPv427
AS50673Serverius Holding B.V.UnclassifiedIPv419
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv617

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.