asn.dev

Observed topology

AS35237 Sberbank Sberbank of Russia PJSC

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS35237: 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
AS3216PJSC "Vimpelcom"MobileIPv4306
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6193
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4143
AS6939Hurricane Electric LLCTransitIPv4111
AS31133PJSC MegaFonMobileIPv4 IPv671
AS24482SG.GSHostingIPv4 IPv616
AS37721Virtual Technologies & SolutionsResidentialIPv415
AS50673Serverius Holding B.V.UnclassifiedIPv415
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv415
AS34927iFog GmbHHostingIPv414

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47457Sberbank of Russia PJSCUnclassifiedIPv429
AS60122Sberbank of Russia PJSCUnclassifiedIPv412

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3216PJSC "Vimpelcom"MobileIPv4316
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6210
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4149
AS6939Hurricane Electric LLCTransitIPv4116
AS31133PJSC MegaFonMobileIPv4 IPv672
AS47457Sberbank of Russia PJSCUnclassifiedIPv429
AS24482SG.GSHostingIPv4 IPv616
AS50673Serverius Holding B.V.UnclassifiedIPv416
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv416
AS37721Virtual Technologies & SolutionsResidentialIPv415

All 13 adjacent →

Provenance

Where this comes from

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