bgpreport

Network · data from 2026-11-12

AS41160 Amt Services srl

Registry name: ORIGINENET-AS Amt Services srl, IT · PeeringDB

16IPv4 routes 0.0% RPKI valid · 93.8% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
16No 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 AS41160, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41160, 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.116.0.0/22 No ROA Other origin only 673 100% 67
89.207.104.0/24 No ROA RIR databaseRIPE 673 100% 67
89.207.105.0/24 No ROA RIR databaseRIPE 673 100% 67
89.207.106.0/24 No ROA RIR databaseRIPE 673 100% 67
89.207.107.0/24 No ROA RIR databaseRIPE 673 100% 67
89.207.108.0/24 No ROA RIR databaseRIPE 673 100% 67
89.207.109.0/24 No ROA RIR databaseRIPE 673 100% 67
89.207.110.0/24 No ROA RIR databaseRIPE 673 100% 67
89.207.111.0/24 No ROA RIR databaseRIPE 673 100% 67
159.253.184.0/21 No ROA RIR databaseRIPE 673 100% 67
185.64.204.0/22 No ROA RIR databaseRIPE 673 100% 67
185.205.164.0/23 No ROA RIR databaseRIPE 673 100% 67
185.205.166.0/24 No ROA RIR databaseRIPE 673 100% 67
185.205.167.0/24 No ROA RIR databaseRIPE 673 100% 67
185.225.216.0/23 No ROA RIR databaseRIPE 673 100% 67
185.225.218.0/23 No ROA RIR databaseRIPE 673 100% 67

AS-SET

AS41160'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 18 are in fix.csv.

  • ROA: none16
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.116.0.0/22No ROA covers it. Add a ROA for AS41160, maxLength 22.673 of 673
Route object: none185.116.0.0/22Route objects for it name AS204060. Add a route object with origin AS41160 in the RIR database for the space.673 of 673
ROA: none89.207.104.0/24No ROA covers it. Add a ROA for AS41160, maxLength 24.673 of 673
ROA: none89.207.105.0/24No ROA covers it. Add a ROA for AS41160, maxLength 24.673 of 673
ROA: none89.207.106.0/24No ROA covers it. Add a ROA for AS41160, maxLength 24.673 of 673
ROA: none89.207.107.0/24No ROA covers it. Add a ROA for AS41160, maxLength 24.673 of 673
ROA: none89.207.108.0/24No ROA covers it. Add a ROA for AS41160, maxLength 24.673 of 673
ROA: none89.207.109.0/24No ROA covers it. Add a ROA for AS41160, maxLength 24.673 of 673
ROA: none89.207.110.0/24No ROA covers it. Add a ROA for AS41160, maxLength 24.673 of 673
ROA: none89.207.111.0/24No ROA covers it. Add a ROA for AS41160, maxLength 24.673 of 673
ROA: none159.253.184.0/21No ROA covers it. Add a ROA for AS41160, maxLength 21.673 of 673
ROA: none185.64.204.0/22No ROA covers it. Add a ROA for AS41160, maxLength 22.673 of 673
ROA: none185.205.164.0/23No ROA covers it. Add a ROA for AS41160, maxLength 23.673 of 673
ROA: none185.205.166.0/24No ROA covers it. Add a ROA for AS41160, maxLength 24.673 of 673
ROA: none185.205.167.0/24No ROA covers it. Add a ROA for AS41160, maxLength 24.673 of 673
ROA: none185.225.216.0/23No ROA covers it. Add a ROA for AS41160, maxLength 23.673 of 673
ROA: none185.225.218.0/23No ROA covers it. Add a ROA for AS41160, maxLength 23.673 of 673

Route objects not announced

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

89.207.104.0/21RIPENo 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.