Network · data from 2026-11-12
AS52953 ZAP TCHE PROVEDOR DE INTERNET
Registry name: AS52953 - ZAP TCHE PROVEDOR DE INTERNET LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52953, 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.22.48.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.22.50.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.22.52.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.22.54.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.22.56.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.22.58.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.22.60.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.22.61.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.22.62.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.22.63.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 2804:5dc0::/36 | Valid | Other IRR onlyRADB | 634 100% |
| 177.22.60.0/23 | Valid | Other IRR onlyRADB, TC | 2 0%low visibility |
| 177.22.62.0/23 | Valid | Other IRR onlyRADB, TC | 2 0%low visibility |
AS-SET
AS52953'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 33 are in fix.csv.
- Route object: RIR13
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 177.22.48.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.50.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.52.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.54.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.56.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.58.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.60.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.61.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.62.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.63.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5dc0::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.60.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.22.62.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52953 whose prefix no peer sees AS52953 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.22.48.0/20 | RADB, TC | Valid |
| 177.22.48.0/21 | RADB, TC | Valid |
| 177.22.48.0/22 | RADB, TC | Valid |
| 177.22.48.0/24 | RADB, TC | Valid |
| 177.22.49.0/24 | RADB, TC | Valid |
| 177.22.50.0/24 | RADB, TC | Valid |
| 177.22.51.0/24 | RADB, TC | Valid |
| 177.22.52.0/22 | RADB, TC | Valid |
| 177.22.52.0/24 | RADB, TC | Valid |
| 177.22.53.0/24 | RADB, TC | Valid |
| 177.22.54.0/24 | RADB, TC | Valid |
| 177.22.55.0/24 | RADB, TC | Valid |
| 177.22.56.0/21 | TC | Valid |
| 177.22.56.0/22 | RADB, TC | Valid |
| 177.22.56.0/24 | RADB, TC | Valid |
| 177.22.57.0/24 | RADB, TC | Valid |
| 177.22.58.0/24 | RADB, TC | Valid |
| 177.22.59.0/24 | RADB, TC | Valid |
| 177.22.60.0/22 | TC | Valid |
| 2804:5dc0::/32 | RADB, 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.