asn.dev

Observed topology

AS62313 PROACT-AS

Unclassified RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS62313: 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
AS1299Arelion Sweden ABTransitIPv4260
AS174Cogent Communications, LLCTransitIPv4259
AS1828Unitas GlobalUnclassifiedIPv4252
AS33891Core-Backbone GmbHHostingIPv4208
AS1257Tele2 Sverige ABMobileIPv4101
AS6939Hurricane Electric LLCTransitIPv465
AS31027GlobalConnect A/SUnclassifiedIPv459
AS34549meerfarbig GmbH & Co. KGHostingIPv424
AS6797GlobalConnect ABUnclassifiedIPv48
AS12779IT.Gate S.p.A.UnclassifiedIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS216350Fortnox AktiebolagUnclassifiedIPv428
AS21083Proact Deutschland GmbHHostingIPv44

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4288
AS174Cogent Communications, LLCTransitIPv4260
AS1828Unitas GlobalUnclassifiedIPv4252
AS33891Core-Backbone GmbHHostingIPv4208
AS1257Tele2 Sverige ABMobileIPv4101
AS6939Hurricane Electric LLCTransitIPv465
AS31027GlobalConnect A/SUnclassifiedIPv459
AS216350Fortnox AktiebolagUnclassifiedIPv428
AS34549meerfarbig GmbH & Co. KGHostingIPv427
AS6797GlobalConnect ABUnclassifiedIPv48

Provenance

Where this comes from

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