asn.dev

Observed topology

AS60592 GRANSY Gransy s.r.o. gransy.com

Hosting RIPE Content

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS60592: 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
AS15685CASABLANCA INT a.s.HostingIPv4 IPv6395
AS20473The Constant Company, LLCHostingIPv4 IPv6287
AS29134Webglobe, s.r.o.HostingIPv4236
AS43541VSHosting s.r.o.HostingIPv4 IPv6209
AS39122Blacknight Internet Solutions LimitedHostingIPv4 IPv621
AS6939Hurricane Electric LLCTransitIPv46
AS13004Serbian Open Exchange DOOUnclassifiedIPv44
AS23961Misaka Network, Inc.UnclassifiedIPv4 IPv64
AS41095IPTP LTDHostingIPv44
AS50338GamerHost s.r.o.HostingIPv4 IPv63

All 13 upstreams →

Transit

Downstream networks

inferred

Networks for which AS60592 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 13

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

ASNetworkTypeFamiliesPaths seen
AS15685CASABLANCA INT a.s.HostingIPv4 IPv6395
AS20473The Constant Company, LLCHostingIPv4 IPv6287
AS29134Webglobe, s.r.o.HostingIPv4236
AS43541VSHosting s.r.o.HostingIPv4 IPv6209
AS39122Blacknight Internet Solutions LimitedHostingIPv4 IPv621
AS6939Hurricane Electric LLCTransitIPv46
AS13004Serbian Open Exchange DOOUnclassifiedIPv44
AS23961Misaka Network, Inc.UnclassifiedIPv4 IPv64
AS41095IPTP LTDHostingIPv44
AS50338GamerHost s.r.o.HostingIPv4 IPv63

All 13 adjacent →

Provenance

Where this comes from

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