asn.dev

Observed topology

AS204332 TKCSYSTEM

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS204332: 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
AS39392SH.cz s.r.o.HostingIPv4 IPv6138
AS6939Hurricane Electric LLCTransitIPv433
AS42000Futruy s.r.o.UnclassifiedIPv629
AS24482SG.GSHostingIPv4 IPv64
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv64
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv43
AS20562Broadband Hosting B.V.HostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50630Advanced Industries Packaging A/SUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS39392SH.cz s.r.o.HostingIPv4 IPv6140
AS6939Hurricane Electric LLCTransitIPv433
AS42000Futruy s.r.o.UnclassifiedIPv629
AS24482SG.GSHostingIPv4 IPv64
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv64
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv43
AS20562Broadband Hosting B.V.HostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS50630Advanced Industries Packaging A/SUnclassifiedIPv42

Provenance

Where this comes from

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