asn.dev

Observed topology

AS39328 Sisnet SISNET NUEVAS TECNOLOGIAS S.L.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39328: 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
AS3262SAREnet, S.A.ResidentialIPv4351
AS34696MISMELINK NETWORKS, SLUnclassifiedIPv4147
AS6939Hurricane Electric LLCTransitIPv477
AS34549meerfarbig GmbH & Co. KGHostingIPv427
AS24482SG.GSHostingIPv49
AS37721Virtual Technologies & SolutionsResidentialIPv49
AS5405Inter.link GmbHUnclassifiedIPv44
AS33891Core-Backbone GmbHHostingIPv42
AS25091IP-Max SAUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205179Virtualdeploy SLUnclassifiedIPv4825

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS205179Virtualdeploy SLUnclassifiedIPv4825
AS34696MISMELINK NETWORKS, SLUnclassifiedIPv4816
AS3262SAREnet, S.A.ResidentialIPv4351
AS6939Hurricane Electric LLCTransitIPv4173
AS34549meerfarbig GmbH & Co. KGHostingIPv463
AS24482SG.GSHostingIPv421
AS37721Virtual Technologies & SolutionsResidentialIPv421
AS5405Inter.link GmbHUnclassifiedIPv44
AS33891Core-Backbone GmbHHostingIPv42
AS25091IP-Max SAUnclassifiedIPv41

Provenance

Where this comes from

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