Observed topology

AS29205 VERCOM

Unclassified RIPE

Upstreams 4 carry this network

Downstreams 9 this network carries

Adjacent (IPv4) 13

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29205: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4	436
AS31229	Beyond.pl sp. z o.o.	Hosting	IPv4	379
AS174	Cogent Communications, LLC	Transit	IPv4	177
AS58321	Oxylion Sp. z o.o.	Unclassified	IPv4	126

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS212904	FRESHPLANNERS Sp. z o.o.	Unclassified	IPv4	464
AS42945	VERCOM S.A.	Unclassified	IPv4	59
AS47348	VERCOM S.A.	Unclassified	IPv4	58
AS59828	VERCOM S.A.	Unclassified	IPv4	58
AS204692	VERCOM S.A.	Unclassified	IPv4	58
AS204962	VERCOM S.A.	Unclassified	IPv4	58
AS204964	VERCOM S.A.	Unclassified	IPv4	58
AS209541	VERCOM S.A.	Unclassified	IPv4	58
AS211920	MessageFlow.com GmbH	Unclassified	IPv4	58

Adjacency

Adjacent networks

All 13

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

AS	Network	Type	Families	Paths seen
AS31229	Beyond.pl sp. z o.o.	Hosting	IPv4	883
AS212904	FRESHPLANNERS Sp. z o.o.	Unclassified	IPv4	464
AS3356	Level 3 Parent, LLC	Transit	IPv4	436
AS58321	Oxylion Sp. z o.o.	Unclassified	IPv4	375
AS174	Cogent Communications, LLC	Transit	IPv4	353
AS42945	VERCOM S.A.	Unclassified	IPv4	59
AS47348	VERCOM S.A.	Unclassified	IPv4	58
AS59828	VERCOM S.A.	Unclassified	IPv4	58
AS204692	VERCOM S.A.	Unclassified	IPv4	58
AS204962	VERCOM S.A.	Unclassified	IPv4	58

All 13 adjacent →

Provenance

Where this comes from

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