bgpreport

Network · data from 2026-11-12

AS201073 yes-as YES TV AND COMMUNICATIONS SERVICES LTD

Registry name: yes-as YES TV AND COMMUNICATIONS SERVICES LTD, IL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201073, 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.
185.86.204.0/24 No ROA RIR databaseRIPE 33 5%low visibility 27
185.86.205.0/24 No ROA RIR databaseRIPE 33 5%low visibility 27
185.86.206.0/24 Valid RIR databaseRIPE 673 100% 67
2a05:bb80::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS201073 isn't in PeeringDB, where networks name their 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 14 are in fix.csv.

  • ROA: none2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none185.86.204.0/24No ROA covers it. Add a ROA for AS201073, maxLength 24.33 of 673
ROA: none185.86.205.0/24No ROA covers it. Add a ROA for AS201073, maxLength 24.33 of 673

Route objects not announced

Route objects with origin AS201073 whose prefix no peer sees AS201073 announce. Many are kept on purpose (backup routes, space announced only in some places).

185.86.204.0/22RIPENo ROA
185.86.204.0/23RIPENo ROA
185.86.206.0/23RIPENo ROA
185.86.207.0/24RIPENo ROA
2a05:bb80:4::/48RIPEValid
2a05:bb80:5::/48RIPEValid
2a05:bb80:9::/48RIPEValid
2a05:bb80:a::/48RIPEValid
2a05:bb80:f::/48RIPEValid
2a05:bb80:10::/48RIPEValid
2a05:bb80:15::/48RIPEValid
2a05:bb80:16::/48RIPEValid

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.