Observed topology

AS60806 ZICOMNEXT "ZICOM NEXT" SPOLKA Z OGRANICZONA ODPOWIEDZIALNOSCIA

Unclassified RIPE Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

Upstream graph Who carries AS60806, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS60806 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60806: 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.

AS	Network	Type	Families	Paths seen
AS9002	RETN Limited	Unclassified	IPv4	459
AS5617	Orange Polska Spolka Akcyjna	Mobile	IPv4	364
AS6939	Hurricane Electric LLC	Transit	IPv4	192
AS33891	Core-Backbone GmbH	Hosting	IPv4	34
AS24482	SG.GS	Hosting	IPv4	18

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS57255	Piotr Platek trading as Platkom Tele-Informatyka	Residential	IPv4	66
AS51272	Gensys Sp. z.o.o	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS9002	RETN Limited	Unclassified	IPv4	549
AS5617	Orange Polska Spolka Akcyjna	Mobile	IPv4	387
AS6939	Hurricane Electric LLC	Transit	IPv4	201
AS57255	Piotr Platek trading as Platkom Tele-Informatyka	Residential	IPv4	66
AS51272	Gensys Sp. z.o.o	Unclassified	IPv4	59
AS33891	Core-Backbone GmbH	Hosting	IPv4	36
AS24482	SG.GS	Hosting	IPv4	19

Provenance

Where this comes from

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