asn.dev

Observed topology

AS60349 VARTEH-AS Varteh Ltd

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60349: 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
AS8717A1 Bulgaria EADResidentialIPv4 IPv667
AS9002RETN LimitedUnclassifiedIPv4 IPv641
AS174Cogent Communications, LLCTransitIPv4 IPv618

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS16154Telecoms-Net Ltd.UnclassifiedIPv4 IPv6794
AS61437Alex Escape LLCUnclassifiedIPv438
AS57619Varna Data Center EOODUnclassifiedIPv435
AS60092FIXITY LLCUnclassifiedIPv4 IPv623
AS62110Leader PI CI Ltd.UnclassifiedIPv412
AS41019Burgasnet LTDUnclassifiedIPv43
AS207772Top Net BG LTDUnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS16154Telecoms-Net Ltd.UnclassifiedIPv4 IPv6796
AS9002RETN LimitedUnclassifiedIPv4 IPv6548
AS174Cogent Communications, LLCTransitIPv4 IPv6448
AS8717A1 Bulgaria EADResidentialIPv4 IPv6101
AS57619Varna Data Center EOODUnclassifiedIPv488
AS61437Alex Escape LLCUnclassifiedIPv438
AS60092FIXITY LLCUnclassifiedIPv4 IPv631
AS62110Leader PI CI Ltd.UnclassifiedIPv412
AS41019Burgasnet LTDUnclassifiedIPv43
AS207772Top Net BG LTDUnclassifiedIPv43

Provenance

Where this comes from

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