Network · data from 2026-11-12
AS27903 AS27903 - DIGICEL S.A. DE C.V.
Registry name: AS27903 - DIGICEL S.A. DE C.V., SV · not in PeeringDB
24IPv4 routes
91.7% RPKI valid · 29.2% with a route object
0IPv6 routes
2RPKI invalid
0 origin · 2 maxLength
0No ROA
17 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS27903, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS27903, 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.
| 38.135.202.0/24 | Invalid: maxLength | Nonecovered by 38.135.200.0/22 | 4 1%low visibility |
| 38.135.203.0/24 | Invalid: maxLength | Nonecovered by 38.135.200.0/22 | 4 1%low visibility |
| 170.0.176.0/23 | Valid | Nonecovered by 170.0.176.0/22 | 672 100% |
| 170.0.176.0/24 | Valid | Nonecovered by 170.0.176.0/22 | 672 100% |
| 170.0.177.0/24 | Valid | Nonecovered by 170.0.176.0/22 | 672 100% |
| 170.0.178.0/23 | Valid | Nonecovered by 170.0.176.0/22 | 672 100% |
| 170.0.178.0/24 | Valid | Nonecovered by 170.0.176.0/22 | 672 100% |
| 170.0.179.0/24 | Valid | Nonecovered by 170.0.176.0/22 | 672 100% |
| 200.89.84.0/24 | Valid | Nonecovered by 200.89.84.0/22 | 672 100% |
| 38.56.208.0/24 | Valid | Nonecovered by 38.56.208.0/22 | 671 100% |
| 38.56.209.0/24 | Valid | Nonecovered by 38.56.208.0/22 | 671 100% |
| 38.56.210.0/24 | Valid | Nonecovered by 38.56.208.0/22 | 671 100% |
| 38.56.211.0/24 | Valid | Nonecovered by 38.56.208.0/22 | 671 100% |
| 200.89.82.0/24 | Valid | Nonecovered by 200.89.80.0/21 | 671 100% |
| 200.89.83.0/24 | Valid | Nonecovered by 200.89.80.0/21 | 671 100% |
| 200.89.85.0/24 | Valid | Nonecovered by 200.89.84.0/22 | 671 100% |
| 200.89.87.0/24 | Valid | Nonecovered by 200.89.84.0/22 | 668 99% |
| 200.89.86.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 38.7.12.0/22 | Valid | RIR databaseARIN | 672 100% |
| 38.135.200.0/22 | Valid | RIR databaseARIN | 672 100% |
| 138.255.152.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 170.0.176.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 200.89.80.0/21 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 38.56.208.0/22 | Valid | RIR databaseARIN | 6 1%low visibility |
AS-SET
AS27903 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 26 are in fix.csv.
- ROA: maxLength2
- Route object: none17
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 38.135.202.0/24 | ROA 38.135.200.0/22 AS27903 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 38.135.202.0/24. |
| Route object: none | 38.135.202.0/24 | No route object for it. A route object for 38.135.200.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| ROA: maxLength | 38.135.203.0/24 | ROA 38.135.200.0/22 AS27903 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 38.135.203.0/24. |
| Route object: none | 38.135.203.0/24 | No route object for it. A route object for 38.135.200.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 170.0.176.0/23 | No route object for it. A route object for 170.0.176.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 170.0.176.0/24 | No route object for it. A route object for 170.0.176.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 170.0.177.0/24 | No route object for it. A route object for 170.0.176.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 170.0.178.0/23 | No route object for it. A route object for 170.0.176.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 170.0.178.0/24 | No route object for it. A route object for 170.0.176.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 170.0.179.0/24 | No route object for it. A route object for 170.0.176.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 200.89.84.0/24 | No route object for it. A route object for 200.89.84.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 38.56.208.0/24 | No route object for it. A route object for 38.56.208.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 38.56.209.0/24 | No route object for it. A route object for 38.56.208.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 38.56.210.0/24 | No route object for it. A route object for 38.56.208.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 38.56.211.0/24 | No route object for it. A route object for 38.56.208.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 200.89.82.0/24 | No route object for it. A route object for 200.89.80.0/21 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 200.89.83.0/24 | No route object for it. A route object for 200.89.80.0/21 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 200.89.85.0/24 | No route object for it. A route object for 200.89.84.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: none | 200.89.87.0/24 | No route object for it. A route object for 200.89.84.0/22 with origin AS27903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27903 in the RIR database for the space. |
| Route object: RIR | 200.89.86.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27903 whose prefix no peer sees AS27903 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.232.48.0/22 | RADB | No ROA |
| 168.243.224.0/20 | RADB | No ROA |
| 168.243.224.0/24 | RADB | No ROA |
| 168.243.226.0/24 | RADB | No ROA |
| 200.89.84.0/22 | RADB | Valid |
| 2803:fa40::/32 | LACNIC, RADB | Valid |
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.