asn.dev

Observed topology

AS205856 AS_polnet24 Robert Wojna trading as Polnet24 SP. Z O.O.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS205856: 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
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4 IPv691
AS5617Orange Polska Spolka AkcyjnaMobileIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv62
AS33891Core-Backbone GmbHHostingIPv41
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS30780Tomasz SLASKI trading as SKONET ISPUnclassifiedIPv642

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4 IPv691
AS30780Tomasz SLASKI trading as SKONET ISPUnclassifiedIPv642
AS6939Hurricane Electric LLCTransitIPv638
AS5617Orange Polska Spolka AkcyjnaMobileIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv64
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv63
AS33891Core-Backbone GmbHHostingIPv41

Provenance

Where this comes from

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