Observed topology

AS6507 RIOT-NA1

Hosting ARIN

Upstreams 72 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 68

Adjacent (IPv6) 24

Upstream graph Who carries AS6507, and who carries them, drawn as a map up to the transit-free core. 74 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.

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	627
AS6939	Hurricane Electric LLC	Transit	IPv4	216
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	144
AS2914	NTT America, Inc.	Transit	IPv4	105
AS4637	Telstra Global	Unclassified	IPv4 IPv6	92
AS142505	LIGHTSTORM DATA CENTERS PVT LTD	Unclassified	IPv4	73
AS9304	HGC Global Communications Limited	Hosting	IPv4	67
AS13335	Cloudflare, Inc.	Hosting	IPv4	65
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4 IPv6	46
AS12956	TELEFONICA GLOBAL SOLUTIONS SL	Transit	IPv4	43

All 72 upstreams →

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS62830	RiotGames	Unclassified	IPv4	51

Adjacency

Adjacent networks

All 73

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	636
AS6939	Hurricane Electric LLC	Transit	IPv4	223
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	153
AS2914	NTT America, Inc.	Transit	IPv4	108
AS4637	Telstra Global	Unclassified	IPv4 IPv6	95
AS142505	LIGHTSTORM DATA CENTERS PVT LTD	Unclassified	IPv4	73
AS9304	HGC Global Communications Limited	Hosting	IPv4	67
AS13335	Cloudflare, Inc.	Hosting	IPv4	65
AS62830	RiotGames	Unclassified	IPv4	51
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4 IPv6	46

All 73 adjacent →

Provenance

Where this comes from

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