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
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% |
| 154.60.109.0/24 | No ROA | Nonecovered by 154.60.108.0/22 | 673 100% |
| 154.60.110.0/24 | No ROA | Nonecovered by 154.60.108.0/22 | 673 100% |
| 154.60.111.0/24 | No ROA | Nonecovered by 154.60.108.0/22 | 673 100% |
| 149.36.200.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 149.36.201.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 149.36.202.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 149.36.203.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 149.36.200.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 154.60.108.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 147.78.24.0/24 | Valid | Nonecovered by 147.78.24.0/22 | 673 100% |
| 147.78.25.0/24 | Valid | Nonecovered by 147.78.24.0/22 | 673 100% |
| 147.78.26.0/24 | Valid | Nonecovered by 147.78.24.0/22 | 673 100% |
| 147.78.27.0/24 | Valid | Nonecovered by 147.78.24.0/22 | 673 100% |
| 193.33.6.0/24 | Valid | Nonecovered by 193.33.6.0/23 | 673 100% |
| 193.33.7.0/24 | Valid | Nonecovered by 193.33.6.0/23 | 673 100% |
| 193.33.40.0/24 | Valid | Nonecovered by 193.33.40.0/23 | 673 100% |
| 193.33.41.0/24 | Valid | Nonecovered by 193.33.40.0/23 | 673 100% |
| 212.163.20.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.163.21.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.163.22.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.163.23.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.163.36.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.163.37.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.163.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.163.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.92.24.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 45.92.24.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.92.25.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.92.26.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.92.27.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 147.78.24.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.33.6.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.33.40.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 212.163.20.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 212.163.36.0/22 | Valid | RIR databaseRIPE | 672 100% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.60.108.0/24 | No ROA covers it. Add a ROA for AS209535, maxLength 24. |
| Route object: none | 154.60.108.0/24 | No 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. |
| ROA: none | 154.60.109.0/24 | No ROA covers it. Add a ROA for AS209535, maxLength 24. |
| Route object: none | 154.60.109.0/24 | No 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. |
| ROA: none | 154.60.110.0/24 | No ROA covers it. Add a ROA for AS209535, maxLength 24. |
| Route object: none | 154.60.110.0/24 | No 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. |
| ROA: none | 154.60.111.0/24 | No ROA covers it. Add a ROA for AS209535, maxLength 24. |
| Route object: none | 154.60.111.0/24 | No 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. |
| ROA: none | 149.36.200.0/24 | No ROA covers it. Add a ROA for AS209535, maxLength 24. |
| Route object: RIR | 149.36.200.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.36.201.0/24 | No ROA covers it. Add a ROA for AS209535, maxLength 24. |
| Route object: RIR | 149.36.201.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.36.202.0/24 | No ROA covers it. Add a ROA for AS209535, maxLength 24. |
| Route object: RIR | 149.36.202.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.36.203.0/24 | No ROA covers it. Add a ROA for AS209535, maxLength 24. |
| Route object: RIR | 149.36.203.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.36.200.0/22 | No ROA covers it. Add a ROA for AS209535, maxLength 22. |
| Route object: RIR | 149.36.200.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.60.108.0/22 | No ROA covers it. Add a ROA for AS209535, maxLength 22. |
| Route object: RIR | 154.60.108.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 147.78.24.0/24 | No 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. |
| Route object: none | 147.78.25.0/24 | No 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. |
| Route object: none | 147.78.26.0/24 | No 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. |
| Route object: none | 147.78.27.0/24 | No 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. |
| Route object: none | 193.33.6.0/24 | No 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. |
| Route object: none | 193.33.7.0/24 | No 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. |
| Route object: none | 193.33.40.0/24 | No 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. |
| Route object: none | 193.33.41.0/24 | No 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. |
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/23 | RADB | No ROA |
| 149.36.202.0/23 | RADB | No ROA |
| 212.163.20.0/23 | RIPE | Valid |
| 212.163.22.0/23 | RIPE | Valid |
| 212.163.36.0/23 | RIPE | Valid |
| 212.163.38.0/23 | RIPE | Valid |
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.