asn.dev

Observed topology

AS39886 STELOGY-INFRASTRUCTURE Nomotech SAS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39886: 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
AS6461Zayo BandwidthTransitIPv4144
AS29467LUXNETWORK S.A.UnclassifiedIPv433

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS35184Nomotech SASUnclassifiedIPv4 IPv6513
AS30801Nomotech SASUnclassifiedIPv4 IPv6453
AS34704VOIP Telecom SASUnclassifiedIPv4 IPv6438
AS57752VOIP Telecom SASResidentialIPv4 IPv6373
AS198034VOIP Telecom SASHostingIPv4344
AS204140Osmoz Ware SASUnclassifiedIPv4 IPv6323
AS34761Nomotech SASUnclassifiedIPv459
AS57103Nomotech SASResidentialIPv4 IPv65

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,876
AS29467LUXNETWORK S.A.UnclassifiedIPv4 IPv61,121
AS35184Nomotech SASUnclassifiedIPv4 IPv6808
AS30801Nomotech SASUnclassifiedIPv4 IPv6453
AS34704VOIP Telecom SASUnclassifiedIPv4 IPv6438
AS57752VOIP Telecom SASResidentialIPv4 IPv6390
AS198034VOIP Telecom SASHostingIPv4344
AS204140Osmoz Ware SASUnclassifiedIPv4 IPv6323
AS34761Nomotech SASUnclassifiedIPv459
AS57103Nomotech SASResidentialIPv4 IPv65

Provenance

Where this comes from

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