Observed topology

AS39816 VOLTA-AS

Residential RIPE

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

Upstream graph Who carries AS39816, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS39816 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39816: 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
AS51465	M3.NET Sp. zoo	Hosting	IPv4	590

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS61434	Ziaja Ltd Zaklad Produkcji Lekow sp z o.o.	Unclassified	IPv4	59
AS62308	Bibus Menos Sp. z o.o.	Unclassified	IPv4	59
AS211746	ETOS S. A.	Unclassified	IPv4	7
AS51976	JP-Telekom Sp z o.o.	Unclassified	IPv4	6
AS51590	PRZEDSIEBIORSTWO HANDLOWOPRODUKCYJNOUSLUGOWE "ARONET" ANDRZEJ OLSZEWSKI	Unclassified	IPv4	3

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS51465	M3.NET Sp. zoo	Hosting	IPv4	724
AS61434	Ziaja Ltd Zaklad Produkcji Lekow sp z o.o.	Unclassified	IPv4	59
AS62308	Bibus Menos Sp. z o.o.	Unclassified	IPv4	59
AS211746	ETOS S. A.	Unclassified	IPv4	7
AS51976	JP-Telekom Sp z o.o.	Unclassified	IPv4	6
AS51590	PRZEDSIEBIORSTWO HANDLOWOPRODUKCYJNOUSLUGOWE "ARONET" ANDRZEJ OLSZEWSKI	Unclassified	IPv4	3

Provenance

Where this comes from

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