bgpreport

Network · data from 2026-11-12

AS48847 WAVES

Registry name: Connect WAVES S.A.L, LB · PeeringDB

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

Announced routes

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

38.77.56.0/22 No ROA None 673 100% 67
147.78.44.0/24 Valid RIR databaseRIPE 673 100% 67
185.12.220.0/22 Valid RIR databaseRIPE 673 100% 67
185.104.68.0/22 Valid RIR databaseRIPE 673 100% 67
185.104.68.0/24 Valid RIR databaseRIPE 673 100% 67
185.104.70.0/24 Valid RIR databaseRIPE 673 100% 67
185.104.71.0/24 Valid RIR databaseRIPE 673 100% 67
185.176.208.0/22 Valid RIR databaseRIPE 673 100% 67
185.176.208.0/24 Valid RIR databaseRIPE 673 100% 67
185.176.210.0/24 Valid RIR databaseRIPE 673 100% 67
185.176.211.0/24 Valid RIR databaseRIPE 673 100% 67
193.84.114.0/23 Valid RIR databaseRIPE 673 100% 67
193.84.118.0/24 Valid RIR databaseRIPE 673 100% 67
185.83.86.0/24 Valid RIR databaseRIPE 672 100% 67
185.176.209.0/24 Valid RIR databaseRIPE 672 100% 67
109.233.16.0/21 Valid RIR databaseRIPE 671 100% 67
2a03:6900::/32 Valid RIR databaseRIPE 636 100% 67
2a06:3480::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS48847'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 17 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none38.77.56.0/22No ROA covers it. Add a ROA for AS48847, maxLength 22.673 of 673
Route object: none38.77.56.0/22No route object for it. Add a route object with origin AS48847 in the RIR database for the space.673 of 673

Route objects not announced

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

109.233.16.0/24RIPEValid
109.233.17.0/24RIPEValid
109.233.18.0/24RIPEValid
109.233.19.0/24RIPEValid
109.233.20.0/24RIPEValid
109.233.21.0/24RIPEValid
109.233.22.0/24RIPEValid
109.233.23.0/24RIPEValid
147.78.45.0/24RIPEValid
185.12.221.0/24RIPEValid
185.12.222.0/24RIPEValid
185.12.223.0/24RIPEValid
193.84.114.0/24RIPEValid
193.84.115.0/24RIPEValid
193.84.118.0/23RIPENo 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.