asn.dev

Observed topology

AS41625 ETSERVICE-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41625: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6179
AS174Cogent Communications, LLCTransitIPv4 IPv6138
AS9002RETN LimitedUnclassifiedIPv4 IPv6123
AS3491PCCW Global (HK) Ltd.TransitIPv442
AS41095IPTP LTDHostingIPv4 IPv620
AS9304HGC Global Communications LimitedHostingIPv4 IPv616
AS140951IPTP NetworksUnclassifiedIPv4 IPv614
AS3320Deutsche Telekom AGMobileIPv45
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv45

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6179
AS174Cogent Communications, LLCTransitIPv4 IPv6138
AS9002RETN LimitedUnclassifiedIPv4 IPv6123
AS3491PCCW Global (HK) Ltd.TransitIPv442
AS41095IPTP LTDHostingIPv4 IPv620
AS9304HGC Global Communications LimitedHostingIPv4 IPv616
AS140951IPTP NetworksUnclassifiedIPv4 IPv614
AS3320Deutsche Telekom AGMobileIPv45
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv45

Provenance

Where this comes from

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