asn.dev

Observed topology

AS35328 DSIDATA DSI DATA flexi

Residential RIPE

Upstreams 9 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 13
Adjacent (IPv6) 5
Upstream graph Who carries AS35328, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS35328 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35328: 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
AS31117ENERGOTEL a.s.UnclassifiedIPv4 IPv6309
AS6939Hurricane Electric LLCTransitIPv4 IPv694
AS3303Swisscom (Schweiz) AGResidentialIPv414
AS24482SG.GSHostingIPv4 IPv68
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv68
AS20562Broadband Hosting B.V.HostingIPv47
AS31230Slovak University of Technology in BratislavaUnclassifiedIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS33891Core-Backbone GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS216083Prva internetova, s.r.oUnclassifiedIPv4 IPv6276
AS16367SALAMON INTERNET, s.r.o.UnclassifiedIPv4180
AS60895LEKOS, s.r.o.UnclassifiedIPv4120

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS31117ENERGOTEL a.s.UnclassifiedIPv4 IPv6794
AS216083Prva internetova, s.r.oUnclassifiedIPv4 IPv6396
AS6939Hurricane Electric LLCTransitIPv4 IPv6225
AS16367SALAMON INTERNET, s.r.o.UnclassifiedIPv4180
AS60895LEKOS, s.r.o.UnclassifiedIPv4120
AS3303Swisscom (Schweiz) AGResidentialIPv435
AS24482SG.GSHostingIPv4 IPv620
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv620
AS20562Broadband Hosting B.V.HostingIPv418
AS31230Slovak University of Technology in BratislavaUnclassifiedIPv418

Provenance

Where this comes from

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