bgpreport

Network · data from 2026-11-12

AS39887 Televideocom

Registry name: TELEVIDEOCOM-AS Televideocom Srl, IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39887, 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.

89.188.128.0/19 No ROA Other origin only 673 100% 67
89.188.128.0/24 No ROA None 673 100% 67
89.188.129.0/24 No ROA None 673 100% 67
89.188.130.0/24 No ROA None 673 100% 67
89.188.131.0/24 No ROA None 673 100% 67
89.188.132.0/22 No ROA None 673 100% 67
89.188.136.0/24 No ROA None 673 100% 67
89.188.137.0/24 No ROA None 673 100% 67
89.188.138.0/24 No ROA None 673 100% 67
89.188.139.0/24 No ROA None 673 100% 67
89.188.140.0/24 No ROA None 673 100% 67
89.188.141.0/24 No ROA None 673 100% 67
89.188.142.0/24 No ROA None 673 100% 67
89.188.143.0/24 No ROA None 673 100% 67
89.188.144.0/24 No ROA None 673 100% 67

AS-SET

AS39887'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 31 are in fix.csv.

  • ROA: none15
  • Route object: none15
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none89.188.128.0/19No ROA covers it. Add a ROA for AS39887, maxLength 19.673 of 673
Route object: none89.188.128.0/19Route objects for it name AS19905. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.128.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.128.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.129.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.129.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.130.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.130.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.131.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.131.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.132.0/22No ROA covers it. Add a ROA for AS39887, maxLength 22.673 of 673
Route object: none89.188.132.0/22No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.136.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.136.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.137.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.137.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.138.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.138.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.139.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.139.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.140.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.140.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.141.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.141.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.142.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.142.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.143.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.143.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673
ROA: none89.188.144.0/24No ROA covers it. Add a ROA for AS39887, maxLength 24.673 of 673
Route object: none89.188.144.0/24No route object for it. Add a route object with origin AS39887 in the RIR database for the space.673 of 673

Route objects not announced

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

89.188.159.0/24RIPENo 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.