Network · data from 2026-11-12
AS52801 AS52801 - Apanet Servicos de Internet Ltda.
Registry name: AS52801 - Apanet Servicos de Internet Ltda., BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52801, 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:ba0::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 635 100% |
| 177.52.88.0/24 | Valid | Other IRR onlyTC | 120 18% |
| 177.52.89.0/24 | Valid | Other IRR onlyRADB, TC | 120 18% |
| 177.52.90.0/24 | Valid | Other IRR onlyRADB, TC | 120 18% |
| 177.52.92.0/24 | Valid | Other IRR onlyRADB, TC | 120 18% |
| 177.52.93.0/24 | Valid | Other IRR onlyRADB, TC | 120 18% |
| 177.52.94.0/24 | Valid | Other IRR onlyRADB, TC | 120 18% |
| 177.52.95.0/24 | Valid | Other IRR onlyRADB, TC | 120 18% |
AS-SET
AS52801 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 23 are in fix.csv.
- Route object: RIR8
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2804:ba0::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.52.88.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.52.89.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.52.90.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.52.92.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.52.93.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.52.94.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.52.95.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52801 whose prefix no peer sees AS52801 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.52.88.0/21 | ALTDB, RADB, TC | Valid |
| 177.52.88.0/22 | RADB, TC | Valid |
| 177.52.88.0/23 | TC | Valid |
| 177.52.90.0/23 | TC | Valid |
| 177.52.91.0/24 | RADB, TC | Valid |
| 177.52.92.0/22 | RADB, TC | Valid |
| 177.52.92.0/23 | TC | Valid |
| 177.52.94.0/23 | TC | Valid |
| 2804:ba0::/33 | TC | Valid |
| 2804:ba0::/34 | TC | Valid |
| 2804:ba0:4000::/34 | TC | Valid |
| 2804:ba0:8000::/33 | TC | Valid |
| 2804:ba0:8000::/34 | TC | Valid |
| 2804:ba0:c000::/34 | TC | Valid |
| 2804:2e18::/32 | 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.