Network · data from 2026-11-12
AS15397 OneCrnaGoraDoo One Crna Gora DOO
Registry name: OneCrnaGoraDoo One Crna Gora DOO, ME · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15397, 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.
| 185.179.52.0/23 | No ROA | Other origin only | 482 72% |
| 79.143.96.0/21 | No ROA | Other origin onlycovered by 79.143.96.0/20 | 1 0%low visibility |
| 79.143.96.168/29 | No ROA | Nonecovered by 79.143.96.0/24 | 1 0%low visibility |
| 79.143.104.0/21 | No ROA | Other origin onlycovered by 79.143.96.0/20 | 1 0%low visibility |
| 79.143.96.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 2a01:5da0::/32 | No ROA | RIR databaseRIPE | 634 100% |
| 2a03:16a0::/32 | No ROA | RIR databaseRIPE | 634 100% |
| 79.143.101.0/24 | No ROA | RIR databaseRIPE | 1 0%low visibility |
| 79.143.103.0/24 | No ROA | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS15397 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 29 are in fix.csv.
- ROA: none9
- Route object: none4
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.179.52.0/23 | No ROA covers it. Add a ROA for AS15397, maxLength 23. |
| Route object: none | 185.179.52.0/23 | Route objects for it name AS19905, AS198949, AS208568. Add a route object with origin AS15397 in the RIR database for the space. |
| ROA: none | 79.143.96.0/21 | No ROA covers it. Add a ROA for AS15397, maxLength 21. |
| Route object: none | 79.143.96.0/21 | Route objects for it name AS19905, AS198949. A route object for 79.143.96.0/20 with origin AS15397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15397 in the RIR database for the space. |
| ROA: none | 79.143.96.168/29 | No ROA covers it. Add a ROA for AS15397, maxLength 29. |
| Route object: none | 79.143.96.168/29 | No route object for it. A route object for 79.143.96.0/24 with origin AS15397 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS15397 in the RIR database for the space. |
| ROA: none | 79.143.104.0/21 | No ROA covers it. Add a ROA for AS15397, maxLength 21. |
| Route object: none | 79.143.104.0/21 | Route objects for it name AS198949. A route object for 79.143.96.0/20 with origin AS15397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15397 in the RIR database for the space. |
| ROA: none | 79.143.96.0/20 | No ROA covers it. Add a ROA for AS15397, maxLength 20. |
| ROA: none | 2a01:5da0::/32 | No ROA covers it. Add a ROA for AS15397, maxLength 32. |
| ROA: none | 2a03:16a0::/32 | No ROA covers it. Add a ROA for AS15397, maxLength 32. |
| ROA: none | 79.143.101.0/24 | No ROA covers it. Add a ROA for AS15397, maxLength 24. |
| ROA: none | 79.143.103.0/24 | No ROA covers it. Add a ROA for AS15397, maxLength 24. |
Route objects not announced
Route objects with origin AS15397 whose prefix no peer sees AS15397 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 79.143.96.0/24 | RIPE | No ROA |
| 79.143.97.0/24 | RIPE | No ROA |
| 79.143.98.0/24 | RIPE | No ROA |
| 79.143.99.0/24 | RIPE | No ROA |
| 79.143.100.0/24 | RIPE | No ROA |
| 79.143.102.0/24 | RIPE | No ROA |
| 79.143.104.0/24 | RIPE | No ROA |
| 79.143.105.0/24 | RIPE | No ROA |
| 79.143.106.0/24 | RIPE | No ROA |
| 79.143.107.0/24 | RIPE | No ROA |
| 79.143.108.0/24 | RIPE | No ROA |
| 79.143.109.0/24 | RIPE | No ROA |
| 79.143.110.0/24 | RIPE | No ROA |
| 79.143.111.0/24 | RIPE | No ROA |
| 185.179.54.0/24 | RIPE | No ROA |
| 185.179.55.0/24 | RIPE | No ROA |
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.