asn.dev

Observed topology

AS47949 GSNETCZ gsnet.cz s.r.o.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47949: 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
AS174Cogent Communications, LLCTransitIPv440
AS39392SH.cz s.r.o.HostingIPv413
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv41
AS20562Broadband Hosting B.V.HostingIPv41
AS24482SG.GSHostingIPv41
AS29504Freenet Liberec, z.s.UnclassifiedIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60724Sicuro Services s. r. o.UnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv480
AS60724Sicuro Services s. r. o.UnclassifiedIPv458
AS39392SH.cz s.r.o.HostingIPv426
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv42
AS20562Broadband Hosting B.V.HostingIPv42
AS24482SG.GSHostingIPv42
AS29504Freenet Liberec, z.s.UnclassifiedIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

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.