asn.dev

Observed topology

AS39603 P4NET P4 Sp. z o.o.

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS39603: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6404
AS3356Level 3 Parent, LLCTransitIPv4 IPv6344
AS6939Hurricane Electric LLCTransitIPv4 IPv6165
AS174Cogent Communications, LLCTransitIPv4 IPv6118
AS29314VECTRA S.A.ResidentialIPv4 IPv671
AS24482SG.GSHostingIPv4 IPv617
AS33891Core-Backbone GmbHHostingIPv416
AS34927iFog GmbHHostingIPv416
AS9141P4 Sp. z o.o.MobileIPv413
AS24748Atman Sp. z o.o.HostingIPv43

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15507P4 Sp. z o.o.UnclassifiedIPv4 IPv690
AS57811Redge Technologies sp. z o.o.HostingIPv458

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6488
AS3356Level 3 Parent, LLCTransitIPv4 IPv6344
AS6939Hurricane Electric LLCTransitIPv4 IPv6198
AS174Cogent Communications, LLCTransitIPv4 IPv6139
AS15507P4 Sp. z o.o.UnclassifiedIPv4 IPv690
AS29314VECTRA S.A.ResidentialIPv4 IPv671
AS57811Redge Technologies sp. z o.o.HostingIPv458
AS24482SG.GSHostingIPv4 IPv619
AS9141P4 Sp. z o.o.MobileIPv418
AS33891Core-Backbone GmbHHostingIPv416

All 14 adjacent →

Provenance

Where this comes from

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