Network · data from 2026-11-12
AS34065 NORMA-PLUS-AS Individual Entrepreneur Tetiana Markova
Registry name: NORMA-PLUS-AS Individual Entrepreneur Tetiana Markova, UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34065, 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.
| 195.238.188.10/32 | No ROA | Nonecovered by 195.238.188.0/24 | 4 1%low visibility |
| 194.28.70.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.28.71.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.17.208.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 194.28.68.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 194.28.69.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.238.188.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 195.238.188.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.238.189.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.238.190.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.238.191.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 194.28.68.0/22 | No ROA | RIR databaseRIPE | 668 99% |
AS-SET
AS34065 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 13 are in fix.csv.
- ROA: none12
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.238.188.10/32 | No ROA covers it. Add a ROA for AS34065, maxLength 32. |
| Route object: none | 195.238.188.10/32 | No route object for it. A route object for 195.238.188.0/24 with origin AS34065 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34065 in the RIR database for the space. |
| ROA: none | 194.28.70.0/24 | No ROA covers it. Add a ROA for AS34065, maxLength 24. |
| ROA: none | 194.28.71.0/24 | No ROA covers it. Add a ROA for AS34065, maxLength 24. |
| ROA: none | 193.17.208.0/24 | No ROA covers it. Add a ROA for AS34065, maxLength 24. |
| ROA: none | 194.28.68.0/24 | No ROA covers it. Add a ROA for AS34065, maxLength 24. |
| ROA: none | 194.28.69.0/24 | No ROA covers it. Add a ROA for AS34065, maxLength 24. |
| ROA: none | 195.238.188.0/22 | No ROA covers it. Add a ROA for AS34065, maxLength 22. |
| ROA: none | 195.238.188.0/24 | No ROA covers it. Add a ROA for AS34065, maxLength 24. |
| ROA: none | 195.238.189.0/24 | No ROA covers it. Add a ROA for AS34065, maxLength 24. |
| ROA: none | 195.238.190.0/24 | No ROA covers it. Add a ROA for AS34065, maxLength 24. |
| ROA: none | 195.238.191.0/24 | No ROA covers it. Add a ROA for AS34065, maxLength 24. |
| ROA: none | 194.28.68.0/22 | No ROA covers it. Add a ROA for AS34065, maxLength 22. |
Route objects not announced
Every route object with origin AS34065 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.