Observed topology

AS34955 ASVICENIK

Unclassified RIPE

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34955: 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
AS39392	SH.cz s.r.o.	Hosting	IPv4	529
AS6939	Hurricane Electric LLC	Transit	IPv4	121
AS1764	Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH	Unclassified	IPv4	11
AS20562	Broadband Hosting B.V.	Hosting	IPv4	11
AS24482	SG.GS	Hosting	IPv4	11
AS29504	Freenet Liberec, z.s.	Unclassified	IPv4	11
AS37721	Virtual Technologies & Solutions	Residential	IPv4	11

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS65200	unnamed	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS39392	SH.cz s.r.o.	Hosting	IPv4	529
AS6939	Hurricane Electric LLC	Transit	IPv4	121
AS24482	SG.GS	Hosting	IPv4	12
AS29504	Freenet Liberec, z.s.	Unclassified	IPv4	12
AS1764	Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH	Unclassified	IPv4	11
AS20562	Broadband Hosting B.V.	Hosting	IPv4	11
AS37721	Virtual Technologies & Solutions	Residential	IPv4	11
AS65200	unnamed	Unclassified	IPv4	2

Provenance

Where this comes from

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