bgpreport

Network · data from 2026-11-12

AS30879 RAI Amsterdam B.V.

Registry name: Rai-AS RAI Real Estate B.V., NL · PeeringDB

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

Announced routes

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

83.97.8.0/23 Valid Nonecovered by 83.97.8.0/21 673 100% 67
83.97.12.0/23 Valid Nonecovered by 83.97.8.0/21 673 100% 67
83.97.14.0/23 Valid Nonecovered by 83.97.8.0/21 673 100% 67
195.34.200.0/23 Valid Nonecovered by 195.34.200.0/22 673 100% 67
195.34.202.0/23 Valid Nonecovered by 195.34.200.0/22 673 100% 67
83.97.8.0/21 Valid RIR databaseRADB, RIPE 673 100% 66
195.34.200.0/22 Valid RIR databaseRIPE 673 100% 66
2a11:d940::/29 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS30879'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.

  • Route object: none5
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none83.97.8.0/23No route object for it. A route object for 83.97.8.0/21 with origin AS30879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30879 in the RIR database for the space.673 of 673
Route object: none83.97.12.0/23No route object for it. A route object for 83.97.8.0/21 with origin AS30879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30879 in the RIR database for the space.673 of 673
Route object: none83.97.14.0/23No route object for it. A route object for 83.97.8.0/21 with origin AS30879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30879 in the RIR database for the space.673 of 673
Route object: none195.34.200.0/23No route object for it. A route object for 195.34.200.0/22 with origin AS30879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30879 in the RIR database for the space.673 of 673
Route object: none195.34.202.0/23No route object for it. A route object for 195.34.200.0/22 with origin AS30879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30879 in the RIR database for the space.673 of 673

Route objects not announced

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

83.97.8.0/24RIPEValid
83.97.9.0/24RADB, RIPEValid
83.97.10.0/24RIPEValid
83.97.11.0/24RIPEValid
83.97.12.0/24RADB, RIPEValid
83.97.13.0/24RADB, RIPEValid
83.97.14.0/24RADB, RIPEValid
83.97.15.0/24RADB, RIPEValid
195.34.200.0/24RIPEValid
195.34.201.0/24RIPEValid
195.34.202.0/24RIPEValid
195.34.203.0/24RIPEValid

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.