asn.dev

Observed topology

AS34169 MEDIA-COM-TYCHY Media-Com Sp. z o.o.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34169: 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-PoludnieUnclassifiedIPv4374
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv473
AS24482SG.GSHostingIPv47
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42717Uslugi Transportowe I Internetowe Trans-Net Grzegorz GojUnclassifiedIPv4130
AS47466Przedsiebiorstwo Produkcyjno-Montazowe Budownictwa PROMONT Sylwester BaradziejUnclassifiedIPv4130
AS50253PLAY5 S.A.UnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4589
AS42717Uslugi Transportowe I Internetowe Trans-Net Grzegorz GojUnclassifiedIPv4130
AS47466Przedsiebiorstwo Produkcyjno-Montazowe Budownictwa PROMONT Sylwester BaradziejUnclassifiedIPv4130
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv4115
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv410
AS24482SG.GSHostingIPv49
AS50253PLAY5 S.A.UnclassifiedIPv43

Provenance

Where this comes from

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