asn.dev

Observed topology

AS62371 PROTON Proton AG

Unclassified RIPE Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62371: 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
AS13335Cloudflare, Inc.HostingIPv4759
AS6939Hurricane Electric LLCTransitIPv6238
AS199524G-Core Labs S.A.HostingIPv433
AS3356Level 3 Parent, LLCTransitIPv69
AS9002RETN LimitedUnclassifiedIPv64
AS1836green.ch AGResidentialIPv62
AS24482SG.GSHostingIPv62
AS25091IP-Max SAUnclassifiedIPv62
AS48362Stadtwerke FeldkirchResidentialIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209103Proton AGUnclassifiedIPv4 IPv6476

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv4759
AS6939Hurricane Electric LLCTransitIPv4 IPv6631
AS209103Proton AGUnclassifiedIPv4 IPv6476
AS3356Level 3 Parent, LLCTransitIPv4 IPv670
AS199524G-Core Labs S.A.HostingIPv433
AS1836green.ch AGResidentialIPv4 IPv68
AS9002RETN LimitedUnclassifiedIPv68
AS24482SG.GSHostingIPv4 IPv68
AS25091IP-Max SAUnclassifiedIPv64
AS33891Core-Backbone GmbHHostingIPv44

All 11 adjacent →

Provenance

Where this comes from

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