Network · data from 2026-11-12
AS25211 EuroCrypt-AS "Euro Crypt" EOOD
Registry name: EuroCrypt-AS "Euro Crypt" EOOD, BG · not in PeeringDB
34IPv4 routes
97.1% RPKI valid · 67.6% with a route object
0IPv6 routes
1RPKI invalid
1 origin · 0 maxLength
0No ROA
11 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
36Route objects not announced
registered with origin AS25211, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS25211, 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.152.216.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 78.159.136.0/24 | Valid | Nonecovered by 78.159.136.0/22 | 673 100% |
| 78.159.137.0/24 | Valid | Nonecovered by 78.159.136.0/22 | 673 100% |
| 78.159.138.0/24 | Valid | Nonecovered by 78.159.136.0/22 | 673 100% |
| 78.159.139.0/24 | Valid | Nonecovered by 78.159.136.0/22 | 673 100% |
| 94.26.28.0/24 | Valid | Nonecovered by 94.26.28.0/23 | 673 100% |
| 94.26.29.0/24 | Valid | Nonecovered by 94.26.28.0/23 | 673 100% |
| 94.26.76.0/24 | Valid | Nonecovered by 94.26.76.0/22 | 673 100% |
| 94.26.77.0/24 | Valid | Nonecovered by 94.26.76.0/22 | 673 100% |
| 94.26.78.0/24 | Valid | Nonecovered by 94.26.76.0/22 | 673 100% |
| 94.26.79.0/24 | Valid | Nonecovered by 94.26.76.0/22 | 673 100% |
| 78.159.128.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.159.149.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.159.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.159.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 78.159.153.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.159.154.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.159.155.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.159.157.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.159.158.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.159.159.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.92.44.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.92.50.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.92.51.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.92.52.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.92.53.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.26.42.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.26.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.160.36.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.96.252.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.96.253.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.96.255.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.92.45.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 94.26.37.0/24 | Valid | RIR databaseRIPE | 3 0%low visibility |
AS-SET
AS25211 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 48 are in fix.csv.
- ROA: origin1
- Route object: none11
- Route object: not announced36
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 93.152.216.0/24 | ROAs covering it name AS27176, AS207043, not AS25211. If AS25211 should announce it, add a ROA for AS25211. |
| Route object: none | 93.152.216.0/24 | Route objects for it name AS27176, AS207043. Add a route object with origin AS25211 in the RIR database for the space. |
| Route object: none | 78.159.136.0/24 | No route object for it. A route object for 78.159.136.0/22 with origin AS25211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25211 in the RIR database for the space. |
| Route object: none | 78.159.137.0/24 | No route object for it. A route object for 78.159.136.0/22 with origin AS25211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25211 in the RIR database for the space. |
| Route object: none | 78.159.138.0/24 | No route object for it. A route object for 78.159.136.0/22 with origin AS25211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25211 in the RIR database for the space. |
| Route object: none | 78.159.139.0/24 | No route object for it. A route object for 78.159.136.0/22 with origin AS25211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25211 in the RIR database for the space. |
| Route object: none | 94.26.28.0/24 | No route object for it. A route object for 94.26.28.0/23 with origin AS25211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25211 in the RIR database for the space. |
| Route object: none | 94.26.29.0/24 | No route object for it. A route object for 94.26.28.0/23 with origin AS25211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25211 in the RIR database for the space. |
| Route object: none | 94.26.76.0/24 | No route object for it. A route object for 94.26.76.0/22 with origin AS25211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25211 in the RIR database for the space. |
| Route object: none | 94.26.77.0/24 | No route object for it. A route object for 94.26.76.0/22 with origin AS25211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25211 in the RIR database for the space. |
| Route object: none | 94.26.78.0/24 | No route object for it. A route object for 94.26.76.0/22 with origin AS25211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25211 in the RIR database for the space. |
| Route object: none | 94.26.79.0/24 | No route object for it. A route object for 94.26.76.0/22 with origin AS25211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25211 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25211 whose prefix no peer sees AS25211 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.141.235.0/24 | RIPE | Valid |
| 78.159.129.0/24 | RIPE | Valid |
| 78.159.136.0/22 | RIPE | No ROA |
| 78.159.152.0/24 | RIPE | Invalid: maxLength |
| 78.159.156.0/24 | RIPE | Valid |
| 85.239.144.0/24 | RIPE | Valid |
| 85.239.147.0/24 | RIPE | Valid |
| 85.239.149.0/24 | RIPE | Valid |
| 87.246.28.0/22 | RIPE | Invalid: origin |
| 93.152.208.0/24 | RIPE | Invalid: origin |
| 93.152.209.0/24 | RIPE | Valid |
| 93.152.212.0/24 | RIPE | Valid |
| 93.152.213.0/24 | RIPE | Valid |
| 93.152.214.0/24 | RIPE | Valid |
| 93.152.218.0/24 | RIPE | Valid |
| 93.152.222.0/24 | RIPE | Valid |
| 93.152.226.0/24 | RIPE | Valid |
| 93.152.227.0/24 | RIPE | Valid |
| 93.152.230.0/24 | RIPE | Valid |
| 94.26.3.0/24 | RIPE | Valid |
| 94.26.28.0/23 | RIPE | No ROA |
| 94.26.32.0/24 | RIPE | Valid |
| 94.26.68.0/24 | RIPE | Valid |
| 94.26.69.0/24 | RIPE | Valid |
| 94.26.70.0/24 | RIPE | Valid |
| 94.26.76.0/22 | RIPE | Valid |
| 94.26.88.0/24 | RIPE | Valid |
| 94.26.89.0/24 | RIPE | Valid |
| 94.190.195.0/24 | RIPE | Valid |
| 109.160.33.0/24 | RIPE | Invalid: maxLength |
| 109.160.37.0/24 | RIPE | Valid |
| 109.160.38.0/24 | RIPE | Valid |
| 109.160.39.0/24 | RIPE | Valid |
| 109.160.40.0/24 | RIPE | Valid |
| 185.96.254.0/24 | RIPE | Valid |
| 212.102.105.0/24 | 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.