asn.dev

Observed topology

AS49685 SIGNET-AS Signet B.V.

Unclassified RIPE NSP

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS49685: 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
AS8455atom86 BVHostingIPv4 IPv6582
AS24785Broadband Hosting B.V.HostingIPv4 IPv6536
AS6939Hurricane Electric LLCTransitIPv457
AS24482SG.GSHostingIPv4 IPv636
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv636
AS48185team.blue NVUnclassifiedIPv4 IPv635
AS1103SURF B.V.UnclassifiedIPv4 IPv630
AS213241TECHIT.BE SRLResidentialIPv628
AS4657StarHub LtdResidentialIPv47
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv66

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39700Signet B.V.UnclassifiedIPv4 IPv61,181

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS39700Signet B.V.UnclassifiedIPv4 IPv68,226
AS24785Broadband Hosting B.V.HostingIPv4 IPv64,118
AS8455atom86 BVHostingIPv4 IPv63,002
AS6939Hurricane Electric LLCTransitIPv4676
AS48185team.blue NVUnclassifiedIPv4 IPv6218
AS24482SG.GSHostingIPv4 IPv6214
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6214
AS213241TECHIT.BE SRLResidentialIPv6122
AS1103SURF B.V.UnclassifiedIPv4 IPv6113
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv6101

All 25 adjacent →

Provenance

Where this comes from

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