asn.dev

Observed topology

AS59832 NASK-PIB

Unclassified RIPE Content

Upstreams 1 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 35
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.

ASNetworkTypeFamiliesPaths seen
AS8308PANSTWOWY INSTYTUT BADAWCZYUnclassifiedIPv460

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204679PANSTWOWY INSTYTUT BADAWCZYUnclassifiedIPv499
AS51101Marceli Kaczo trading as Rewolucja-NETResidentialIPv496
AS199953Centralny Osrodek InformatykiUnclassifiedIPv460
AS50705PRZEDSIEBIORSTWO TELEKOMUNIKACYJNE "TELGAM" SPOLKA AKCYJNAUnclassifiedIPv439
AS197336TEL-KAB Sp. z o.o.UnclassifiedIPv416

Adjacency

Adjacent networks

All 35

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

ASNetworkTypeFamiliesPaths seen
AS204679PANSTWOWY INSTYTUT BADAWCZYUnclassifiedIPv499
AS51101Marceli Kaczo trading as Rewolucja-NETResidentialIPv496
AS1299Arelion Sweden ABTransitIPv470
AS8308PANSTWOWY INSTYTUT BADAWCZYUnclassifiedIPv460
AS19551Incapsula IncHostingIPv460
AS199953Centralny Osrodek InformatykiUnclassifiedIPv460
AS50705PRZEDSIEBIORSTWO TELEKOMUNIKACYJNE "TELGAM" SPOLKA AKCYJNAUnclassifiedIPv439
AS174Cogent Communications, LLCTransitIPv432
AS9141P4 Sp. z o.o.MobileIPv418
AS34549meerfarbig GmbH & Co. KGHostingIPv418

All 35 adjacent →

Provenance

Where this comes from

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