Network · data from 2026-11-12
AS10412 CIA. DE TECNOL. DA INFOR. E COMUNICAÇÃO DO PARANÁ AS10412
Registry name: AS10412 - CIA. DE TECNOL. DA INFOR. E COMUNICACAO DO PARANA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10412, 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.
| 200.201.0.0/21 | No ROA | Nonecovered by 200.201.0.0/17 | 670 100% |
| 200.201.40.0/21 | No ROA | Nonecovered by 200.201.0.0/17 | 670 100% |
| 200.201.48.0/20 | No ROA | Nonecovered by 200.201.0.0/17 | 670 100% |
| 200.201.64.0/18 | No ROA | Nonecovered by 200.201.0.0/17 | 670 100% |
| 200.201.116.0/24 | No ROA | Nonecovered by 200.201.0.0/17 | 668 99% |
| 200.201.113.0/24 | No ROA | Nonecovered by 200.201.0.0/17 | 667 99% |
| 2804:5ac::/32 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS10412'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 15 are in fix.csv.
- ROA: none7
- Route object: none6
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.201.0.0/21 | No ROA covers it. Add a ROA for AS10412, maxLength 21. |
| Route object: none | 200.201.0.0/21 | No route object for it. A route object for 200.201.0.0/17 with origin AS10412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10412 in the RIR database for the space. |
| ROA: none | 200.201.40.0/21 | No ROA covers it. Add a ROA for AS10412, maxLength 21. |
| Route object: none | 200.201.40.0/21 | No route object for it. A route object for 200.201.0.0/17 with origin AS10412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10412 in the RIR database for the space. |
| ROA: none | 200.201.48.0/20 | No ROA covers it. Add a ROA for AS10412, maxLength 20. |
| Route object: none | 200.201.48.0/20 | No route object for it. A route object for 200.201.0.0/17 with origin AS10412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10412 in the RIR database for the space. |
| ROA: none | 200.201.64.0/18 | No ROA covers it. Add a ROA for AS10412, maxLength 18. |
| Route object: none | 200.201.64.0/18 | No route object for it. A route object for 200.201.0.0/17 with origin AS10412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10412 in the RIR database for the space. |
| ROA: none | 200.201.116.0/24 | No ROA covers it. Add a ROA for AS10412, maxLength 24. |
| Route object: none | 200.201.116.0/24 | No route object for it. A route object for 200.201.0.0/17 with origin AS10412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10412 in the RIR database for the space. |
| ROA: none | 200.201.113.0/24 | No ROA covers it. Add a ROA for AS10412, maxLength 24. |
| Route object: none | 200.201.113.0/24 | No route object for it. A route object for 200.201.0.0/17 with origin AS10412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10412 in the RIR database for the space. |
| ROA: none | 2804:5ac::/32 | No ROA covers it. Add a ROA for AS10412, maxLength 32. |
| Route object: RIR | 2804:5ac::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10412 whose prefix no peer sees AS10412 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.201.0.0/17 | 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.