Network · data from 2026-11-12
AS267486 AS267486 - MARIA DE FATIMA SILVA MARCELINO LIMA ME
Registry name: AS267486 - MARIA DE FATIMA SILVA MARCELINO LIMA ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267486, 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:4238:8000::/34 | No ROA | Nonecovered by 2804:4238::/32 | 632 99% |
| 2804:4238:c000::/34 | No ROA | Nonecovered by 2804:4238::/32 | 632 99% |
| 192.141.132.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 192.141.133.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 192.141.134.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 192.141.135.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS267486 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 17 are in fix.csv.
- ROA: none6
- Route object: none2
- Route object: RIR4
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:4238:8000::/34 | No ROA covers it. Add a ROA for AS267486, maxLength 34. |
| Route object: none | 2804:4238:8000::/34 | No route object for it. A route object for 2804:4238::/32 with origin AS267486 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267486 in the RIR database for the space. |
| ROA: none | 2804:4238:c000::/34 | No ROA covers it. Add a ROA for AS267486, maxLength 34. |
| Route object: none | 2804:4238:c000::/34 | No route object for it. A route object for 2804:4238::/32 with origin AS267486 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267486 in the RIR database for the space. |
| ROA: none | 192.141.132.0/24 | No ROA covers it. Add a ROA for AS267486, maxLength 24. |
| Route object: RIR | 192.141.132.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.141.133.0/24 | No ROA covers it. Add a ROA for AS267486, maxLength 24. |
| Route object: RIR | 192.141.133.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.141.134.0/24 | No ROA covers it. Add a ROA for AS267486, maxLength 24. |
| Route object: RIR | 192.141.134.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.141.135.0/24 | No ROA covers it. Add a ROA for AS267486, maxLength 24. |
| Route object: RIR | 192.141.135.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267486 whose prefix no peer sees AS267486 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 187.61.96.0/20 | RADB | No ROA |
| 192.141.132.0/22 | RADB | No ROA |
| 192.141.132.0/23 | RADB | No ROA |
| 2804:2f98::/32 | RADB | No ROA |
| 2804:4238::/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.