bgpreport

Network · data from 2026-11-12

AS57781 YARTELESERVICE-AS LLC Yarteleservice

Registry name: YARTELESERVICE-AS LLC Yarteleservice, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57781, 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.
176.107.216.0/23 No ROA Nonecovered by 176.107.216.0/22 672 100% 67
91.242.164.0/22 No ROA RIR databaseRIPE 673 100% 66
176.107.210.0/23 No ROA RIR databaseRIPE 673 100% 66
91.242.165.0/24 Valid RIR databaseRIPE 673 100% 66
176.107.208.0/24 Valid RIR databaseRIPE 673 100% 67
176.107.209.0/24 Valid RIR databaseRIPE 673 100% 67
176.107.212.0/24 Valid RIR databaseRIPE 673 100% 67
176.107.214.0/24 Valid RIR databaseRIPE 673 100% 66
176.107.215.0/24 Valid RIR databaseRIPE 673 100% 67
176.107.219.0/24 Valid RIR databaseRIPE 673 100% 67
176.107.220.0/24 Valid RIR databaseRIPE 673 100% 66
176.107.221.0/24 Valid RIR databaseRIPE 673 100% 66
176.107.222.0/24 Valid RIR databaseRIPE 673 100% 66
176.107.223.0/24 Valid RIR databaseRIPE 673 100% 66
192.162.192.0/24 Valid RIR databaseRIPE 673 100% 66
192.162.193.0/24 Valid RIR databaseRIPE 673 100% 66
91.242.166.0/24 Valid RIR databaseRIPE 672 100% 67
91.242.167.0/24 Valid RIR databaseRIPE 672 100% 67
176.107.211.0/24 Valid RIR databaseRIPE 672 100% 66
176.107.213.0/24 Valid RIR databaseRIPE 672 100% 67
176.107.216.0/24 Valid RIR databaseRIPE 672 100% 67
176.107.218.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS57781 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 15 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none176.107.216.0/23No ROA covers it. Add a ROA for AS57781, maxLength 23.672 of 673
Route object: none176.107.216.0/23No route object for it. A route object for 176.107.216.0/22 with origin AS57781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57781 in the RIR database for the space.672 of 673
ROA: none91.242.164.0/22No ROA covers it. Add a ROA for AS57781, maxLength 22.673 of 673
ROA: none176.107.210.0/23No ROA covers it. Add a ROA for AS57781, maxLength 23.673 of 673

Route objects not announced

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

91.242.164.0/24RIPENo ROA
176.107.208.0/21RIPENo ROA
176.107.208.0/23RIPENo ROA
176.107.210.0/24RIPENo ROA
176.107.212.0/22RIPENo ROA
176.107.216.0/22RIPENo ROA
176.107.217.0/24RIPENo ROA
176.107.220.0/22RIPENo ROA
192.162.192.0/22RIPEInvalid: origin
192.162.194.0/24RIPEValid
192.162.195.0/24RIPEValid

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.