asn.dev

Observed topology

AS35434 PIRXNET-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35434: 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
AS9141P4 Sp. z o.o.MobileIPv4 IPv6655
AS15744Silesian University of Technology, Computer CentreHostingIPv4 IPv6313
AS6939Hurricane Electric LLCTransitIPv4 IPv6185
AS24482SG.GSHostingIPv4 IPv618
AS24748Atman Sp. z o.o.HostingIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202220Obsluga pc P.Dudzinski P.Jablonski P.Ral. B.Miller s.c.ResidentialIPv4329
AS62031Tomasz Gasior trading as SownetResidentialIPv4 IPv618

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9141P4 Sp. z o.o.MobileIPv4 IPv6891
AS15744Silesian University of Technology, Computer CentreHostingIPv4 IPv6424
AS202220Obsluga pc P.Dudzinski P.Jablonski P.Ral. B.Miller s.c.ResidentialIPv4329
AS6939Hurricane Electric LLCTransitIPv4 IPv6185
AS24482SG.GSHostingIPv4 IPv618
AS62031Tomasz Gasior trading as SownetResidentialIPv4 IPv618
AS24748Atman Sp. z o.o.HostingIPv4 IPv62

Provenance

Where this comes from

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