Network · data from 2026-11-12
AS28086 Worldcom de Costa Rica
Registry name: AS28086 - Worldcom de Costa Rica, S.A., CR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28086, 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.
| 190.123.132.0/24 | Valid | Nonecovered by 190.123.128.0/20 | 672 100% |
| 190.123.133.0/24 | Valid | Nonecovered by 190.123.128.0/20 | 672 100% |
| 190.123.134.0/24 | Valid | Nonecovered by 190.123.128.0/20 | 672 100% |
| 190.123.135.0/24 | Valid | Nonecovered by 190.123.128.0/20 | 672 100% |
| 190.123.140.0/24 | Valid | Nonecovered by 190.123.128.0/20 | 672 100% |
| 190.123.141.0/24 | Valid | Nonecovered by 190.123.128.0/20 | 672 100% |
| 190.123.142.0/24 | Valid | Nonecovered by 190.123.128.0/20 | 672 100% |
| 209.213.176.0/21 | Valid | Nonecovered by 209.213.176.0/20 | 671 100% |
| 190.123.136.0/24 | Valid | Nonecovered by 190.123.128.0/20 | 3 0%low visibility |
| 209.213.184.0/21 | Valid | Other origin onlycovered by 209.213.176.0/20 | 2 0%low visibility |
| 190.123.129.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 190.123.130.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 190.123.143.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 216.25.160.0/20 | Valid | Other IRR onlyRADB | 671 100% |
| 190.123.131.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 190.123.128.0/20 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 2803:d200::/32 | Valid | RIR databaseLACNIC, RADB | 635 100% |
AS-SET
AS28086's PeeringDB record names no 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 16 are in fix.csv.
- Route object: none10
- Route object: RIR5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.123.132.0/24 | No route object for it. A route object for 190.123.128.0/20 with origin AS28086 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28086 in the RIR database for the space. |
| Route object: none | 190.123.133.0/24 | No route object for it. A route object for 190.123.128.0/20 with origin AS28086 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28086 in the RIR database for the space. |
| Route object: none | 190.123.134.0/24 | No route object for it. A route object for 190.123.128.0/20 with origin AS28086 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28086 in the RIR database for the space. |
| Route object: none | 190.123.135.0/24 | No route object for it. A route object for 190.123.128.0/20 with origin AS28086 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28086 in the RIR database for the space. |
| Route object: none | 190.123.140.0/24 | No route object for it. A route object for 190.123.128.0/20 with origin AS28086 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28086 in the RIR database for the space. |
| Route object: none | 190.123.141.0/24 | No route object for it. A route object for 190.123.128.0/20 with origin AS28086 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28086 in the RIR database for the space. |
| Route object: none | 190.123.142.0/24 | No route object for it. A route object for 190.123.128.0/20 with origin AS28086 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28086 in the RIR database for the space. |
| Route object: none | 209.213.176.0/21 | No route object for it. A route object for 209.213.176.0/20 with origin AS28086 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28086 in the RIR database for the space. |
| Route object: none | 190.123.136.0/24 | No route object for it. A route object for 190.123.128.0/20 with origin AS28086 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28086 in the RIR database for the space. |
| Route object: none | 209.213.184.0/21 | Route objects for it name AS13805. A route object for 209.213.176.0/20 with origin AS28086 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28086 in the RIR database for the space. |
| Route object: RIR | 190.123.129.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.123.130.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.123.143.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 216.25.160.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.123.131.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28086 whose prefix no peer sees AS28086 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 209.213.176.0/20 | 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.