Network · data from 2026-11-12
AS199173 TECHNOLUX-AS TechnoLux Ltd.
Registry name: TECHNOLUX-AS TechnoLux Ltd., BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199173, 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.
| 151.237.80.0/23 | Valid | Nonecovered by 151.237.80.0/22 | 673 100% |
| 151.237.82.0/24 | Valid | Nonecovered by 151.237.80.0/22 | 673 100% |
| 151.237.83.0/24 | Valid | Nonecovered by 151.237.80.0/22 | 673 100% |
| 85.187.184.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 85.187.184.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.187.185.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.187.186.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.187.218.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 85.187.224.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 151.237.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 151.237.80.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 151.237.88.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 151.237.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.69.203.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 77.78.157.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.78.158.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.187.218.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.187.224.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.187.225.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.187.227.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.187.230.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS199173 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 8 are in fix.csv.
- Route object: none3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 151.237.80.0/23 | No route object for it. A route object for 151.237.80.0/22 with origin AS199173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199173 in the RIR database for the space. |
| Route object: none | 151.237.82.0/24 | No route object for it. A route object for 151.237.80.0/22 with origin AS199173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199173 in the RIR database for the space. |
| Route object: none | 151.237.83.0/24 | No route object for it. A route object for 151.237.80.0/22 with origin AS199173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199173 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS199173 whose prefix no peer sees AS199173 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.187.219.0/24 | RIPE | Valid |
| 85.187.226.0/24 | RIPE | Valid |
| 85.187.228.0/24 | RIPE | Valid |
| 85.187.229.0/24 | RIPE | Valid |
| 85.187.231.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.