bgpreport

Network · data from 2026-11-12

AS35051 Nexi-as Nexi Payments S.P.A.

Registry name: Nexi-as Nexi Payments S.P.A., IT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35051, 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.198.116.0/24 No ROA Other IRR onlyRADB 672 100% 67
185.198.117.0/24 No ROA Other IRR onlyRADB 672 100% 67
185.198.118.0/24 No ROA Other IRR onlyRADB 672 100% 67
185.198.119.0/24 No ROA Other IRR onlyRADB 672 100% 67
193.108.60.0/24 No ROA Other IRR onlyRADB 672 100% 67
193.108.61.0/24 No ROA Other IRR onlyRADB 672 100% 67
193.108.62.0/24 No ROA Other IRR onlyRADB 672 100% 67
193.108.63.0/24 No ROA Other IRR onlyRADB 672 100% 67
185.198.116.0/22 No ROA RIR databaseRIPE 671 100% 67
193.108.60.0/22 No ROA RIR databaseRIPE 671 100% 67

AS-SET

AS35051 isn't in PeeringDB, where networks name their 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 18 are in fix.csv.

  • ROA: none10
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none185.198.116.0/24No ROA covers it. Add a ROA for AS35051, maxLength 24.672 of 673
Route object: RIR185.198.116.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none185.198.117.0/24No ROA covers it. Add a ROA for AS35051, maxLength 24.672 of 673
Route object: RIR185.198.117.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none185.198.118.0/24No ROA covers it. Add a ROA for AS35051, maxLength 24.672 of 673
Route object: RIR185.198.118.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none185.198.119.0/24No ROA covers it. Add a ROA for AS35051, maxLength 24.672 of 673
Route object: RIR185.198.119.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none193.108.60.0/24No ROA covers it. Add a ROA for AS35051, maxLength 24.672 of 673
Route object: RIR193.108.60.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none193.108.61.0/24No ROA covers it. Add a ROA for AS35051, maxLength 24.672 of 673
Route object: RIR193.108.61.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none193.108.62.0/24No ROA covers it. Add a ROA for AS35051, maxLength 24.672 of 673
Route object: RIR193.108.62.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none193.108.63.0/24No ROA covers it. Add a ROA for AS35051, maxLength 24.672 of 673
Route object: RIR193.108.63.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none185.198.116.0/22No ROA covers it. Add a ROA for AS35051, maxLength 22.671 of 673
ROA: none193.108.60.0/22No ROA covers it. Add a ROA for AS35051, maxLength 22.671 of 673

Route objects not announced

Every route object with origin AS35051 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.