asn.dev

Observed topology

AS6507 RIOT-NA1 - Riot Games, Inc

Hosting ARIN Content

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

Transit

Upstream networks

All 72

Networks observed carrying traffic for AS6507: 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, LLCTransitIPv4604
AS6939Hurricane Electric LLCTransitIPv4219
AS1299Arelion Sweden ABTransitIPv4 IPv6147
AS2914NTT America, Inc.TransitIPv4 IPv6126
AS4637Telstra GlobalUnclassifiedIPv4 IPv693
AS142505LIGHTSTORM DATA CENTERS PVT LTDUnclassifiedIPv474
AS13335Cloudflare, Inc.HostingIPv464
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv643
AS9304HGC Global Communications LimitedHostingIPv439
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv437

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS62830RiotGamesUnclassifiedIPv449

Adjacency

Adjacent networks

All 73

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4612
AS6939Hurricane Electric LLCTransitIPv4226
AS1299Arelion Sweden ABTransitIPv4 IPv6155
AS2914NTT America, Inc.TransitIPv4 IPv6129
AS4637Telstra GlobalUnclassifiedIPv4 IPv696
AS142505LIGHTSTORM DATA CENTERS PVT LTDUnclassifiedIPv474
AS13335Cloudflare, Inc.HostingIPv464
AS62830RiotGamesUnclassifiedIPv449
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv643
AS9304HGC Global Communications LimitedHostingIPv439

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.