Network · data from 2026-11-12
AS265966 ALENCAR & ALENCAR
Registry name: AS265966 - J M P M ALENCAR & A G F ALENCAR LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265966, 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.
| 164.163.176.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 164.163.176.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 164.163.176.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 164.163.177.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 164.163.178.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 164.163.178.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 164.163.179.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2804:408c::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:408c::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:408c:1::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:408c:2::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:408c:3::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:408c:4::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:408c:5::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:408c:6::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:408c:10::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:408c:11::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:408c:1a::/48 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS265966'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 18 are in fix.csv.
- Route object: RIR18
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 164.163.176.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.176.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.176.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.177.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.178.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.178.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.179.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c:1::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c:2::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c:3::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c:4::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c:5::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c:6::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c:10::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c:11::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:408c:1a::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS265966 is announced.
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.