asn.dev

Observed topology

AS3169 BRKNETWORKDEVICES

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3169: 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
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4662
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv463
AS212261Stowarzyszenie e-PoludnieUnclassifiedIPv435
AS24482SG.GSHostingIPv412
AS35179Korbank S. A.UnclassifiedIPv411
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206786Tomasz SzachtaUnclassifiedIPv466

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4718
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv469
AS206786Tomasz SzachtaUnclassifiedIPv466
AS212261Stowarzyszenie e-PoludnieUnclassifiedIPv437
AS24482SG.GSHostingIPv413
AS35179Korbank S. A.UnclassifiedIPv411
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv42

Provenance

Where this comes from

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