Network · data from 2026-11-12
AS3313 INET-AS RETELIT-X S.R.L.
Registry name: INET-AS RETELIT-X S.R.L., IT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3313, 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.
| 213.92.0.0/18 | No ROA | Nonecovered by 213.92.0.0/17 | 673 100% |
| 213.92.64.0/18 | No ROA | Nonecovered by 213.92.0.0/17 | 673 100% |
| 81.174.64.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 194.177.96.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 194.185.0.0/16 | No ROA | RIR databaseRIPE | 673 100% |
| 212.239.0.0/17 | No ROA | RIR databaseRIPE | 673 100% |
| 213.92.0.0/17 | No ROA | RIR databaseRIPE | 673 100% |
| 31.12.8.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 192.106.192.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 193.36.47.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 193.201.171.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a03:cf00::/32 | No ROA | RIR databaseRIPE | 635 100% |
| 193.43.15.0/24 | No ROA | RIR databaseRIPE | 594 88% |
| 194.20.8.0/21 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS3313 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 18 are in fix.csv.
- ROA: none13
- Route object: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 213.92.0.0/18 | No ROA covers it. Add a ROA for AS3313, maxLength 18. |
| Route object: none | 213.92.0.0/18 | No route object for it. A route object for 213.92.0.0/17 with origin AS3313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3313 in the RIR database for the space. |
| ROA: none | 213.92.64.0/18 | No ROA covers it. Add a ROA for AS3313, maxLength 18. |
| Route object: none | 213.92.64.0/18 | No route object for it. A route object for 213.92.0.0/17 with origin AS3313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3313 in the RIR database for the space. |
| ROA: none | 81.174.64.0/18 | No ROA covers it. Add a ROA for AS3313, maxLength 18. |
| ROA: none | 194.177.96.0/19 | No ROA covers it. Add a ROA for AS3313, maxLength 19. |
| ROA: none | 194.185.0.0/16 | No ROA covers it. Add a ROA for AS3313, maxLength 16. |
| ROA: none | 212.239.0.0/17 | No ROA covers it. Add a ROA for AS3313, maxLength 17. |
| ROA: none | 213.92.0.0/17 | No ROA covers it. Add a ROA for AS3313, maxLength 17. |
| ROA: none | 31.12.8.0/22 | No ROA covers it. Add a ROA for AS3313, maxLength 22. |
| ROA: none | 192.106.192.0/24 | No ROA covers it. Add a ROA for AS3313, maxLength 24. |
| ROA: none | 193.36.47.0/24 | No ROA covers it. Add a ROA for AS3313, maxLength 24. |
| ROA: none | 193.201.171.0/24 | No ROA covers it. Add a ROA for AS3313, maxLength 24. |
| ROA: none | 2a03:cf00::/32 | No ROA covers it. Add a ROA for AS3313, maxLength 32. |
| ROA: none | 193.43.15.0/24 | No ROA covers it. Add a ROA for AS3313, maxLength 24. |
Route objects not announced
Route objects with origin AS3313 whose prefix no peer sees AS3313 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 71.19.134.0/23 | RIPE-NONAUTH | No ROA |
| 81.174.71.0/24 | RADB | No ROA |
| 212.239.17.0/24 | RADB | No 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.