bgpreport

Network · data from 2026-11-12

AS198110 VISTLINK-AS LLC "VISTlink"

Registry name: VISTLINK-AS LLC "VISTlink", RU · not in PeeringDB

13IPv4 routes 0.0% RPKI valid · 92.3% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
13No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS198110, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS198110, 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.
31.186.64.0/20 No ROA Other origin only 672 100% 67
31.186.72.0/24 No ROA RIR databaseRIPE 673 100% 66
31.186.73.0/24 No ROA RIR databaseRIPE 673 100% 66
31.186.74.0/24 No ROA RIR databaseRIPE 673 100% 66
31.186.75.0/24 No ROA RIR databaseRIPE 673 100% 66
31.186.76.0/24 No ROA RIR databaseRIPE 673 100% 66
31.186.77.0/24 No ROA RIR databaseRIPE 673 100% 66
31.186.79.0/24 No ROA RIR databaseRIPE 673 100% 66
185.113.244.0/24 No ROA RIR databaseRIPE 673 100% 66
185.113.245.0/24 No ROA RIR databaseRIPE 673 100% 66
185.113.246.0/24 No ROA RIR databaseRIPE 673 100% 66
185.113.247.0/24 No ROA RIR databaseRIPE 673 100% 66
185.113.244.0/22 No ROA RIR databaseRIPE 672 100% 66

AS-SET

AS198110 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 23 are in fix.csv.

  • ROA: none13
  • Route object: none1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none31.186.64.0/20No ROA covers it. Add a ROA for AS198110, maxLength 20.672 of 673
Route object: none31.186.64.0/20Route objects for it name AS24626. Add a route object with origin AS198110 in the RIR database for the space.672 of 673
ROA: none31.186.72.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none31.186.73.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none31.186.74.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none31.186.75.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none31.186.76.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none31.186.77.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none31.186.79.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none185.113.244.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none185.113.245.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none185.113.246.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none185.113.247.0/24No ROA covers it. Add a ROA for AS198110, maxLength 24.673 of 673
ROA: none185.113.244.0/22No ROA covers it. Add a ROA for AS198110, maxLength 22.672 of 673

Route objects not announced

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

31.186.64.0/24RIPENo ROA
31.186.65.0/24RIPENo ROA
31.186.66.0/24RIPENo ROA
31.186.67.0/24RIPENo ROA
31.186.68.0/24RIPENo ROA
31.186.69.0/24RIPENo ROA
31.186.70.0/24RIPENo ROA
31.186.71.0/24RIPENo ROA
31.186.78.0/24RIPENo ROA

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.