bgpreport

Network · data from 2026-11-12

AS40311 VIASAT-3 - ViaSat,Inc.

Registry name: VIASAT-3 - ViaSat,Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40311, 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.
201.46.96.0/21 No ROA Nonecovered by 201.46.96.0/20 667 99% 67
138.94.17.0/24 No ROA Other IRR onlyRADB 667 99% 67
138.94.19.0/24 No ROA Other IRR onlyRADB 667 99% 67
45.232.112.0/23 No ROA Other IRR onlyRADB 666 99% 66
45.232.114.0/23 No ROA Other IRR onlyRADB 666 99% 66
8.17.107.0/24 Valid None 673 100% 67
8.17.109.0/24 Valid None 673 100% 67
181.199.212.0/24 Valid RIR databaseLACNIC 666 99% 67
198.45.248.0/23 Valid RIR databaseARIN, RADB 666 99% 67
198.45.250.0/24 Valid RIR databaseARIN, RADB 666 99% 67
190.98.181.0/24 Valid RIR databaseLACNIC 665 99% 67

AS-SET

AS40311 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: none5
  • Route object: none3
  • Route object: RIR4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none201.46.96.0/21No ROA covers it. Add a ROA for AS40311, maxLength 21.667 of 673
Route object: none201.46.96.0/21No route object for it. A route object for 201.46.96.0/20 with origin AS40311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40311 in the RIR database for the space.667 of 673
ROA: none138.94.17.0/24No ROA covers it. Add a ROA for AS40311, maxLength 24.667 of 673
Route object: RIR138.94.17.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none138.94.19.0/24No ROA covers it. Add a ROA for AS40311, maxLength 24.667 of 673
Route object: RIR138.94.19.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.232.112.0/23No ROA covers it. Add a ROA for AS40311, maxLength 23.666 of 673
Route object: RIR45.232.112.0/23Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none45.232.114.0/23No ROA covers it. Add a ROA for AS40311, maxLength 23.666 of 673
Route object: RIR45.232.114.0/23Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: none8.17.107.0/24No route object for it. Add a route object with origin AS40311 in the RIR database for the space.673 of 673
Route object: none8.17.109.0/24No route object for it. Add a route object with origin AS40311 in the RIR database for the space.673 of 673

Route objects not announced

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

45.232.112.0/22RADBNo ROA
201.46.96.0/20RADBNo ROA
2804:4ab8::/32RADBNo 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.