Network · data from 2026-11-12
AS28203 AS28203 - Webcenter Sist Prest de Servicos de Informatica
Registry name: AS28203 - Webcenter Sist Prest de Servicos de Informatica, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28203, 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.
| 189.91.43.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 189.91.32.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 189.91.34.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 189.91.44.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 189.91.36.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 189.91.40.0/21 | No ROA | Other IRR onlyRADB | 670 100% |
| 189.91.45.0/24 | No ROA | Other IRR onlyRADB | 32 5%low visibility |
| 189.91.46.0/24 | No ROA | Other IRR onlyRADB | 32 5%low visibility |
AS-SET
AS28203 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: none8
- Route object: RIR8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 189.91.43.0/24 | No ROA covers it. Add a ROA for AS28203, maxLength 24. |
| Route object: RIR | 189.91.43.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 189.91.32.0/23 | No ROA covers it. Add a ROA for AS28203, maxLength 23. |
| Route object: RIR | 189.91.32.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 189.91.34.0/24 | No ROA covers it. Add a ROA for AS28203, maxLength 24. |
| Route object: RIR | 189.91.34.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 189.91.44.0/24 | No ROA covers it. Add a ROA for AS28203, maxLength 24. |
| Route object: RIR | 189.91.44.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 189.91.36.0/22 | No ROA covers it. Add a ROA for AS28203, maxLength 22. |
| Route object: RIR | 189.91.36.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 189.91.40.0/21 | No ROA covers it. Add a ROA for AS28203, maxLength 21. |
| Route object: RIR | 189.91.40.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 189.91.45.0/24 | No ROA covers it. Add a ROA for AS28203, maxLength 24. |
| Route object: RIR | 189.91.45.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 189.91.46.0/24 | No ROA covers it. Add a ROA for AS28203, maxLength 24. |
| Route object: RIR | 189.91.46.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28203 whose prefix no peer sees AS28203 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 189.91.32.0/20 | 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.