bgpreport

Network · data from 2026-11-12

AS198380 Nova Quadri

Registry name: NOVAQUADRI-AS BLUNOVA S.R.L., IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198380, 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.
185.93.204.0/22 No ROA RIR databaseRIPE 671 100% 67
134.90.240.0/21 Valid RIR databaseRIPE 671 100% 67
185.154.236.0/22 Valid RIR databaseRIPE 671 100% 67
185.211.80.0/22 Valid RIR databaseRIPE 671 100% 67
185.219.86.0/24 Valid RIR databaseRIPE 671 100% 67
185.242.15.0/24 Valid RIR databaseRIPE 671 100% 67
193.24.40.0/23 Valid RIR databaseRIPE 671 100% 67
217.196.138.0/23 Valid RIR databaseRIPE 671 100% 67
134.90.240.0/22 Valid RIR databaseRIPE 3 0%low visibility 3
134.90.244.0/22 Valid RIR databaseRIPE 3 0%low visibility 3
185.211.80.0/23 Valid RIR databaseRIPE 3 0%low visibility 3
185.211.82.0/23 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

AS198380'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 32 are in fix.csv.

  • ROA: none1
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: none185.93.204.0/22No ROA covers it. Add a ROA for AS198380, maxLength 22.671 of 673

Route objects not announced

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

134.90.240.0/23RIPEValid
134.90.240.0/24RIPEValid
134.90.241.0/24RIPEValid
134.90.242.0/23RIPEValid
134.90.242.0/24RIPEValid
134.90.243.0/24RIPEValid
134.90.244.0/23RIPEValid
134.90.244.0/24RIPEValid
134.90.245.0/24RIPEValid
134.90.246.0/23RIPEValid
134.90.246.0/24RIPEValid
134.90.247.0/24RIPEValid
185.93.204.0/24RIPENo ROA
185.93.205.0/24RIPENo ROA
185.93.206.0/24RIPENo ROA
185.93.207.0/24RIPENo ROA
185.154.236.0/23RIPEValid
185.154.236.0/24RIPEValid
185.154.237.0/24RIPEValid
185.154.238.0/23RIPEValid
185.154.238.0/24RIPEValid
185.154.239.0/24RIPEValid
185.211.80.0/24RIPEValid
185.211.81.0/24RIPEValid
185.211.82.0/24RIPEValid
185.211.83.0/24RIPEValid
193.24.40.0/22RIPENo ROA
193.24.40.0/24RIPEValid
193.24.41.0/24RIPEValid
217.196.138.0/24RIPEValid
217.196.139.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.