asn.dev

Observed topology

AS201966 OPTIKABEL

Residential RIPE

Upstreams 6 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 4
Upstream graph Who carries AS201966, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS201966 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201966: 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, LLCTransitIPv4 IPv6171
AS174Cogent Communications, LLCTransitIPv4 IPv6112
AS6939Hurricane Electric LLCTransitIPv4 IPv681
AS62178MASTER IT Technologies, a.s.UnclassifiedIPv425
AS24748Atman Sp. z o.o.HostingIPv46
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS62178MASTER IT Technologies, a.s.UnclassifiedIPv440
AS199810Miasto Bielsko-BialaUnclassifiedIPv415

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6216
AS174Cogent Communications, LLCTransitIPv4 IPv6114
AS6939Hurricane Electric LLCTransitIPv4 IPv695
AS62178MASTER IT Technologies, a.s.UnclassifiedIPv472
AS199810Miasto Bielsko-BialaUnclassifiedIPv415
AS24748Atman Sp. z o.o.HostingIPv46
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv4 IPv62
AS24482SG.GSHostingIPv41

Provenance

Where this comes from

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