Network · data from 2026-11-12
AS34312 ARMNET-AS FOP Boyko Oleg Mikhaylovich
Registry name: ARMNET-AS FOP Boyko Oleg Mikhaylovich, UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34312, 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.
| 193.111.6.0/23 | Valid | Other origin only | 671 100% |
| 89.200.248.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 195.95.207.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.95.206.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS34312 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 | 193.111.6.0/23 | Route objects for it name AS24726. Add a route object with origin AS34312 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS34312 whose prefix no peer sees AS34312 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.200.248.0/22 | RIPE | Invalid: maxLength |
| 89.200.251.0/24 | RIPE | Invalid: maxLength |
| 89.200.252.0/24 | RIPE | Invalid: maxLength |
| 195.95.206.0/23 | 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.