Network · data from 2026-11-12
AS61737 Computex Informática Ltda
Registry name: AS61737 - Computex Informatica Ltda, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61737, 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.
| 131.72.180.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 2804:1b9c::/32 | Valid | Other IRR onlyRADB, TC | 631 99% |
| 2804:1b9c::/33 | Valid | Other IRR onlyTC | 631 99% |
| 2804:1b9c:8000::/33 | Valid | Other IRR onlyTC | 631 99% |
| 2804:1b9c::/34 | Valid | Other IRR onlyTC | 350 55% |
| 2804:1b9c:4000::/34 | Valid | Other IRR onlyTC | 350 55% |
| 2804:1b9c:8000::/34 | Valid | Other IRR onlyTC | 350 55% |
| 2804:1b9c:c000::/34 | Valid | Other IRR onlyTC | 350 55% |
| 131.72.180.0/24 | Valid | Other IRR onlyRADB, TC | 202 30% |
| 131.72.181.0/24 | Valid | Other IRR onlyRADB, TC | 202 30% |
| 131.72.182.0/24 | Valid | Other IRR onlyRADB, TC | 202 30% |
| 131.72.183.0/24 | Valid | Other IRR onlyRADB, TC | 202 30% |
AS-SET
AS61737'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 14 are in fix.csv.
- Route object: RIR12
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 131.72.180.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1b9c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1b9c::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1b9c:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1b9c::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1b9c:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1b9c:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1b9c:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.72.180.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.72.181.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.72.182.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.72.183.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 AS61737 whose prefix no peer sees AS61737 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.72.180.0/23 | RADB, TC | Valid |
| 131.72.182.0/23 | 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.