Network · data from 2026-11-12
AS264643 AS264643 - Enredes S.A.
Registry name: AS264643 - Enredes S.A., AR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264643, 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.
| 45.178.252.0/24 | Valid | Nonecovered by 45.178.252.0/22 | 668 99% |
| 45.178.253.0/24 | Valid | Nonecovered by 45.178.252.0/22 | 668 99% |
| 45.178.254.0/24 | Valid | Nonecovered by 45.178.252.0/22 | 668 99% |
| 45.178.255.0/24 | Valid | Nonecovered by 45.178.252.0/22 | 668 99% |
| 143.255.152.0/24 | Valid | Nonecovered by 143.255.152.0/22 | 668 99% |
| 143.255.153.0/24 | Valid | Nonecovered by 143.255.152.0/22 | 668 99% |
| 143.255.154.0/24 | Valid | Nonecovered by 143.255.152.0/22 | 668 99% |
| 143.255.155.0/24 | Valid | Nonecovered by 143.255.152.0/22 | 668 99% |
| 45.178.252.0/22 | Valid | RIR databaseLACNIC | 666 99% |
| 143.255.152.0/22 | Valid | RIR databaseLACNIC, RADB | 666 99% |
AS-SET
AS264643 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 8 are in fix.csv.
- Route object: none8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.178.252.0/24 | No route object for it. A route object for 45.178.252.0/22 with origin AS264643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264643 in the RIR database for the space. |
| Route object: none | 45.178.253.0/24 | No route object for it. A route object for 45.178.252.0/22 with origin AS264643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264643 in the RIR database for the space. |
| Route object: none | 45.178.254.0/24 | No route object for it. A route object for 45.178.252.0/22 with origin AS264643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264643 in the RIR database for the space. |
| Route object: none | 45.178.255.0/24 | No route object for it. A route object for 45.178.252.0/22 with origin AS264643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264643 in the RIR database for the space. |
| Route object: none | 143.255.152.0/24 | No route object for it. A route object for 143.255.152.0/22 with origin AS264643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264643 in the RIR database for the space. |
| Route object: none | 143.255.153.0/24 | No route object for it. A route object for 143.255.152.0/22 with origin AS264643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264643 in the RIR database for the space. |
| Route object: none | 143.255.154.0/24 | No route object for it. A route object for 143.255.152.0/22 with origin AS264643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264643 in the RIR database for the space. |
| Route object: none | 143.255.155.0/24 | No route object for it. A route object for 143.255.152.0/22 with origin AS264643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264643 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS264643 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.