Network · data from 2026-11-12
AS43595 UGRESHA-NET-AS Ugresha Network Ltd.
Registry name: UGRESHA-NET-AS Ugresha Network Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43595, 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.
| 91.195.60.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 176.107.240.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 2a06:4180:1::/48 | Valid | None | 328 52% |
AS-SET
AS43595 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 7 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.195.60.0/23 | No ROA covers it. Add a ROA for AS43595, maxLength 23. |
| ROA: none | 176.107.240.0/21 | No ROA covers it. Add a ROA for AS43595, maxLength 21. |
| Route object: none | 2a06:4180:1::/48 | No route object for it. Add a route object with origin AS43595 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS43595 whose prefix no peer sees AS43595 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.195.60.0/24 | RIPE | No ROA |
| 91.195.61.0/24 | RIPE | No ROA |
| 176.107.240.0/22 | RIPE | No ROA |
| 176.107.244.0/22 | 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.