Network · data from 2026-11-12
AS265606 DIGY NETWORKS
Registry name: AS265606 - DIGY NETWORKS, MX · PeeringDB
20IPv4 routes
100.0% RPKI valid · 60.0% with a route object
2IPv6 routes
100.0% RPKI valid · 50.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
9 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS265606, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS265606, 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.
| 45.188.124.0/24 | Valid | Nonecovered by 45.188.124.0/22 | 672 100% |
| 45.188.125.0/24 | Valid | Nonecovered by 45.188.124.0/22 | 672 100% |
| 45.188.126.0/23 | Valid | Nonecovered by 45.188.124.0/22 | 672 100% |
| 45.188.126.0/24 | Valid | Nonecovered by 45.188.124.0/22 | 672 100% |
| 45.188.127.0/24 | Valid | Nonecovered by 45.188.124.0/22 | 672 100% |
| 200.71.108.0/24 | Valid | Nonecovered by 200.71.108.0/22 | 671 100% |
| 200.225.60.0/24 | Valid | Nonecovered by 200.225.60.0/23 | 671 100% |
| 200.225.61.0/24 | Valid | Nonecovered by 200.225.60.0/23 | 671 100% |
| 2806:362:200::/40 | Valid | Nonecovered by 2806:362::/32 | 604 95% |
| 200.71.109.0/24 | Valid | Other IRR onlyALTDB | 671 100% |
| 200.71.110.0/24 | Valid | Other IRR onlyALTDB, RADB | 671 100% |
| 200.71.111.0/24 | Valid | Other IRR onlyALTDB | 671 100% |
| 38.156.128.0/18 | Valid | RIR databaseARIN | 673 100% |
| 148.224.30.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 204.153.206.0/23 | Valid | RIR databaseLACNIC | 673 100% |
| 45.188.124.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 148.230.4.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 148.230.15.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 190.2.191.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 200.71.108.0/22 | Valid | RIR databaseALTDB, LACNIC, RADB | 671 100% |
| 200.225.60.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 2806:362::/32 | Valid | RIR databaseALTDB, LACNIC | 631 99% |
AS-SET
AS265606'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 14 are in fix.csv.
- Route object: none9
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.188.124.0/24 | No route object for it. A route object for 45.188.124.0/22 with origin AS265606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265606 in the RIR database for the space. |
| Route object: none | 45.188.125.0/24 | No route object for it. A route object for 45.188.124.0/22 with origin AS265606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265606 in the RIR database for the space. |
| Route object: none | 45.188.126.0/23 | No route object for it. A route object for 45.188.124.0/22 with origin AS265606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265606 in the RIR database for the space. |
| Route object: none | 45.188.126.0/24 | No route object for it. A route object for 45.188.124.0/22 with origin AS265606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265606 in the RIR database for the space. |
| Route object: none | 45.188.127.0/24 | No route object for it. A route object for 45.188.124.0/22 with origin AS265606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265606 in the RIR database for the space. |
| Route object: none | 200.71.108.0/24 | No route object for it. A route object for 200.71.108.0/22 with origin AS265606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265606 in the RIR database for the space. |
| Route object: none | 200.225.60.0/24 | No route object for it. A route object for 200.225.60.0/23 with origin AS265606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265606 in the RIR database for the space. |
| Route object: none | 200.225.61.0/24 | No route object for it. A route object for 200.225.60.0/23 with origin AS265606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265606 in the RIR database for the space. |
| Route object: none | 2806:362:200::/40 | No route object for it. A route object for 2806:362::/32 with origin AS265606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265606 in the RIR database for the space. |
| Route object: RIR | 200.71.109.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 200.71.110.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.71.111.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265606 whose prefix no peer sees AS265606 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.36.152.0/22 | RADB | No ROA |
| 2806:3ac::/32 | LACNIC | 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.