asn.dev

Observed topology

AS60602 INOVARE-AS str. Uzinelor 21 of. 37

Hosting RIPE Content

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS60602: 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
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6246
AS9002RETN LimitedUnclassifiedIPv4 IPv6212
AS174Cogent Communications, LLCTransitIPv4 IPv6200
AS57463NetIX Communications JSCUnclassifiedIPv4 IPv6128
AS6939Hurricane Electric LLCTransitIPv498
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv616
AS34019Hivane AssociationUnclassifiedIPv4 IPv616
AS401753BIXCE IncUnclassifiedIPv4 IPv616
AS20764CJSC RASCOMUnclassifiedIPv414

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208414WEDOS Internet, a.s.HostingIPv640
AS34529GLOBAL NETWORK TECHNOLOGY SRLUnclassifiedIPv415

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6261
AS9002RETN LimitedUnclassifiedIPv4 IPv6217
AS174Cogent Communications, LLCTransitIPv4 IPv6202
AS57463NetIX Communications JSCUnclassifiedIPv4 IPv6151
AS6939Hurricane Electric LLCTransitIPv498
AS208414WEDOS Internet, a.s.HostingIPv640
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv631
AS24482SG.GSHostingIPv4 IPv618
AS401753BIXCE IncUnclassifiedIPv4 IPv618
AS34019Hivane AssociationUnclassifiedIPv4 IPv617

All 16 adjacent →

Provenance

Where this comes from

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