Network · data from 2026-11-12
AS267523 ARANTES & ARANTES TELECOM
Registry name: AS267523 - LEMAX INTERNET, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267523, 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:42c0::/33 | Invalid: maxLength | Nonecovered by 2804:42c0::/32 | 2 0%low visibility |
| 2804:42c0:8000::/33 | Invalid: maxLength | Nonecovered by 2804:42c0::/32 | 2 0%low visibility |
| 2804:42c0::/36 | Valid | Nonecovered by 2804:42c0::/32 | 636 100% |
| 201.182.160.0/23 | Valid | Other IRR onlyTC | 669 99% |
| 201.182.162.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 201.182.160.0/22 | Valid | Other IRR onlyRADB, TC | 666 99% |
| 2804:42c0:1000::/36 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:42c0::/32 | Valid | Other IRR onlyRADB, TC | 632 99% |
| 201.182.163.0/24 | Valid | Other IRR onlyTC | 198 29% |
| 201.182.162.0/23 | Valid | Other IRR onlyTC | 175 26% |
AS-SET
AS267523'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 13 are in fix.csv.
- ROA: maxLength2
- Route object: none3
- Route object: RIR7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2804:42c0::/33 | ROA 2804:42c0::/32 AS267523 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:42c0::/33. |
| Route object: none | 2804:42c0::/33 | No route object for it. A route object for 2804:42c0::/32 with origin AS267523 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267523 in the RIR database for the space. |
| ROA: maxLength | 2804:42c0:8000::/33 | ROA 2804:42c0::/32 AS267523 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:42c0:8000::/33. |
| Route object: none | 2804:42c0:8000::/33 | No route object for it. A route object for 2804:42c0::/32 with origin AS267523 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267523 in the RIR database for the space. |
| Route object: none | 2804:42c0::/36 | No route object for it. A route object for 2804:42c0::/32 with origin AS267523 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267523 in the RIR database for the space. |
| Route object: RIR | 201.182.160.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.182.162.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.182.160.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:42c0:1000::/36 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:42c0::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.182.163.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.182.162.0/23 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267523 whose prefix no peer sees AS267523 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.23.184.0/21 | 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.