asn.dev

Observed topology

AS37517 CVTS1

Unclassified AFRINIC

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS37517: 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 ABTransitIPv4 IPv61,153
AS6939Hurricane Electric LLCTransitIPv4 IPv6407
AS37468Angola CablesUnclassifiedIPv4324
AS34549meerfarbig GmbH & Co. KGHostingIPv4168
AS33891Core-Backbone GmbHHostingIPv460
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv643
AS1836green.ch AGResidentialIPv442
AS6797GlobalConnect ABUnclassifiedIPv442
AS12779IT.Gate S.p.A.UnclassifiedIPv442
AS20764CJSC RASCOMUnclassifiedIPv442

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328148Agence De l'Informatique de l'EtatUnclassifiedIPv4750
AS327862NOSi EPEUnclassifiedIPv4177
AS328941CABO VERDE TELECOM, S.AUnclassifiedIPv4177

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,747
AS328148Agence De l'Informatique de l'EtatUnclassifiedIPv41,040
AS6939Hurricane Electric LLCTransitIPv4 IPv6524
AS37613DOLPHIN TELECOMMUNICATION LIMITEDUnclassifiedIPv4460
AS37468Angola CablesUnclassifiedIPv4445
AS34549meerfarbig GmbH & Co. KGHostingIPv4256
AS327862NOSi EPEUnclassifiedIPv4177
AS328941CABO VERDE TELECOM, S.AUnclassifiedIPv4177
AS33891Core-Backbone GmbHHostingIPv470
AS24482SG.GSHostingIPv465

All 22 adjacent →

Provenance

Where this comes from

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