bgpreport

Network · data from 2026-11-12

AS198479 Nunsys

Registry name: BPLAN Nunsys SA, ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198479, 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.
37.128.169.0/24 No ROA RIR databaseRIPE 671 100% 67
37.128.170.0/24 No ROA RIR databaseRIPE 671 100% 67
37.128.171.0/24 No ROA RIR databaseRIPE 671 100% 67
37.128.172.0/24 No ROA RIR databaseRIPE 671 100% 67
37.128.173.0/24 No ROA RIR databaseRIPE 671 100% 67
37.128.174.0/24 No ROA RIR databaseRIPE 671 100% 67
91.235.108.0/22 No ROA RIR databaseRIPE 671 100% 67
185.5.236.0/23 No ROA RIR databaseRIPE 671 100% 67
185.9.192.0/22 No ROA RIR databaseRIPE 671 100% 67
185.9.193.0/24 No ROA RIR databaseRIPE 671 100% 67
185.9.194.0/24 No ROA RIR databaseRIPE 671 100% 67
185.9.195.0/24 No ROA RIR databaseRIPE 671 100% 67
91.235.48.0/23 Valid Nonecovered by 91.235.48.0/22 672 100% 67
91.235.49.0/24 Valid RIR databaseRIPE 672 100% 67
91.235.51.0/24 Valid RIR databaseRIPE 672 100% 67
37.128.168.0/24 Valid RIR databaseRIPE 671 100% 67
91.235.48.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS198479'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 14 are in fix.csv.

  • ROA: none12
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none37.128.169.0/24No ROA covers it. Add a ROA for AS198479, maxLength 24.671 of 673
ROA: none37.128.170.0/24No ROA covers it. Add a ROA for AS198479, maxLength 24.671 of 673
ROA: none37.128.171.0/24No ROA covers it. Add a ROA for AS198479, maxLength 24.671 of 673
ROA: none37.128.172.0/24No ROA covers it. Add a ROA for AS198479, maxLength 24.671 of 673
ROA: none37.128.173.0/24No ROA covers it. Add a ROA for AS198479, maxLength 24.671 of 673
ROA: none37.128.174.0/24No ROA covers it. Add a ROA for AS198479, maxLength 24.671 of 673
ROA: none91.235.108.0/22No ROA covers it. Add a ROA for AS198479, maxLength 22.671 of 673
ROA: none185.5.236.0/23No ROA covers it. Add a ROA for AS198479, maxLength 23.671 of 673
ROA: none185.9.192.0/22No ROA covers it. Add a ROA for AS198479, maxLength 22.671 of 673
ROA: none185.9.193.0/24No ROA covers it. Add a ROA for AS198479, maxLength 24.671 of 673
ROA: none185.9.194.0/24No ROA covers it. Add a ROA for AS198479, maxLength 24.671 of 673
ROA: none185.9.195.0/24No ROA covers it. Add a ROA for AS198479, maxLength 24.671 of 673
Route object: none91.235.48.0/23No route object for it. A route object for 91.235.48.0/22 with origin AS198479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198479 in the RIR database for the space.672 of 673

Route objects not announced

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

91.235.48.0/22RIPEValid

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.