bgpreport

Network · data from 2026-11-12

AS60349 Varteh Ltd

Registry name: VARTEH-AS Varteh LTD, BG · PeeringDB

6IPv4 routes 100.0% RPKI valid · 66.7% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS60349, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS60349, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
194.38.36.0/23 Valid Nonecovered by 194.38.36.0/22 87 13% 36
194.38.38.0/23 Valid Nonecovered by 194.38.36.0/22 87 13% 36
194.38.36.0/22 Valid RIR databaseRIPE 672 100% 66
2a09:6d40::/31 Valid RIR databaseRIPE 634 100% 70
2a09:6d40::/32 Valid RIR databaseRIPE 349 55% 64
194.38.36.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
194.38.38.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
194.38.39.0/24 Valid RIR databaseRIPE 2 0%low visibility 3

AS-SET

AS60349's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none194.38.36.0/23No route object for it. A route object for 194.38.36.0/22 with origin AS60349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60349 in the RIR database for the space.87 of 673
Route object: none194.38.38.0/23No route object for it. A route object for 194.38.36.0/22 with origin AS60349 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60349 in the RIR database for the space.87 of 673

Route objects not announced

Every route object with origin AS60349 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.