Network · data from 2026-11-12
AS267441 AS267441 - J BARBOSA SERVICOS DE COMUNICACAO MULTIMIDIA LTDA
Registry name: AS267441 - J BARBOSA SERVICOS DE COMUNICACAO MULTIMIDIA LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267441, 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:4190:3000::/36 | No ROA | Nonecovered by 2804:4190::/33 | 635 100% |
| 2804:4190::/36 | No ROA | Nonecovered by 2804:4190::/33 | 634 100% |
| 2804:4190:1000::/36 | No ROA | Nonecovered by 2804:4190::/33 | 634 100% |
| 2804:4190:2000::/36 | No ROA | Nonecovered by 2804:4190::/33 | 633 100% |
| 192.141.16.0/24 | No ROA | Other IRR onlyRADB, TC | 673 100% |
| 192.141.19.0/24 | No ROA | Other IRR onlyTC | 673 100% |
| 192.141.17.0/24 | No ROA | Other IRR onlyTC | 672 100% |
| 192.141.18.0/24 | No ROA | Other IRR onlyTC | 671 100% |
AS-SET
AS267441 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 22 are in fix.csv.
- ROA: none8
- Route object: none4
- Route object: RIR4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:4190:3000::/36 | No ROA covers it. Add a ROA for AS267441, maxLength 36. |
| Route object: none | 2804:4190:3000::/36 | No route object for it. A route object for 2804:4190::/33 with origin AS267441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267441 in the RIR database for the space. |
| ROA: none | 2804:4190::/36 | No ROA covers it. Add a ROA for AS267441, maxLength 36. |
| Route object: none | 2804:4190::/36 | No route object for it. A route object for 2804:4190::/33 with origin AS267441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267441 in the RIR database for the space. |
| ROA: none | 2804:4190:1000::/36 | No ROA covers it. Add a ROA for AS267441, maxLength 36. |
| Route object: none | 2804:4190:1000::/36 | No route object for it. A route object for 2804:4190::/33 with origin AS267441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267441 in the RIR database for the space. |
| ROA: none | 2804:4190:2000::/36 | No ROA covers it. Add a ROA for AS267441, maxLength 36. |
| Route object: none | 2804:4190:2000::/36 | No route object for it. A route object for 2804:4190::/33 with origin AS267441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267441 in the RIR database for the space. |
| ROA: none | 192.141.16.0/24 | No ROA covers it. Add a ROA for AS267441, maxLength 24. |
| Route object: RIR | 192.141.16.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 192.141.19.0/24 | No ROA covers it. Add a ROA for AS267441, maxLength 24. |
| Route object: RIR | 192.141.19.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 192.141.17.0/24 | No ROA covers it. Add a ROA for AS267441, maxLength 24. |
| Route object: RIR | 192.141.17.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 192.141.18.0/24 | No ROA covers it. Add a ROA for AS267441, maxLength 24. |
| Route object: RIR | 192.141.18.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267441 whose prefix no peer sees AS267441 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.141.16.0/22 | RADB, TC | No ROA |
| 192.141.16.0/23 | RADB, TC | No ROA |
| 192.141.18.0/23 | RADB, TC | No ROA |
| 2804:4190::/32 | RADB, TC | No ROA |
| 2804:4190::/33 | TC | No ROA |
| 2804:4190:8000::/33 | 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.