asn.dev

Observed topology

AS34409 POLSKAPRESS-AS

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34409: 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
AS3257GTT Communications Inc.TransitIPv4 IPv6343
AS12831Technical University of Gdansk, Academic Computer Center TASKUnclassifiedIPv4 IPv6187
AS6939Hurricane Electric LLCTransitIPv4 IPv6122
AS5617Orange Polska Spolka AkcyjnaMobileIPv4 IPv661
AS24482SG.GSHostingIPv4 IPv613
AS33891Core-Backbone GmbHHostingIPv412
AS29632Netassist International EOODUnclassifiedIPv62
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204534Polska Press Sp. z o.o.UnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4 IPv6345
AS12831Technical University of Gdansk, Academic Computer Center TASKUnclassifiedIPv4 IPv6188
AS6939Hurricane Electric LLCTransitIPv4 IPv6122
AS5617Orange Polska Spolka AkcyjnaMobileIPv4 IPv661
AS24482SG.GSHostingIPv4 IPv613
AS33891Core-Backbone GmbHHostingIPv412
AS204534Polska Press Sp. z o.o.UnclassifiedIPv43
AS29632Netassist International EOODUnclassifiedIPv62
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv61

Provenance

Where this comes from

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