bgpreport

Network · data from 2026-11-12

AS34931 Awareness Software Limited

Registry name: AWARESOFT Awareness Software Limited, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34931, 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.
149.255.60.0/22 No ROA Nonecovered by 149.255.56.0/21 669 99% 67
149.255.56.0/22 No ROA Nonecovered by 149.255.56.0/21 666 99% 67
85.159.248.0/21 No ROA RIR databaseRIPE 673 100% 66
93.189.104.0/21 No ROA RIR databaseRIPE 673 100% 67
149.255.56.0/21 No ROA RIR databaseRIPE 673 100% 66
185.7.88.0/22 No ROA RIR databaseRIPE 673 100% 66
89.28.168.0/21 No ROA RIR databaseRIPE 670 100% 67
185.88.108.0/22 No ROA RIR databaseRIPE 668 99% 67
194.9.32.0/23 No ROA RIR databaseRIPE 668 99% 67

AS-SET

AS34931's PeeringDB record names no 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 11 are in fix.csv.

  • ROA: none9
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none149.255.60.0/22No ROA covers it. Add a ROA for AS34931, maxLength 22.669 of 673
Route object: none149.255.60.0/22No route object for it. A route object for 149.255.56.0/21 with origin AS34931 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34931 in the RIR database for the space.669 of 673
ROA: none149.255.56.0/22No ROA covers it. Add a ROA for AS34931, maxLength 22.666 of 673
Route object: none149.255.56.0/22No route object for it. A route object for 149.255.56.0/21 with origin AS34931 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34931 in the RIR database for the space.666 of 673
ROA: none85.159.248.0/21No ROA covers it. Add a ROA for AS34931, maxLength 21.673 of 673
ROA: none93.189.104.0/21No ROA covers it. Add a ROA for AS34931, maxLength 21.673 of 673
ROA: none149.255.56.0/21No ROA covers it. Add a ROA for AS34931, maxLength 21.673 of 673
ROA: none185.7.88.0/22No ROA covers it. Add a ROA for AS34931, maxLength 22.673 of 673
ROA: none89.28.168.0/21No ROA covers it. Add a ROA for AS34931, maxLength 21.670 of 673
ROA: none185.88.108.0/22No ROA covers it. Add a ROA for AS34931, maxLength 22.668 of 673
ROA: none194.9.32.0/23No ROA covers it. Add a ROA for AS34931, maxLength 23.668 of 673

Route objects not announced

Every route object with origin AS34931 is announced.

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.