Network · data from 2026-11-12
AS42313 One Albania
Registry name: ONEALBANIA-AS ONE ALBANIA SH.A., AL · PeeringDB
72IPv4 routes
100.0% RPKI valid · 83.3% with a route object
17IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
12 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
18Route objects not announced
registered with origin AS42313, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS42313, 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.
| 79.106.40.0/24 | Valid | Nonecovered by 79.106.32.0/19 | 673 100% |
| 79.106.48.0/24 | Valid | Nonecovered by 79.106.32.0/19 | 673 100% |
| 79.106.50.0/24 | Valid | Nonecovered by 79.106.32.0/19 | 673 100% |
| 79.106.75.0/24 | Valid | Nonecovered by 79.106.64.0/19 | 673 100% |
| 79.106.203.0/24 | Valid | Nonecovered by 79.106.192.0/19 | 673 100% |
| 79.106.212.0/24 | Valid | Nonecovered by 79.106.192.0/19 | 673 100% |
| 79.106.216.0/24 | Valid | Nonecovered by 79.106.192.0/19 | 673 100% |
| 79.106.225.0/24 | Valid | Nonecovered by 79.106.224.0/19 | 673 100% |
| 79.106.226.0/24 | Valid | Nonecovered by 79.106.224.0/19 | 673 100% |
| 185.171.144.0/22 | Valid | None | 673 100% |
| 79.106.79.0/24 | Valid | Nonecovered by 79.106.64.0/19 | 672 100% |
| 79.106.162.0/24 | Valid | Nonecovered by 79.106.160.0/19 | 3 0%low visibility |
| 79.106.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.0.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.42.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.56.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.77.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.96.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.96.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.98.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.117.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.118.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.120.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.122.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.123.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.124.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.125.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.126.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.127.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.160.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.196.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.207.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.211.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.218.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.224.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.228.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.229.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.230.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.232.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.240.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.240.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.242.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.244.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.246.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.255.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.171.144.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.171.146.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.171.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.24.240.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 217.24.248.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 217.24.248.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.24.254.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.106.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 79.106.0.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 79.106.84.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 79.106.102.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 79.106.104.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 79.106.128.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 79.106.192.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 217.24.240.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 79.106.128.0/19 | Valid | RIR databaseRIPE | 670 100% |
| 2a05:fdc0::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc0:1000::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc0:3100::/40 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc1::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc2::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc2:1000::/36 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc2:2000::/36 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc2:3000::/36 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc2:4000::/36 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc2:5000::/36 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc2:6000::/36 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc2:7000::/36 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc2:8000::/36 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc2:9000::/36 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:fdc0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a05:fdc0:2200::/40 | Valid | RIR databaseRIPE | 631 99% |
| 2a05:fdc0:3200::/40 | Valid | RIR databaseRIPE | 631 99% |
| 79.106.101.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 79.106.176.0/21 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS42313'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 30 are in fix.csv.
- Route object: none12
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 79.106.40.0/24 | No route object for it. A route object for 79.106.32.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 79.106.48.0/24 | No route object for it. A route object for 79.106.32.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 79.106.50.0/24 | No route object for it. A route object for 79.106.32.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 79.106.75.0/24 | No route object for it. A route object for 79.106.64.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 79.106.203.0/24 | No route object for it. A route object for 79.106.192.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 79.106.212.0/24 | No route object for it. A route object for 79.106.192.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 79.106.216.0/24 | No route object for it. A route object for 79.106.192.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 79.106.225.0/24 | No route object for it. A route object for 79.106.224.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 79.106.226.0/24 | No route object for it. A route object for 79.106.224.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 185.171.144.0/22 | No route object for it. Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 79.106.79.0/24 | No route object for it. A route object for 79.106.64.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
| Route object: none | 79.106.162.0/24 | No route object for it. A route object for 79.106.160.0/19 with origin AS42313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42313 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS42313 whose prefix no peer sees AS42313 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 79.106.16.0/20 | RIPE | Invalid: maxLength |
| 79.106.16.0/23 | RIPE | Invalid: maxLength |
| 79.106.18.0/23 | RIPE | Invalid: maxLength |
| 79.106.37.0/24 | RIPE | Valid |
| 79.106.94.0/23 | RIPE | Valid |
| 79.106.95.0/24 | RIPE | Valid |
| 79.106.103.0/24 | RIPE | Valid |
| 79.106.105.0/24 | RIPE | Invalid: maxLength |
| 79.106.106.0/24 | RIPE | Invalid: maxLength |
| 79.106.111.0/24 | RIPE | Invalid: maxLength |
| 79.106.194.0/23 | RIPE | Valid |
| 79.106.195.0/24 | RIPE | Valid |
| 79.106.204.0/24 | RIPE | Valid |
| 79.106.205.0/24 | RIPE | Valid |
| 79.106.210.0/24 | RIPE | Valid |
| 79.106.254.0/24 | RIPE | Valid |
| 2a05:fdc0:2100::/40 | RIPE | Valid |
| 2a05:fdc0:2300::/40 | 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.