asn.dev

Observed topology

AS41666 PYRO-AS Institute for Pyrotechnical Cleaning

Hosting RIPE Educational/Research

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS41666: 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
AS49585CoreRoute UGUnclassifiedIPv4 IPv655
AS6939Hurricane Electric LLCTransitIPv4 IPv642
AS2914NTT America, Inc.TransitIPv4 IPv637
AS24482SG.GSHostingIPv4 IPv63
AS401753BIXCE IncUnclassifiedIPv4 IPv63
AS1103SURF B.V.UnclassifiedIPv42
AS20766Association "Gitoyen"UnclassifiedIPv42
AS31500Global Network Management IncUnclassifiedIPv42
AS34927iFog GmbHHostingIPv42
AS37100SEACOM LimitedUnclassifiedIPv42

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56883Airmass 1 ABHostingIPv4 IPv696

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS56883Airmass 1 ABHostingIPv4 IPv696
AS2914NTT America, Inc.TransitIPv4 IPv679
AS6939Hurricane Electric LLCTransitIPv4 IPv677
AS49585CoreRoute UGUnclassifiedIPv4 IPv666
AS24482SG.GSHostingIPv4 IPv65
AS31500Global Network Management IncUnclassifiedIPv43
AS202365Omer GOLGELIUnclassifiedIPv43
AS401753BIXCE IncUnclassifiedIPv4 IPv63
AS1103SURF B.V.UnclassifiedIPv42
AS20766Association "Gitoyen"UnclassifiedIPv42

All 17 adjacent →

Provenance

Where this comes from

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