Network · data from 2026-11-12
AS394881 EK-HOSTING - EK HOSTING INC
Registry name: EK-HOSTING - EK HOSTING INC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394881, 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.
| 38.90.12.0/22 | Valid | Nonecovered by 38.90.0.0/20 | 673 100% |
| 203.23.177.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 45.119.4.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.23.176.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS394881 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 5 are in fix.csv.
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 38.90.12.0/22 | No route object for it. A route object for 38.90.0.0/20 with origin AS394881 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394881 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394881 whose prefix no peer sees AS394881 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.90.0.0/20 | ARIN | Valid |
| 103.6.108.0/22 | RADB | Valid |
| 103.133.94.0/24 | APNIC | Valid |
| 203.34.110.0/24 | APNIC | 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.