Network · data from 2026-11-12
AS52819 AS52819 - Placido e Andrade LTDA
Registry name: AS52819 - Placido e Andrade LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52819, 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.75.112.0/22 | No ROA | Other IRR onlyTC | 672 100% |
| 177.75.119.0/24 | No ROA | Other IRR onlyRADB, TC | 672 100% |
| 177.75.120.0/21 | No ROA | Other IRR onlyRADB, TC | 672 100% |
| 177.75.120.0/23 | No ROA | Other IRR onlyTC | 672 100% |
| 177.75.122.0/23 | No ROA | Other IRR onlyTC | 672 100% |
| 177.75.124.0/23 | No ROA | Other IRR onlyTC | 672 100% |
| 177.75.126.0/23 | No ROA | Other IRR onlyTC | 672 100% |
| 177.75.116.0/23 | No ROA | Other IRR onlyTC | 670 100% |
| 177.75.118.0/24 | No ROA | Other IRR onlyTC | 670 100% |
| 177.75.120.0/22 | No ROA | Other IRR onlyTC | 1 0%low visibility |
| 177.75.124.0/22 | No ROA | Other IRR onlyTC | 1 0%low visibility |
AS-SET
AS52819 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 48 are in fix.csv.
- ROA: none11
- Route object: RIR11
- Route object: not announced26
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 177.75.112.0/22 | No ROA covers it. Add a ROA for AS52819, maxLength 22. |
| Route object: RIR | 177.75.112.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.75.119.0/24 | No ROA covers it. Add a ROA for AS52819, maxLength 24. |
| Route object: RIR | 177.75.119.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 177.75.120.0/21 | No ROA covers it. Add a ROA for AS52819, maxLength 21. |
| Route object: RIR | 177.75.120.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 177.75.120.0/23 | No ROA covers it. Add a ROA for AS52819, maxLength 23. |
| Route object: RIR | 177.75.120.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.75.122.0/23 | No ROA covers it. Add a ROA for AS52819, maxLength 23. |
| Route object: RIR | 177.75.122.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.75.124.0/23 | No ROA covers it. Add a ROA for AS52819, maxLength 23. |
| Route object: RIR | 177.75.124.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.75.126.0/23 | No ROA covers it. Add a ROA for AS52819, maxLength 23. |
| Route object: RIR | 177.75.126.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.75.116.0/23 | No ROA covers it. Add a ROA for AS52819, maxLength 23. |
| Route object: RIR | 177.75.116.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.75.118.0/24 | No ROA covers it. Add a ROA for AS52819, maxLength 24. |
| Route object: RIR | 177.75.118.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.75.120.0/22 | No ROA covers it. Add a ROA for AS52819, maxLength 22. |
| Route object: RIR | 177.75.120.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 177.75.124.0/22 | No ROA covers it. Add a ROA for AS52819, maxLength 22. |
| Route object: RIR | 177.75.124.0/22 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52819 whose prefix no peer sees AS52819 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.75.112.0/20 | RADB, TC | No ROA |
| 177.75.112.0/21 | TC | No ROA |
| 177.75.112.0/23 | TC | No ROA |
| 177.75.112.0/24 | TC | No ROA |
| 177.75.113.0/24 | TC | No ROA |
| 177.75.114.0/23 | TC | No ROA |
| 177.75.114.0/24 | TC | No ROA |
| 177.75.115.0/24 | TC | No ROA |
| 177.75.116.0/22 | TC | No ROA |
| 177.75.116.0/24 | TC | No ROA |
| 177.75.117.0/24 | TC | No ROA |
| 177.75.118.0/23 | TC | No ROA |
| 177.75.120.0/24 | TC | No ROA |
| 177.75.121.0/24 | TC | No ROA |
| 177.75.122.0/24 | TC | No ROA |
| 177.75.123.0/24 | TC | No ROA |
| 177.75.124.0/24 | TC | No ROA |
| 177.75.125.0/24 | TC | No ROA |
| 177.75.126.0/24 | TC | No ROA |
| 177.75.127.0/24 | TC | No ROA |
| 2804:6ad8::/32 | RADB, TC | No ROA |
| 2804:6ad8::/33 | TC | No ROA |
| 2804:6ad8:4000::/34 | TC | No ROA |
| 2804:6ad8:8000::/33 | TC | No ROA |
| 2804:6ad8:8000::/34 | TC | No ROA |
| 2804:6ad8:c000::/34 | 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.