Network · data from 2026-11-12
AS52924 AS52924 - NEXCESS Solucoes de Redes Ltda.
Registry name: AS52924 - NEXCESS Solucoes de Redes Ltda., BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52924, 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.
| 177.184.237.0/24 | Valid | Nonecovered by 177.184.236.0/23 | 668 99% |
| 2804:36e8:c090::/44 | Valid | Nonecovered by 2804:36e8::/32 | 635 100% |
| 2804:36e8:c010::/44 | Valid | Nonecovered by 2804:36e8::/32 | 634 100% |
| 2804:36e8:c080::/44 | Valid | Nonecovered by 2804:36e8::/32 | 342 54% |
| 177.184.235.0/24 | Valid | Other IRR onlyRADB, TC | 673 100% |
| 177.184.226.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.184.224.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.184.225.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.184.227.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.184.230.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.184.232.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.184.234.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.184.239.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 177.184.228.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 177.184.229.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 177.184.238.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 177.184.231.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 177.184.233.0/24 | Valid | Other IRR onlyRADB, TC | 667 99% |
| 177.184.236.0/24 | Valid | Other IRR onlyRADB, TC | 667 99% |
| 2804:36e8:c030::/44 | Valid | Other IRR onlyRADB | 636 100% |
| 2804:36e8::/33 | Valid | Other IRR onlyTC | 635 100% |
| 2804:36e8:8000::/34 | Valid | Other IRR onlyTC | 635 100% |
| 2804:36e8:c070::/44 | Valid | Other IRR onlyRADB | 633 100% |
AS-SET
AS52924 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 31 are in fix.csv.
- Route object: none4
- Route object: RIR19
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 177.184.237.0/24 | No route object for it. A route object for 177.184.236.0/23 with origin AS52924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52924 in the RIR database for the space. |
| Route object: none | 2804:36e8:c090::/44 | No route object for it. A route object for 2804:36e8::/32 with origin AS52924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52924 in the RIR database for the space. |
| Route object: none | 2804:36e8:c010::/44 | No route object for it. A route object for 2804:36e8::/32 with origin AS52924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52924 in the RIR database for the space. |
| Route object: none | 2804:36e8:c080::/44 | No route object for it. A route object for 2804:36e8::/32 with origin AS52924 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52924 in the RIR database for the space. |
| Route object: RIR | 177.184.235.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.226.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.224.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.225.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.227.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.230.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.232.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.234.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.239.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.228.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.229.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.238.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.231.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.233.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.184.236.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:36e8:c030::/44 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:36e8::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:36e8:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:36e8:c070::/44 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52924 whose prefix no peer sees AS52924 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.184.224.0/20 | RADB, TC | Valid |
| 177.184.236.0/23 | TC | Valid |
| 2804:36e8::/32 | RADB, TC | Valid |
| 2804:36e8:c001::/48 | RADB | Valid |
| 2804:36e8:c070::/48 | RADB | Valid |
| 2804:36e8:c071::/48 | RADB | Valid |
| 2804:36e8:c078::/45 | RADB | Valid |
| 2804:36e8:c0b0::/44 | TC | Valid |
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.