Observed topology

AS25468 pl-polrze-AS Rzeszow University of Technology

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 3

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25468: 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
AS8501	Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking Center	Education	IPv4 IPv6	475

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS206006	Ekonomiczna im. ks. Bronislawa Markiewicza w Jaroslawiu	Unclassified	IPv4 IPv6	42
AS31381	Wyzsza Szkola Informatyki i Zarzadzania	Unclassified	IPv4	8

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS8501	Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking Center	Education	IPv4 IPv6	525
AS206006	Ekonomiczna im. ks. Bronislawa Markiewicza w Jaroslawiu	Unclassified	IPv4 IPv6	42
AS31381	Wyzsza Szkola Informatyki i Zarzadzania	Unclassified	IPv4	8

Provenance

Where this comes from

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