Network · data from 2026-11-12
AS267485 AS267485 - TRIBUNAL REGIONAL DO TRABALHO DA 24A REGIAO
Registry name: AS267485 - TRIBUNAL REGIONAL DO TRABALHO DA 24A REGIAO, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267485, 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.
| 192.141.97.0/24 | No ROA | Other IRR onlyALTDB, RADB | 671 100% |
| 2801:80:1de0::/48 | No ROA | Other IRR onlyALTDB, RADB | 628 99% |
AS-SET
AS267485 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 6 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.141.97.0/24 | No ROA covers it. Add a ROA for AS267485, maxLength 24. |
| Route object: RIR | 192.141.97.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 2801:80:1de0::/48 | No ROA covers it. Add a ROA for AS267485, maxLength 48. |
| Route object: RIR | 2801:80:1de0::/48 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267485 whose prefix no peer sees AS267485 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 186.209.96.0/20 | RADB | No ROA |
| 2804:1210::/32 | RADB | 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.