Observed topology

AS59832 NASK-PIB NAUKOWA I AKADEMICKA SIEC KOMPUTEROWA - PANSTWOWY INSTYTUT BADAWCZY

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 30

Adjacent (IPv6) 0

Upstream graph Who carries AS59832, and who carries them, drawn as a map up to the transit-free core. 4 exchanges Where AS59832 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59832: 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.

AS	Network	Type	Families	Paths seen
AS8308	PANSTWOWY INSTYTUT BADAWCZY	Unclassified	IPv4	59

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS199953	Centralny Osrodek Informatyki	Unclassified	IPv4	60
AS202600	KOMENDA GLOWNA STRAZY GRANICZNEJ	Unclassified	IPv4	60
AS204679	PANSTWOWY INSTYTUT BADAWCZY	Unclassified	IPv4	43
AS199815	Biuro Urzadzania Lasu i Geodezji Lesnej Przedsiebiorstwo Panstwowe	Unclassified	IPv4	16
AS50705	PRZEDSIEBIORSTWO TELEKOMUNIKACYJNE "TELGAM" SPOLKA AKCYJNA	Unclassified	IPv4	1

Adjacency

Adjacent networks

All 30

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

AS	Network	Type	Families	Paths seen
AS19551	Incapsula Inc	Hosting	IPv4	136
AS199953	Centralny Osrodek Informatyki	Unclassified	IPv4	60
AS202600	KOMENDA GLOWNA STRAZY GRANICZNEJ	Unclassified	IPv4	60
AS8308	PANSTWOWY INSTYTUT BADAWCZY	Unclassified	IPv4	59
AS204679	PANSTWOWY INSTYTUT BADAWCZY	Unclassified	IPv4	43
AS199815	Biuro Urzadzania Lasu i Geodezji Lesnej Przedsiebiorstwo Panstwowe	Unclassified	IPv4	16
AS1299	Arelion Sweden AB	Transit	IPv4	10
AS6939	Hurricane Electric LLC	Transit	IPv4	6
AS174	Cogent Communications, LLC	Transit	IPv4	4
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	3

All 30 adjacent →

Provenance

Where this comes from

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