Network · data from 2026-11-12
AS205025 iRegister Ilir Kurti
Registry name: iRegister Ilir Kurti, AL · not in PeeringDB
28IPv4 routes
71.4% RPKI valid · 71.4% with a route object
0IPv6 routes
8RPKI invalid
8 origin · 0 maxLength
0No ROA
8 with no route object for this origin
8Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS205025, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS205025, 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.
| 136.148.196.0/24 | Invalid: origin | None | 2 0%low visibility |
| 136.148.197.0/24 | Invalid: origin | None | 2 0%low visibility |
| 136.148.198.0/24 | Invalid: origin | None | 2 0%low visibility |
| 136.148.199.0/24 | Invalid: origin | None | 2 0%low visibility |
| 136.148.204.0/24 | Invalid: origin | None | 2 0%low visibility |
| 136.148.205.0/24 | Invalid: origin | None | 2 0%low visibility |
| 136.148.206.0/24 | Invalid: origin | None | 2 0%low visibility |
| 136.148.207.0/24 | Invalid: origin | None | 2 0%low visibility |
| 62.101.161.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.101.162.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.101.163.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.101.164.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.101.166.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.101.167.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 82.198.32.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 82.198.33.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 82.198.34.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 82.198.35.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.53.102.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.53.103.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.146.17.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.146.19.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.146.21.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.146.23.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.146.25.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.146.27.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.146.29.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.146.31.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS205025 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 16 are in fix.csv.
- ROA: origin8
- Route object: none8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 136.148.196.0/24 | ROAs covering it name AS6079, not AS205025. If AS205025 should announce it, add a ROA for AS205025. |
| Route object: none | 136.148.196.0/24 | No route object for it. Add a route object with origin AS205025 in the RIR database for the space. |
| ROA: origin | 136.148.197.0/24 | ROAs covering it name AS6079, not AS205025. If AS205025 should announce it, add a ROA for AS205025. |
| Route object: none | 136.148.197.0/24 | No route object for it. Add a route object with origin AS205025 in the RIR database for the space. |
| ROA: origin | 136.148.198.0/24 | ROAs covering it name AS6079, not AS205025. If AS205025 should announce it, add a ROA for AS205025. |
| Route object: none | 136.148.198.0/24 | No route object for it. Add a route object with origin AS205025 in the RIR database for the space. |
| ROA: origin | 136.148.199.0/24 | ROAs covering it name AS6079, not AS205025. If AS205025 should announce it, add a ROA for AS205025. |
| Route object: none | 136.148.199.0/24 | No route object for it. Add a route object with origin AS205025 in the RIR database for the space. |
| ROA: origin | 136.148.204.0/24 | ROAs covering it name AS6079, not AS205025. If AS205025 should announce it, add a ROA for AS205025. |
| Route object: none | 136.148.204.0/24 | No route object for it. Add a route object with origin AS205025 in the RIR database for the space. |
| ROA: origin | 136.148.205.0/24 | ROAs covering it name AS6079, not AS205025. If AS205025 should announce it, add a ROA for AS205025. |
| Route object: none | 136.148.205.0/24 | No route object for it. Add a route object with origin AS205025 in the RIR database for the space. |
| ROA: origin | 136.148.206.0/24 | ROAs covering it name AS6079, not AS205025. If AS205025 should announce it, add a ROA for AS205025. |
| Route object: none | 136.148.206.0/24 | No route object for it. Add a route object with origin AS205025 in the RIR database for the space. |
| ROA: origin | 136.148.207.0/24 | ROAs covering it name AS6079, not AS205025. If AS205025 should announce it, add a ROA for AS205025. |
| Route object: none | 136.148.207.0/24 | No route object for it. Add a route object with origin AS205025 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS205025 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.