asn.dev

Observed topology

AS210220 ICTFUTURE

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210220: 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
AS12741Netia SAResidentialIPv4 IPv6396
AS12912T-Mobile Polska S.A.UnclassifiedIPv4 IPv624
AS3356Level 3 Parent, LLCTransitIPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS2096194 Military Clinical Hospital with Polyclinic Independent Public Health Care Facility in WroclawUnclassifiedIPv454
AS197494Polskie Radio-Regionalna Rozglosnia we Wroclawiu-Radio Wroclaw-Spolka AkcyjnaUnclassifiedIPv442
AS57295Marcin WlodarczakUnclassifiedIPv619
AS199845INVENT Sp. z o.o.UnclassifiedIPv46
AS31106Wroclawski Park Technologiczny S.A.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12741Netia SAResidentialIPv4 IPv6506
AS2096194 Military Clinical Hospital with Polyclinic Independent Public Health Care Facility in WroclawUnclassifiedIPv454
AS197494Polskie Radio-Regionalna Rozglosnia we Wroclawiu-Radio Wroclaw-Spolka AkcyjnaUnclassifiedIPv442
AS12912T-Mobile Polska S.A.UnclassifiedIPv4 IPv636
AS57295Marcin WlodarczakUnclassifiedIPv619
AS3356Level 3 Parent, LLCTransitIPv68
AS199845INVENT Sp. z o.o.UnclassifiedIPv46
AS31106Wroclawski Park Technologiczny S.A.UnclassifiedIPv41

Provenance

Where this comes from

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