bgpreport

Network · data from 2026-11-12

AS209535 ITEGAL ITEGAL SERVICIOS TIC S.L.

Registry name: ITEGAL ITEGAL SERVICIOS TIC S.L., ES · not in PeeringDB

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

Announced routes

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

154.60.108.0/24 No ROA Nonecovered by 154.60.108.0/22 673 100% 67
154.60.109.0/24 No ROA Nonecovered by 154.60.108.0/22 673 100% 67
154.60.110.0/24 No ROA Nonecovered by 154.60.108.0/22 673 100% 67
154.60.111.0/24 No ROA Nonecovered by 154.60.108.0/22 673 100% 67
149.36.200.0/24 No ROA Other IRR onlyRADB 673 100% 67
149.36.201.0/24 No ROA Other IRR onlyRADB 673 100% 67
149.36.202.0/24 No ROA Other IRR onlyRADB 673 100% 67
149.36.203.0/24 No ROA Other IRR onlyRADB 673 100% 67
149.36.200.0/22 No ROA Other IRR onlyRADB 672 100% 67
154.60.108.0/22 No ROA Other IRR onlyRADB 672 100% 67
147.78.24.0/24 Valid Nonecovered by 147.78.24.0/22 673 100% 67
147.78.25.0/24 Valid Nonecovered by 147.78.24.0/22 673 100% 67
147.78.26.0/24 Valid Nonecovered by 147.78.24.0/22 673 100% 67
147.78.27.0/24 Valid Nonecovered by 147.78.24.0/22 673 100% 67
193.33.6.0/24 Valid Nonecovered by 193.33.6.0/23 673 100% 67
193.33.7.0/24 Valid Nonecovered by 193.33.6.0/23 673 100% 67
193.33.40.0/24 Valid Nonecovered by 193.33.40.0/23 673 100% 67
193.33.41.0/24 Valid Nonecovered by 193.33.40.0/23 673 100% 67
212.163.20.0/24 Valid RIR databaseRIPE 673 100% 67
212.163.21.0/24 Valid RIR databaseRIPE 673 100% 67
212.163.22.0/24 Valid RIR databaseRIPE 673 100% 67
212.163.23.0/24 Valid RIR databaseRIPE 673 100% 67
212.163.36.0/24 Valid RIR databaseRIPE 673 100% 67
212.163.37.0/24 Valid RIR databaseRIPE 673 100% 67
212.163.38.0/24 Valid RIR databaseRIPE 673 100% 67
212.163.39.0/24 Valid RIR databaseRIPE 673 100% 67
45.92.24.0/22 Valid RIR databaseRIPE 672 100% 67
45.92.24.0/24 Valid RIR databaseRIPE 672 100% 67
45.92.25.0/24 Valid RIR databaseRIPE 672 100% 67
45.92.26.0/24 Valid RIR databaseRIPE 672 100% 67
45.92.27.0/24 Valid RIR databaseRIPE 672 100% 67
147.78.24.0/22 Valid RIR databaseRIPE 672 100% 67
193.33.6.0/23 Valid RIR databaseRIPE 672 100% 67
193.33.40.0/23 Valid RIR databaseRIPE 672 100% 67
212.163.20.0/22 Valid RIR databaseRIPE 672 100% 67
212.163.36.0/22 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS209535 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 34 are in fix.csv.

  • ROA: none10
  • Route object: none12
  • Route object: RIR6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none154.60.108.0/24No ROA covers it. Add a ROA for AS209535, maxLength 24.673 of 673
Route object: none154.60.108.0/24No route object for it. A route object for 154.60.108.0/22 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
ROA: none154.60.109.0/24No ROA covers it. Add a ROA for AS209535, maxLength 24.673 of 673
Route object: none154.60.109.0/24No route object for it. A route object for 154.60.108.0/22 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
ROA: none154.60.110.0/24No ROA covers it. Add a ROA for AS209535, maxLength 24.673 of 673
Route object: none154.60.110.0/24No route object for it. A route object for 154.60.108.0/22 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
ROA: none154.60.111.0/24No ROA covers it. Add a ROA for AS209535, maxLength 24.673 of 673
Route object: none154.60.111.0/24No route object for it. A route object for 154.60.108.0/22 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
ROA: none149.36.200.0/24No ROA covers it. Add a ROA for AS209535, maxLength 24.673 of 673
Route object: RIR149.36.200.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.36.201.0/24No ROA covers it. Add a ROA for AS209535, maxLength 24.673 of 673
Route object: RIR149.36.201.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.36.202.0/24No ROA covers it. Add a ROA for AS209535, maxLength 24.673 of 673
Route object: RIR149.36.202.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.36.203.0/24No ROA covers it. Add a ROA for AS209535, maxLength 24.673 of 673
Route object: RIR149.36.203.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.36.200.0/22No ROA covers it. Add a ROA for AS209535, maxLength 22.672 of 673
Route object: RIR149.36.200.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.60.108.0/22No ROA covers it. Add a ROA for AS209535, maxLength 22.672 of 673
Route object: RIR154.60.108.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none147.78.24.0/24No route object for it. A route object for 147.78.24.0/22 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
Route object: none147.78.25.0/24No route object for it. A route object for 147.78.24.0/22 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
Route object: none147.78.26.0/24No route object for it. A route object for 147.78.24.0/22 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
Route object: none147.78.27.0/24No route object for it. A route object for 147.78.24.0/22 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
Route object: none193.33.6.0/24No route object for it. A route object for 193.33.6.0/23 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
Route object: none193.33.7.0/24No route object for it. A route object for 193.33.6.0/23 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
Route object: none193.33.40.0/24No route object for it. A route object for 193.33.40.0/23 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673
Route object: none193.33.41.0/24No route object for it. A route object for 193.33.40.0/23 with origin AS209535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209535 in the RIR database for the space.673 of 673

Route objects not announced

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

149.36.200.0/23RADBNo ROA
149.36.202.0/23RADBNo ROA
212.163.20.0/23RIPEValid
212.163.22.0/23RIPEValid
212.163.36.0/23RIPEValid
212.163.38.0/23RIPEValid

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.