asn.dev

Observed topology

AS60733 PERKE-NET

Unclassified RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60733: 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
AS13004Serbian Open Exchange DOOUnclassifiedIPv4 IPv6165
AS6204INTERKVM HOST SRLUnclassifiedIPv4 IPv627
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv619
AS6939Hurricane Electric LLCTransitIPv410
AS3257GTT Communications Inc.TransitIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50872LOCALHOST d.o.o.UnclassifiedIPv421
AS200305Sasa RisticUnclassifiedIPv618
AS47267Serbian National Internet Domain Registry FoundationUnclassifiedIPv4 IPv610
AS198691SPACE Admins d.o.o.UnclassifiedIPv46
AS13004Serbian Open Exchange DOOUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13004Serbian Open Exchange DOOUnclassifiedIPv4 IPv6189
AS6204INTERKVM HOST SRLUnclassifiedIPv4 IPv644
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv640
AS50872LOCALHOST d.o.o.UnclassifiedIPv421
AS200305Sasa RisticUnclassifiedIPv618
AS3257GTT Communications Inc.TransitIPv4 IPv612
AS6939Hurricane Electric LLCTransitIPv410
AS47267Serbian National Internet Domain Registry FoundationUnclassifiedIPv4 IPv610
AS198691SPACE Admins d.o.o.UnclassifiedIPv46

Provenance

Where this comes from

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