asn.dev

Observed topology

AS205563 ZGATO

Unclassified RIPE

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

Transit

Upstream networks

All 37

Networks observed carrying traffic for AS205563: 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
AS63473HostHatch, LLCUnclassifiedIPv6553
AS53667FranTech SolutionsHostingIPv6326
AS211619MAXKO d.o.o.HostingIPv6324
AS215120Evolus IT Solutions GmbHUnclassifiedIPv6162
AS56655Gigahost ASUnclassifiedIPv6156
AS152900Onidel Pty LtdUnclassifiedIPv6148
AS210464ANDREW KRISTULIResidentialIPv6144
AS215467Skhron OUHostingIPv6141
AS213683Host.AL ShpkHostingIPv6140
AS3204xTom OUHostingIPv4 IPv6133

All 37 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 37

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

ASNetworkTypeFamiliesPaths seen
AS63473HostHatch, LLCUnclassifiedIPv6553
AS53667FranTech SolutionsHostingIPv6326
AS211619MAXKO d.o.o.HostingIPv6324
AS215120Evolus IT Solutions GmbHUnclassifiedIPv6162
AS56655Gigahost ASUnclassifiedIPv6156
AS152900Onidel Pty LtdUnclassifiedIPv6148
AS210464ANDREW KRISTULIResidentialIPv6144
AS215467Skhron OUHostingIPv6141
AS213683Host.AL ShpkHostingIPv6140
AS3204xTom OUHostingIPv4 IPv6133

All 37 adjacent →

Provenance

Where this comes from

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