asn.dev

Observed topology

AS196735 AS-JONCZ jakub@jon.cz

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS196735: 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 IPv6120
AS6939Hurricane Electric LLCTransitIPv422
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv42
AS20562Broadband Hosting B.V.HostingIPv42
AS24482SG.GSHostingIPv42
AS29504Freenet Liberec, z.s.UnclassifiedIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56344Viridium.cz s.r.o.ResidentialIPv4 IPv6187
AS200114PODA a.s.UnclassifiedIPv4177
AS197542Jan SaulichUnclassifiedIPv459
AS209795SPC-net s.r.o.UnclassifiedIPv459

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS39392SH.cz s.r.o.HostingIPv4 IPv6514
AS56344Viridium.cz s.r.o.ResidentialIPv4 IPv6187
AS200114PODA a.s.UnclassifiedIPv4177
AS6939Hurricane Electric LLCTransitIPv477
AS197542Jan SaulichUnclassifiedIPv459
AS209795SPC-net s.r.o.UnclassifiedIPv459
AS20562Broadband Hosting B.V.HostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv47
AS24482SG.GSHostingIPv47

All 11 adjacent →

Provenance

Where this comes from

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