asn.dev

Observed topology

AS34766 Layer23 atom86 BV

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34766: 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
AS8455atom86 BVHostingIPv4 IPv6368
AS200023Qonnected B.V.ResidentialIPv4144
AS24785Broadband Hosting B.V.HostingIPv4119
AS1299Arelion Sweden ABTransitIPv4 IPv6111
AS13237euNetworks GmbHUnclassifiedIPv4 IPv658

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44612IP-SecurITy B.V.UnclassifiedIPv4 IPv6337
AS51377CoMaSys ApSUnclassifiedIPv4 IPv6326
AS204866Microdata ApsUnclassifiedIPv4242
AS212447Seneca B.V.UnclassifiedIPv4 IPv6154
AS204432Perspektiva IT ApSUnclassifiedIPv454
AS218370TWS technologies GmbHUnclassifiedIPv4 IPv645
AS34501Viva Telecom SRLUnclassifiedIPv431
AS35349ViewControl B.V.UnclassifiedIPv414

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS8455atom86 BVHostingIPv4 IPv6767
AS1299Arelion Sweden ABTransitIPv4 IPv6669
AS44612IP-SecurITy B.V.UnclassifiedIPv4 IPv6337
AS51377CoMaSys ApSUnclassifiedIPv4 IPv6326
AS200023Qonnected B.V.ResidentialIPv4287
AS204866Microdata ApsUnclassifiedIPv4242
AS24785Broadband Hosting B.V.HostingIPv4222
AS212447Seneca B.V.UnclassifiedIPv4 IPv6154
AS13237euNetworks GmbHUnclassifiedIPv4 IPv658
AS204432Perspektiva IT ApSUnclassifiedIPv454

Provenance

Where this comes from

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