asn.dev

Observed topology

AS3267 niks SCIENTIFIC RESEARCH INSTITUTE FOR SYSTEM ANALYSIS OF THE NATIONAL RESEARCH CENTRE "KURCHATOV INSTITUTE"

Education RIPE Educational/Research

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS3267: 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
AS31500Global Network Management IncUnclassifiedIPv4 IPv62,841
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6666
AS6939Hurricane Electric LLCTransitIPv4 IPv6600
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6385
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6100
AS24482SG.GSHostingIPv4 IPv698
AS49673Truenetwork LLCUnclassifiedIPv491
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv688
AS56655Gigahost ASUnclassifiedIPv4 IPv685
AS25091IP-Max SAUnclassifiedIPv412

All 12 upstreams →

Transit

Downstream networks

All 60

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

ASNetworkTypeFamiliesPaths seen
AS42289ITMO UniversityUnclassifiedIPv4405
AS58255Institute for Nuclear Research of the Russian Academy of SciencesUnclassifiedIPv4387
AS49199Autonomous Nonprofit Organisation "Russian Scientific-Research Institute for Public Networks"UnclassifiedIPv4300
AS8398Tver Region Center of Informatization at Tver State UniversityUnclassifiedIPv4240
AS39503Peter the Great St. Petersburg Polytechnic UniversityUnclassifiedIPv4228
AS5480State Educational institution for High professional education 'Southern Federal University'EducationIPv4208
AS8790Federal State Budgetary Educational Institution of Higher Education "Petrozavodsk State University"EducationIPv4182
AS3351Ioffe Physical-Technical Institute of the Russian Academy of SciencesUnclassifiedIPv4177
AS29581State Educational Institution of higher professional Education 'Altay State University' named after Polzunov I.I.UnclassifiedIPv4 IPv6171
AS197467Samara University named after KorolevUnclassifiedIPv4 IPv6164

All 60 downstreams →

Adjacency

Adjacent networks

All 75

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

ASNetworkTypeFamiliesPaths seen
AS31500Global Network Management IncUnclassifiedIPv4 IPv65,901
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv61,491
AS6939Hurricane Electric LLCTransitIPv4 IPv61,251
AS3216PJSC "Vimpelcom"MobileIPv4 IPv61,108
AS2683Federal State Budgetary Educational Institution of Higher Education Lomonosov Moscow State UniversityEducationIPv4 IPv6448
AS42289ITMO UniversityUnclassifiedIPv4405
AS58255Institute for Nuclear Research of the Russian Academy of SciencesUnclassifiedIPv4387
AS49199Autonomous Nonprofit Organisation "Russian Scientific-Research Institute for Public Networks"UnclassifiedIPv4360
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv6255
AS8398Tver Region Center of Informatization at Tver State UniversityUnclassifiedIPv4240

All 75 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.