bgpreport

Network · data from 2026-11-12

AS47191 BlueTech-WAF blue tech technology Co., Limited

Registry name: BlueTech-WAF blue tech technology Co., Limited, VG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47191, 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.

85.149.236.0/22 Valid None 671 100% 67
37.77.82.0/23 Valid Nonecovered by 37.77.80.0/22 656 97% 67
37.77.84.0/23 Valid Nonecovered by 37.77.80.0/21 656 97% 67
37.77.86.0/23 Valid Nonecovered by 37.77.80.0/21 656 97% 67
37.77.82.0/24 Valid Nonecovered by 37.77.80.0/22 7 1%low visibility 4
37.77.83.0/24 Valid Nonecovered by 37.77.80.0/22 7 1%low visibility 4
37.77.84.0/24 Valid Nonecovered by 37.77.80.0/21 7 1%low visibility 4
37.77.85.0/24 Valid Nonecovered by 37.77.80.0/21 7 1%low visibility 4
37.77.86.0/24 Valid Nonecovered by 37.77.80.0/21 7 1%low visibility 4
37.77.87.0/24 Valid Nonecovered by 37.77.80.0/21 7 1%low visibility 4
74.113.236.0/24 Valid Other origin onlycovered by 74.113.236.0/23 7 1%low visibility 4
74.113.237.0/24 Valid Nonecovered by 74.113.236.0/23 7 1%low visibility 4
85.149.232.0/24 Valid Nonecovered by 85.149.232.0/23 7 1%low visibility 4
85.149.233.0/24 Valid Nonecovered by 85.149.232.0/23 7 1%low visibility 4
85.149.234.0/24 Valid Nonecovered by 85.149.234.0/23 7 1%low visibility 4
85.149.235.0/24 Valid Nonecovered by 85.149.234.0/23 7 1%low visibility 4
85.149.236.0/23 Valid None 7 1%low visibility 4
85.149.238.0/23 Valid None 7 1%low visibility 4
37.77.80.0/21 Valid Other IRR onlyRADB 672 100% 67
216.180.224.0/20 Valid Other IRR onlyRADB 672 100% 67
85.149.232.0/23 Valid Other IRR onlyRADB 669 99% 67
85.149.234.0/23 Valid Other IRR onlyRADB 669 99% 67
74.113.236.0/23 Valid Other IRR onlyRADB 656 97% 67

AS-SET

AS47191 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 24 are in fix.csv.

  • Route object: none18
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none85.149.236.0/22No route object for it. Add a route object with origin AS47191 in the RIR database for the space.671 of 673
Route object: none37.77.82.0/23No route object for it. A route object for 37.77.80.0/22 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.656 of 673
Route object: none37.77.84.0/23No route object for it. A route object for 37.77.80.0/21 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.656 of 673
Route object: none37.77.86.0/23No route object for it. A route object for 37.77.80.0/21 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.656 of 673
Route object: none37.77.82.0/24No route object for it. A route object for 37.77.80.0/22 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none37.77.83.0/24No route object for it. A route object for 37.77.80.0/22 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none37.77.84.0/24No route object for it. A route object for 37.77.80.0/21 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none37.77.85.0/24No route object for it. A route object for 37.77.80.0/21 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none37.77.86.0/24No route object for it. A route object for 37.77.80.0/21 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none37.77.87.0/24No route object for it. A route object for 37.77.80.0/21 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none74.113.236.0/24Route objects for it name AS40065. A route object for 74.113.236.0/23 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none74.113.237.0/24No route object for it. A route object for 74.113.236.0/23 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none85.149.232.0/24No route object for it. A route object for 85.149.232.0/23 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none85.149.233.0/24No route object for it. A route object for 85.149.232.0/23 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none85.149.234.0/24No route object for it. A route object for 85.149.234.0/23 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none85.149.235.0/24No route object for it. A route object for 85.149.234.0/23 with origin AS47191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none85.149.236.0/23No route object for it. Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: none85.149.238.0/23No route object for it. Add a route object with origin AS47191 in the RIR database for the space.7 of 673
Route object: RIR37.77.80.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR216.180.224.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR85.149.232.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR85.149.234.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR74.113.236.0/23Route object only in RADB. Add it in the RIR database for the space.656 of 673

Route objects not announced

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

37.77.80.0/22RADBValid

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.