Network · data from 2026-11-12
AS263420 ACX TELECOM LTDA.
Registry name: AS263420 - ACX TELECOM LTDA., BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263420, 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.
| 2804:83c4:b700::/40 | Invalid: origin | Other origin only | 27 4%low visibility |
| 179.191.226.0/24 | No ROA | Nonecovered by 179.191.224.0/21 | 670 100% |
| 179.191.227.0/24 | No ROA | Nonecovered by 179.191.224.0/21 | 669 99% |
| 179.191.228.0/24 | No ROA | Other origin onlycovered by 179.191.224.0/21 | 669 99% |
| 179.191.224.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 179.191.225.0/24 | No ROA | Other IRR onlyTC | 670 100% |
| 179.191.229.0/24 | No ROA | Other IRR onlyALTDB, RADB, TC | 668 99% |
| 179.191.230.0/23 | Valid | Other IRR onlyTC | 670 100% |
AS-SET
AS263420'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 19 are in fix.csv.
- ROA: origin1
- ROA: none6
- Route object: none4
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2804:83c4:b700::/40 | ROAs covering it name AS272218, not AS263420. If AS263420 should announce it, add a ROA for AS263420. |
| Route object: none | 2804:83c4:b700::/40 | Route objects for it name AS272218. Add a route object with origin AS263420 in the RIR database for the space. |
| ROA: none | 179.191.226.0/24 | No ROA covers it. Add a ROA for AS263420, maxLength 24. |
| Route object: none | 179.191.226.0/24 | No route object for it. A route object for 179.191.224.0/21 with origin AS263420 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263420 in the RIR database for the space. |
| ROA: none | 179.191.227.0/24 | No ROA covers it. Add a ROA for AS263420, maxLength 24. |
| Route object: none | 179.191.227.0/24 | No route object for it. A route object for 179.191.224.0/21 with origin AS263420 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263420 in the RIR database for the space. |
| ROA: none | 179.191.228.0/24 | No ROA covers it. Add a ROA for AS263420, maxLength 24. |
| Route object: none | 179.191.228.0/24 | Route objects for it name AS263054. A route object for 179.191.224.0/21 with origin AS263420 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263420 in the RIR database for the space. |
| ROA: none | 179.191.224.0/24 | No ROA covers it. Add a ROA for AS263420, maxLength 24. |
| Route object: RIR | 179.191.224.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 179.191.225.0/24 | No ROA covers it. Add a ROA for AS263420, maxLength 24. |
| Route object: RIR | 179.191.225.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 179.191.229.0/24 | No ROA covers it. Add a ROA for AS263420, maxLength 24. |
| Route object: RIR | 179.191.229.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.191.230.0/23 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263420 whose prefix no peer sees AS263420 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.191.224.0/21 | RADB, TC | No ROA |
| 179.191.230.0/24 | TC | Valid |
| 179.191.231.0/24 | TC | Valid |
| 2804:15f4::/32 | RADB, TC | 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.