asn.dev

Observed topology

AS39537 HNS www.hns.net

Unclassified RIPE

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS39537: 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, LLCTransitIPv4 IPv6449
AS3356Level 3 Parent, LLCTransitIPv4 IPv6432
AS6939Hurricane Electric LLCTransitIPv4 IPv6195
AS34549meerfarbig GmbH & Co. KGHostingIPv463
AS50304Blix Solutions ASUnclassifiedIPv442
AS24482SG.GSHostingIPv4 IPv623
AS3216PJSC "Vimpelcom"MobileIPv421
AS3741Dimension DataUnclassifiedIPv421
AS4657StarHub LtdResidentialIPv421
AS12552GlobalConnect ABUnclassifiedIPv421

All 18 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211124CGI France SASUnclassifiedIPv41,307
AS51491SysGroup plcUnclassifiedIPv4118
AS64415Ashgoal LimitedUnclassifiedIPv442
AS201261The Watershed Arts Trust LtdUnclassifiedIPv425

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS211124CGI France SASUnclassifiedIPv41,307
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,004
AS174Cogent Communications, LLCTransitIPv4 IPv6676
AS6939Hurricane Electric LLCTransitIPv4 IPv6387
AS34549meerfarbig GmbH & Co. KGHostingIPv4144
AS51491SysGroup plcUnclassifiedIPv4118
AS50304Blix Solutions ASUnclassifiedIPv496
AS33891Core-Backbone GmbHHostingIPv454
AS3216PJSC "Vimpelcom"MobileIPv448
AS3741Dimension DataUnclassifiedIPv448

All 24 adjacent →

Provenance

Where this comes from

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