asn.dev

Observed topology

AS28797 KOSMAN-COM-AS Technical University of Koszalin

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28797: 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
AS13293Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking CenterUnclassifiedIPv446
AS6939Hurricane Electric LLCTransitIPv412
AS24482SG.GSHostingIPv41
AS196844Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking CenterUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS196728Bialogardzka Spoldzielnia MieszkaniowaUnclassifiedIPv444
AS28678Technical University of KoszalinUnclassifiedIPv418
AS208424GlobalLogic Poland Sp. z o.o.UnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13293Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking CenterUnclassifiedIPv467
AS196728Bialogardzka Spoldzielnia MieszkaniowaUnclassifiedIPv444
AS196844Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking CenterUnclassifiedIPv436
AS6939Hurricane Electric LLCTransitIPv420
AS28678Technical University of KoszalinUnclassifiedIPv418
AS208424GlobalLogic Poland Sp. z o.o.UnclassifiedIPv42
AS24482SG.GSHostingIPv41

Provenance

Where this comes from

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