Network · data from 2026-11-12
AS61732 AS61732 - PRECISA INTERNET E COMUNICACAO LTDA
Registry name: AS61732 - PRECISA INTERNET E COMUNICACAO LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61732, 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:1b84::/33 | No ROA | Nonecovered by 2804:1b84::/32 | 107 17% |
| 2804:1b84:8000::/33 | No ROA | Nonecovered by 2804:1b84::/32 | 107 17% |
| 131.72.104.0/22 | No ROA | Other IRR onlyRADB, TC | 672 100% |
| 170.247.16.0/22 | No ROA | Other IRR onlyRADB, TC | 672 100% |
| 2804:1b84::/32 | No ROA | Other IRR onlyRADB | 634 100% |
| 131.72.106.0/23 | No ROA | Other IRR onlyRADB, TC | 119 18% |
| 170.247.16.0/23 | No ROA | Other IRR onlyRADB, TC | 119 18% |
| 170.247.18.0/23 | No ROA | Other IRR onlyRADB, TC | 119 18% |
| 131.72.104.0/23 | No ROA | Other IRR onlyRADB, TC | 118 18% |
AS-SET
AS61732 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 26 are in fix.csv.
- ROA: none9
- Route object: none2
- Route object: RIR7
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:1b84::/33 | No ROA covers it. Add a ROA for AS61732, maxLength 33. |
| Route object: none | 2804:1b84::/33 | No route object for it. A route object for 2804:1b84::/32 with origin AS61732 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61732 in the RIR database for the space. |
| ROA: none | 2804:1b84:8000::/33 | No ROA covers it. Add a ROA for AS61732, maxLength 33. |
| Route object: none | 2804:1b84:8000::/33 | No route object for it. A route object for 2804:1b84::/32 with origin AS61732 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61732 in the RIR database for the space. |
| ROA: none | 131.72.104.0/22 | No ROA covers it. Add a ROA for AS61732, maxLength 22. |
| Route object: RIR | 131.72.104.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 170.247.16.0/22 | No ROA covers it. Add a ROA for AS61732, maxLength 22. |
| Route object: RIR | 170.247.16.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:1b84::/32 | No ROA covers it. Add a ROA for AS61732, maxLength 32. |
| Route object: RIR | 2804:1b84::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 131.72.106.0/23 | No ROA covers it. Add a ROA for AS61732, maxLength 23. |
| Route object: RIR | 131.72.106.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 170.247.16.0/23 | No ROA covers it. Add a ROA for AS61732, maxLength 23. |
| Route object: RIR | 170.247.16.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 170.247.18.0/23 | No ROA covers it. Add a ROA for AS61732, maxLength 23. |
| Route object: RIR | 170.247.18.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 131.72.104.0/23 | No ROA covers it. Add a ROA for AS61732, maxLength 23. |
| Route object: RIR | 131.72.104.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 AS61732 whose prefix no peer sees AS61732 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.72.104.0/24 | TC | No ROA |
| 131.72.105.0/24 | RADB, TC | No ROA |
| 131.72.106.0/24 | TC | No ROA |
| 131.72.107.0/24 | TC | No ROA |
| 170.247.16.0/24 | TC | No ROA |
| 170.247.17.0/24 | RADB, TC | No ROA |
| 170.247.18.0/24 | TC | No ROA |
| 170.247.19.0/24 | TC | 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.