asn.dev

Observed topology

AS202580 A-Systems Sp. z o.o.

Unclassified RIPE Route Server

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS202580: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS30058FDCservers.netUnclassifiedIPv4 IPv6202
AS48729ServerKing B.V.UnclassifiedIPv488
AS202425IP Volume incUnclassifiedIPv455
AS207466Sebastien BeaufourUnclassifiedIPv617
AS44529Geely Europe Innovation and Collaboration ABUnclassifiedIPv4 IPv612
AS58349Elna Paulette Valentin trading as INNETRA PCUnclassifiedIPv44
AS210578Niels Groenewegen trading as NeNetUnclassifiedIPv64
AS212477RoyaleHosting BVHostingIPv42
AS219331Thomas BOUZINUnclassifiedIPv62
AS211715Christian VondersteinUnclassifiedIPv61

All 11 downstreams →

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS48729ServerKing B.V.UnclassifiedIPv4548
AS401753BIXCE IncUnclassifiedIPv4 IPv6530
AS6939Hurricane Electric LLCTransitIPv4420
AS30058FDCservers.netUnclassifiedIPv4 IPv6292
AS202425IP Volume incUnclassifiedIPv487
AS20764CJSC RASCOMUnclassifiedIPv419
AS207466Sebastien BeaufourUnclassifiedIPv617
AS44529Geely Europe Innovation and Collaboration ABUnclassifiedIPv4 IPv612
AS6206Netrouting B.V.HostingIPv4 IPv67
AS24482SG.GSHostingIPv66

All 21 adjacent →

Provenance

Where this comes from

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