Network · data from 2026-11-12
AS35444 Digicom Albania
Registry name: DigicomAlbania-AS Digicom SHPK, AL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35444, 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.
| 93.93.168.0/24 | Valid | Nonecovered by 93.93.168.0/23 | 673 100% |
| 93.93.169.0/24 | Valid | Nonecovered by 93.93.168.0/23 | 673 100% |
| 93.93.170.0/24 | Valid | Nonecovered by 93.93.170.0/23 | 673 100% |
| 93.93.171.0/24 | Valid | Nonecovered by 93.93.170.0/23 | 673 100% |
| 185.187.0.0/24 | Valid | Nonecovered by 185.187.0.0/23 | 673 100% |
| 185.187.1.0/24 | Valid | Nonecovered by 185.187.0.0/23 | 673 100% |
| 185.187.2.0/23 | Valid | Nonecovered by 185.187.0.0/22 | 673 100% |
| 185.187.3.0/24 | Valid | Nonecovered by 185.187.0.0/22 | 673 100% |
| 185.212.188.0/24 | Valid | Nonecovered by 185.212.188.0/23 | 673 100% |
| 185.212.189.0/24 | Valid | Nonecovered by 185.212.188.0/23 | 673 100% |
| 185.212.190.0/24 | Valid | Nonecovered by 185.212.188.0/22 | 673 100% |
| 185.239.9.0/24 | Valid | Nonecovered by 185.239.8.0/23 | 673 100% |
| 185.239.10.0/24 | Valid | Nonecovered by 185.239.10.0/23 | 673 100% |
| 185.239.11.0/24 | Valid | Nonecovered by 185.239.10.0/23 | 673 100% |
| 185.175.254.0/24 | Valid | Nonecovered by 185.175.252.0/22 | 669 99% |
| 45.93.220.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 80.90.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 81.26.200.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 93.93.168.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 93.93.168.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 93.93.170.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.158.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.187.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.187.0.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.212.188.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.239.8.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.239.8.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.239.10.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 80.90.80.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.90.83.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.90.87.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.90.90.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.90.91.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.26.200.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.26.201.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.26.202.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.26.203.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.26.204.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.132.94.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 81.26.206.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 185.132.92.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 185.175.252.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 81.26.205.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a03:2de0::/32 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS35444'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 35 are in fix.csv.
- Route object: none15
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 93.93.168.0/24 | No route object for it. A route object for 93.93.168.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 93.93.169.0/24 | No route object for it. A route object for 93.93.168.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 93.93.170.0/24 | No route object for it. A route object for 93.93.170.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 93.93.171.0/24 | No route object for it. A route object for 93.93.170.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.187.0.0/24 | No route object for it. A route object for 185.187.0.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.187.1.0/24 | No route object for it. A route object for 185.187.0.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.187.2.0/23 | No route object for it. A route object for 185.187.0.0/22 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.187.3.0/24 | No route object for it. A route object for 185.187.0.0/22 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.212.188.0/24 | No route object for it. A route object for 185.212.188.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.212.189.0/24 | No route object for it. A route object for 185.212.188.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.212.190.0/24 | No route object for it. A route object for 185.212.188.0/22 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.239.9.0/24 | No route object for it. A route object for 185.239.8.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.239.10.0/24 | No route object for it. A route object for 185.239.10.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.239.11.0/24 | No route object for it. A route object for 185.239.10.0/23 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
| Route object: none | 185.175.254.0/24 | No route object for it. A route object for 185.175.252.0/22 with origin AS35444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35444 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS35444 whose prefix no peer sees AS35444 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.90.80.0/21 | RIPE | Invalid: maxLength |
| 80.90.81.0/24 | RIPE | Invalid: maxLength |
| 80.90.82.0/24 | RIPE | Invalid: maxLength |
| 80.90.84.0/24 | RIPE | Invalid: maxLength |
| 80.90.85.0/24 | RIPE | Invalid: maxLength |
| 80.90.86.0/24 | RIPE | Invalid: maxLength |
| 80.90.88.0/21 | RIPE | Invalid: maxLength |
| 80.90.89.0/24 | RIPE | Valid |
| 80.90.92.0/24 | RIPE | Valid |
| 80.90.93.0/24 | RIPE | Invalid: maxLength |
| 80.90.94.0/24 | RIPE | Invalid: maxLength |
| 80.90.95.0/24 | RIPE | Invalid: maxLength |
| 81.26.206.0/24 | RIPE | Valid |
| 81.26.207.0/24 | RIPE | Valid |
| 185.132.92.0/22 | RIPE | No ROA |
| 185.132.93.0/24 | RIPE | Valid |
| 185.132.95.0/24 | RIPE | Valid |
| 185.158.0.0/23 | RIPE | Valid |
| 185.158.2.0/23 | RIPE | Valid |
| 185.212.188.0/23 | RIPE | 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.