Network · data from 2026-11-12
AS28387 Blacom
Registry name: AS28387 - Computadoras y Servicios Especiales SA de CV, MX · PeeringDB
20IPv4 routes
100.0% RPKI valid · 50.0% with a route object
4IPv6 routes
100.0% RPKI valid · 25.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
13 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS28387, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS28387, 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.
| 201.139.177.0/24 | Valid | Nonecovered by 201.139.176.0/21 | 673 100% |
| 201.139.183.0/24 | Valid | Nonecovered by 201.139.176.0/21 | 672 100% |
| 201.131.200.0/24 | Valid | Nonecovered by 201.131.200.0/22 | 671 100% |
| 201.139.178.0/24 | Valid | Nonecovered by 201.139.176.0/21 | 671 100% |
| 201.139.179.0/24 | Valid | Nonecovered by 201.139.176.0/21 | 671 100% |
| 201.139.180.0/24 | Valid | Nonecovered by 201.139.176.0/21 | 671 100% |
| 201.139.181.0/24 | Valid | Nonecovered by 201.139.176.0/21 | 671 100% |
| 201.139.182.0/24 | Valid | Nonecovered by 201.139.176.0/21 | 671 100% |
| 2806:300:1::/48 | Valid | Nonecovered by 2806:300::/32 | 633 100% |
| 2806:300:10::/48 | Valid | Nonecovered by 2806:300::/32 | 633 100% |
| 2806:300:11::/48 | Valid | Nonecovered by 2806:300::/32 | 633 100% |
| 201.139.176.0/24 | Valid | Nonecovered by 201.139.176.0/21 | 2 0%low visibility |
| 201.139.180.0/22 | Valid | Nonecovered by 201.139.176.0/21 | 2 0%low visibility |
| 201.131.201.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.174.84.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.174.85.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.174.86.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.174.87.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 201.131.202.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 201.131.203.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.174.84.0/22 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 201.131.200.0/22 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 201.139.176.0/21 | Valid | RIR databaseLACNIC | 673 100% |
| 2806:300::/32 | Valid | RIR databaseLACNIC, RADB | 633 100% |
AS-SET
AS28387'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 26 are in fix.csv.
- Route object: none13
- Route object: RIR7
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 201.139.177.0/24 | No route object for it. A route object for 201.139.176.0/21 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 201.139.183.0/24 | No route object for it. A route object for 201.139.176.0/21 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 201.131.200.0/24 | No route object for it. A route object for 201.131.200.0/22 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 201.139.178.0/24 | No route object for it. A route object for 201.139.176.0/21 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 201.139.179.0/24 | No route object for it. A route object for 201.139.176.0/21 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 201.139.180.0/24 | No route object for it. A route object for 201.139.176.0/21 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 201.139.181.0/24 | No route object for it. A route object for 201.139.176.0/21 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 201.139.182.0/24 | No route object for it. A route object for 201.139.176.0/21 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 2806:300:1::/48 | No route object for it. A route object for 2806:300::/32 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 2806:300:10::/48 | No route object for it. A route object for 2806:300::/32 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 2806:300:11::/48 | No route object for it. A route object for 2806:300::/32 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 201.139.176.0/24 | No route object for it. A route object for 201.139.176.0/21 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: none | 201.139.180.0/22 | No route object for it. A route object for 201.139.176.0/21 with origin AS28387 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28387 in the RIR database for the space. |
| Route object: RIR | 201.131.201.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.174.84.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.174.85.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.174.86.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.174.87.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.202.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.131.203.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28387 whose prefix no peer sees AS28387 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 148.219.0.0/16 | RADB | No ROA |
| 148.219.128.0/18 | RADB | No ROA |
| 2806:300::/48 | RADB | Valid |
| 2806:32b::/32 | LACNIC | Valid |
| 2806:347::/32 | RADB | No ROA |
| 2806:3a6::/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.