asn.dev

Observed topology

AS62041 TELEGRAM

Hosting RIPE Content

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

Transit

Upstream networks

All 36

Networks observed carrying traffic for AS62041: 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 IPv6235
AS174Cogent Communications, LLCTransitIPv4 IPv6187
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6163
AS6939Hurricane Electric LLCTransitIPv4 IPv6146
AS1273IDDQD-ASBusinessIPv4 IPv6106
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv672
AS9002RETN LimitedUnclassifiedIPv4 IPv671
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv671
AS5511Orange S.A.TransitIPv4 IPv648
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv624

All 36 upstreams →

Transit

Downstream networks

inferred

Networks for which AS62041 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

All 36

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6235
AS174Cogent Communications, LLCTransitIPv4 IPv6187
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6163
AS6939Hurricane Electric LLCTransitIPv4 IPv6146
AS1273IDDQD-ASBusinessIPv4 IPv6106
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv672
AS9002RETN LimitedUnclassifiedIPv4 IPv671
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv671
AS5511Orange S.A.TransitIPv4 IPv648
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv624

All 36 adjacent →

Provenance

Where this comes from

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