asn.dev

Observed topology

AS201434 CITYSTRADAPL-AS CITYSTRADA S.A.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201434: 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
AS20853eTOP sp. z o.o.UnclassifiedIPv4 IPv6298
AS3257GTT Communications Inc.TransitIPv4 IPv671
AS6939Hurricane Electric LLCTransitIPv46
AS24482SG.GSHostingIPv4 IPv66
AS205268Diomar sp. z o.o.HostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS346006G Networks Sp. z o. o.UnclassifiedIPv4 IPv6264
AS31628Getfiber Sp. z o.o.UnclassifiedIPv4235
AS205268Diomar sp. z o.o.HostingIPv4 IPv682
AS202431M.G. System Sp. z o.o.UnclassifiedIPv458
AS2112344VOD Sp z o. o.UnclassifiedIPv412
AS204797Jamitel sp. z o.o.UnclassifiedIPv44
AS42576Maciej Jan Broniarz trading as CERT NGOUnclassifiedIPv62

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS20853eTOP sp. z o.o.UnclassifiedIPv4 IPv6857
AS346006G Networks Sp. z o. o.UnclassifiedIPv4 IPv6264
AS31628Getfiber Sp. z o.o.UnclassifiedIPv4235
AS3257GTT Communications Inc.TransitIPv4 IPv6148
AS205268Diomar sp. z o.o.HostingIPv4 IPv692
AS202431M.G. System Sp. z o.o.UnclassifiedIPv458
AS24482SG.GSHostingIPv4 IPv617
AS2112344VOD Sp z o. o.UnclassifiedIPv412
AS6939Hurricane Electric LLCTransitIPv410
AS204797Jamitel sp. z o.o.UnclassifiedIPv44

All 12 adjacent →

Provenance

Where this comes from

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