Network · data from 2026-11-12
AS61789 AS61789 - PORTO SEGURO CIA DE SEGUROS GERAIS
Registry name: AS61789 - PORTO SEGURO CIA DE SEGUROS GERAIS, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61789, 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.
| 131.161.98.0/24 | No ROA | Nonecovered by 131.161.96.0/22 | 672 100% |
| 143.137.106.0/24 | No ROA | Nonecovered by 143.137.104.0/22 | 672 100% |
| 131.161.97.0/24 | No ROA | Nonecovered by 131.161.96.0/22 | 671 100% |
| 131.161.96.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 138.0.220.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 143.137.104.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 200.229.112.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS61789 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: none7
- Route object: none3
- Route object: RIR4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 131.161.98.0/24 | No ROA covers it. Add a ROA for AS61789, maxLength 24. |
| Route object: none | 131.161.98.0/24 | No route object for it. A route object for 131.161.96.0/22 with origin AS61789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61789 in the RIR database for the space. |
| ROA: none | 143.137.106.0/24 | No ROA covers it. Add a ROA for AS61789, maxLength 24. |
| Route object: none | 143.137.106.0/24 | No route object for it. A route object for 143.137.104.0/22 with origin AS61789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61789 in the RIR database for the space. |
| ROA: none | 131.161.97.0/24 | No ROA covers it. Add a ROA for AS61789, maxLength 24. |
| Route object: none | 131.161.97.0/24 | No route object for it. A route object for 131.161.96.0/22 with origin AS61789 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61789 in the RIR database for the space. |
| ROA: none | 131.161.96.0/22 | No ROA covers it. Add a ROA for AS61789, maxLength 22. |
| Route object: RIR | 131.161.96.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 138.0.220.0/22 | No ROA covers it. Add a ROA for AS61789, maxLength 22. |
| Route object: RIR | 138.0.220.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 143.137.104.0/22 | No ROA covers it. Add a ROA for AS61789, maxLength 22. |
| Route object: RIR | 143.137.104.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.229.112.0/24 | No ROA covers it. Add a ROA for AS61789, maxLength 24. |
| Route object: RIR | 200.229.112.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61789 whose prefix no peer sees AS61789 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.0.220.0/24 | RADB | No ROA |
| 2801:80:b00::/48 | RADB | No ROA |
| 2804:2188::/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.