Network · data from 2026-11-12
AS267416 AS267416 - PIENSCO MANUTENCAO E PROJETOS LTDA
Registry name: AS267416 - PIENSCO MANUTENCAO E PROJETOS LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267416, 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.
| 45.235.111.0/24 | No ROA | Other IRR onlyRADB, TC | 2 0%low visibility |
| 45.235.109.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 45.235.110.0/24 | Valid | Other IRR onlyTC | 2 0%low visibility |
AS-SET
AS267416 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 8 are in fix.csv.
- ROA: none1
- Route object: RIR3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.235.111.0/24 | No ROA covers it. Add a ROA for AS267416, maxLength 24. |
| Route object: RIR | 45.235.111.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.235.109.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.235.110.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267416 whose prefix no peer sees AS267416 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.235.108.0/22 | RADB, TC | No ROA |
| 45.235.108.0/24 | TC | No ROA |
| 45.235.110.0/23 | RADB | No ROA |
| 2804:4d2c::/32 | RADB, 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.