bgpreport

Network · data from 2026-11-12

AS200583 InfoCert TINEXTA INFOCERT S.p.A

Registry name: InfoCert TINEXTA INFOCERT S.p.A, IT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200583, 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.34.249.0/24 Invalid: maxLength Nonecovered by 185.34.248.0/22 93 14% 39
185.247.212.0/24 No ROA Nonecovered by 185.247.212.0/22 673 100% 67
185.247.214.0/24 No ROA Nonecovered by 185.247.212.0/22 673 100% 67
185.247.215.0/24 No ROA Nonecovered by 185.247.212.0/22 673 100% 67
81.173.37.0/24 No ROA Nonecovered by 81.173.36.0/22 672 100% 67
185.247.212.0/22 No ROA RIR databaseRIPE 673 100% 67
81.173.36.0/22 No ROA RIR databaseRIPE 671 100% 67
185.102.40.0/22 No ROA RIR databaseRIPE 671 100% 67
185.34.248.0/24 Valid Nonecovered by 185.34.248.0/22 671 100% 67
185.34.248.0/22 Valid RIR databaseRIPE 673 100% 67
185.34.251.0/24 Valid RIR databaseRIPE 673 100% 70
185.102.41.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: maxLength1
  • ROA: none7
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: maxLength185.34.249.0/24ROA 185.34.248.0/22 AS200583 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 185.34.249.0/24.93 of 673
Route object: none185.34.249.0/24No route object for it. A route object for 185.34.248.0/22 with origin AS200583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200583 in the RIR database for the space.93 of 673
ROA: none185.247.212.0/24No ROA covers it. Add a ROA for AS200583, maxLength 24.673 of 673
Route object: none185.247.212.0/24No route object for it. A route object for 185.247.212.0/22 with origin AS200583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200583 in the RIR database for the space.673 of 673
ROA: none185.247.214.0/24No ROA covers it. Add a ROA for AS200583, maxLength 24.673 of 673
Route object: none185.247.214.0/24No route object for it. A route object for 185.247.212.0/22 with origin AS200583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200583 in the RIR database for the space.673 of 673
ROA: none185.247.215.0/24No ROA covers it. Add a ROA for AS200583, maxLength 24.673 of 673
Route object: none185.247.215.0/24No route object for it. A route object for 185.247.212.0/22 with origin AS200583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200583 in the RIR database for the space.673 of 673
ROA: none81.173.37.0/24No ROA covers it. Add a ROA for AS200583, maxLength 24.672 of 673
Route object: none81.173.37.0/24No route object for it. A route object for 81.173.36.0/22 with origin AS200583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200583 in the RIR database for the space.672 of 673
ROA: none185.247.212.0/22No ROA covers it. Add a ROA for AS200583, maxLength 22.673 of 673
ROA: none81.173.36.0/22No ROA covers it. Add a ROA for AS200583, maxLength 22.671 of 673
ROA: none185.102.40.0/22No ROA covers it. Add a ROA for AS200583, maxLength 22.671 of 673
Route object: none185.34.248.0/24No route object for it. A route object for 185.34.248.0/22 with origin AS200583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200583 in the RIR database for the space.671 of 673

Route objects not announced

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