Network · data from 2026-11-12
AS263659 AS263659 - PCNET INTERNET
Registry name: AS263659 - PCNET INTERNET, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263659, 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.
| 170.233.161.0/24 | No ROA | Nonecovered by 170.233.160.0/22 | 670 100% |
| 170.233.162.0/24 | No ROA | Nonecovered by 170.233.160.0/22 | 670 100% |
| 191.240.192.0/24 | No ROA | Nonecovered by 191.240.192.0/22 | 670 100% |
| 191.240.194.0/24 | No ROA | Nonecovered by 191.240.192.0/22 | 670 100% |
| 191.240.195.0/24 | No ROA | Nonecovered by 191.240.192.0/22 | 670 100% |
| 170.233.160.0/24 | No ROA | Nonecovered by 170.233.160.0/22 | 669 99% |
| 191.240.193.0/24 | No ROA | Nonecovered by 191.240.192.0/22 | 669 99% |
| 170.233.163.0/24 | No ROA | Nonecovered by 170.233.160.0/22 | 667 99% |
| 170.233.160.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 191.240.192.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
AS-SET
AS263659 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 21 are in fix.csv.
- ROA: none10
- Route object: none8
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 170.233.161.0/24 | No ROA covers it. Add a ROA for AS263659, maxLength 24. |
| Route object: none | 170.233.161.0/24 | No route object for it. A route object for 170.233.160.0/22 with origin AS263659 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263659 in the RIR database for the space. |
| ROA: none | 170.233.162.0/24 | No ROA covers it. Add a ROA for AS263659, maxLength 24. |
| Route object: none | 170.233.162.0/24 | No route object for it. A route object for 170.233.160.0/22 with origin AS263659 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263659 in the RIR database for the space. |
| ROA: none | 191.240.192.0/24 | No ROA covers it. Add a ROA for AS263659, maxLength 24. |
| Route object: none | 191.240.192.0/24 | No route object for it. A route object for 191.240.192.0/22 with origin AS263659 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263659 in the RIR database for the space. |
| ROA: none | 191.240.194.0/24 | No ROA covers it. Add a ROA for AS263659, maxLength 24. |
| Route object: none | 191.240.194.0/24 | No route object for it. A route object for 191.240.192.0/22 with origin AS263659 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263659 in the RIR database for the space. |
| ROA: none | 191.240.195.0/24 | No ROA covers it. Add a ROA for AS263659, maxLength 24. |
| Route object: none | 191.240.195.0/24 | No route object for it. A route object for 191.240.192.0/22 with origin AS263659 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263659 in the RIR database for the space. |
| ROA: none | 170.233.160.0/24 | No ROA covers it. Add a ROA for AS263659, maxLength 24. |
| Route object: none | 170.233.160.0/24 | No route object for it. A route object for 170.233.160.0/22 with origin AS263659 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263659 in the RIR database for the space. |
| ROA: none | 191.240.193.0/24 | No ROA covers it. Add a ROA for AS263659, maxLength 24. |
| Route object: none | 191.240.193.0/24 | No route object for it. A route object for 191.240.192.0/22 with origin AS263659 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263659 in the RIR database for the space. |
| ROA: none | 170.233.163.0/24 | No ROA covers it. Add a ROA for AS263659, maxLength 24. |
| Route object: none | 170.233.163.0/24 | No route object for it. A route object for 170.233.160.0/22 with origin AS263659 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263659 in the RIR database for the space. |
| ROA: none | 170.233.160.0/22 | No ROA covers it. Add a ROA for AS263659, maxLength 22. |
| Route object: RIR | 170.233.160.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 191.240.192.0/22 | No ROA covers it. Add a ROA for AS263659, maxLength 22. |
| Route object: RIR | 191.240.192.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263659 whose prefix no peer sees AS263659 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:1118::/32 | 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.