asn.dev

Observed topology

AS5550 TASK-AS Gdansk University of Technology

Education RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS5550: 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
AS8501Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking CenterEducationIPv4 IPv647
AS196844Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking CenterUnclassifiedIPv4 IPv645
AS24482SG.GSHostingIPv4 IPv62
AS5617Orange Polska Spolka AkcyjnaMobileIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12827Wirtualna Polska Media S.A.UnclassifiedIPv440

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS196844Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking CenterUnclassifiedIPv4 IPv683
AS8501Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking CenterEducationIPv4 IPv647
AS12827Wirtualna Polska Media S.A.UnclassifiedIPv440
AS12831Technical University of Gdansk, Academic Computer Center TASKUnclassifiedIPv435
AS43171Lukasz Rafal Hamerski trading as MaxnetResidentialIPv435
AS24482SG.GSHostingIPv4 IPv64
AS5617Orange Polska Spolka AkcyjnaMobileIPv41

Provenance

Where this comes from

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