Network · data from 2026-11-12
AS3319 URAN User Association of Ukrainian Research and Academic Network URAN
Registry name: URAN User Association of Ukrainian Research and Academic Network URAN, UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3319, 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.
| 77.47.248.0/22 | Invalid: origin | None | 2 0%low visibility |
| 195.178.152.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 77.47.154.0/24 | Valid | Nonecovered by 77.47.152.0/22 | 98 15% |
| 77.47.155.0/24 | Valid | Nonecovered by 77.47.152.0/22 | 98 15% |
| 195.178.134.0/24 | Valid | Nonecovered by 195.178.132.0/22 | 1 0%low visibility |
| 103.11.70.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 115.167.59.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 185.143.56.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.143.57.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.143.58.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.143.59.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.129.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.132.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.132.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.133.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.135.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.136.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.139.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.144.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.147.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.154.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.178.156.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.111.194.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.111.207.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.111.216.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.111.217.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.47.152.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 77.47.210.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.47.211.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.47.248.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.47.249.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.47.252.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.47.253.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.47.254.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.47.255.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 195.178.128.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 113.203.214.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 113.203.216.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 195.178.148.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 195.178.149.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 77.47.242.0/24 | Valid | RIR databaseRIPE | 662 98% |
| 195.178.146.0/24 | Valid | RIR databaseRIPE | 645 96% |
| 195.178.143.0/24 | Valid | RIR databaseRIPE | 628 93% |
| 77.47.142.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 195.178.130.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS3319 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 8 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 77.47.248.0/22 | ROAs covering it name AS25500, not AS3319. If AS3319 should announce it, add a ROA for AS3319. |
| Route object: none | 77.47.248.0/22 | No route object for it. Add a route object with origin AS3319 in the RIR database for the space. |
| ROA: none | 195.178.152.0/22 | No ROA covers it. Add a ROA for AS3319, maxLength 22. |
| Route object: none | 77.47.154.0/24 | No route object for it. A route object for 77.47.152.0/22 with origin AS3319 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3319 in the RIR database for the space. |
| Route object: none | 77.47.155.0/24 | No route object for it. A route object for 77.47.152.0/22 with origin AS3319 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3319 in the RIR database for the space. |
| Route object: none | 195.178.134.0/24 | No route object for it. A route object for 195.178.132.0/22 with origin AS3319 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3319 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS3319 whose prefix no peer sees AS3319 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 195.178.128.0/22 | RIPE | Valid |
| 212.111.215.0/24 | 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.