Network · data from 2026-11-12
AS208664 EUB-AS JSC Eurasian Bank
Registry name: EUB-AS JSC Eurasian Bank, KZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208664, 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.
| 212.154.157.0/25 | Invalid: origin | None | 1 0%low visibility |
| 212.154.157.128/26 | Invalid: origin | None | 1 0%low visibility |
| 91.201.10.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.207.8.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS208664 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 4 are in fix.csv.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 212.154.157.0/25 | ROAs covering it name AS9198, AS50482, not AS208664. If AS208664 should announce it, add a ROA for AS208664. |
| Route object: none | 212.154.157.0/25 | No route object for it. Add a route object with origin AS208664 in the RIR database for the space. |
| ROA: origin | 212.154.157.128/26 | ROAs covering it name AS9198, AS50482, not AS208664. If AS208664 should announce it, add a ROA for AS208664. |
| Route object: none | 212.154.157.128/26 | No route object for it. Add a route object with origin AS208664 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS208664 is announced.
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.