asn.dev

Observed topology

AS62014 Telegram Telegram Messenger Inc

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62014: 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
AS24482SG.GSHostingIPv4 IPv6220
AS6939Hurricane Electric LLCTransitIPv4 IPv6119
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv656
AS174Cogent Communications, LLCTransitIPv4 IPv637
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv619
AS1273IDDQD-ASBusinessIPv412
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv68
AS38001NewMedia Express Pte LtdHostingIPv4 IPv68
AS37989DCS1 Pte. Ltd.HostingIPv47
AS9002RETN LimitedUnclassifiedIPv63

Transit

Downstream networks

inferred

Networks for which AS62014 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 AS62014 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS24482SG.GSHostingIPv4 IPv6220
AS6939Hurricane Electric LLCTransitIPv4 IPv6119
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv656
AS174Cogent Communications, LLCTransitIPv4 IPv637
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv619
AS1273IDDQD-ASBusinessIPv412
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv68
AS38001NewMedia Express Pte LtdHostingIPv4 IPv68
AS37989DCS1 Pte. Ltd.HostingIPv47
AS9002RETN LimitedUnclassifiedIPv63

Provenance

Where this comes from

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