Network · data from 2026-11-12
AS47196 Garant-Park-Internet Garant-Park-Internet LLC
Registry name: Garant-Park-Internet Garant-Park-Internet LLC, RU · not in PeeringDB
44IPv4 routes
88.6% RPKI valid · 86.4% with a route object
2IPv6 routes
50.0% RPKI valid · 100.0% with a route object
1RPKI invalid
1 origin · 0 maxLength
5No ROA
6 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS47196, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS47196, 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.
| 46.173.220.0/22 | Invalid: origin | Other origin only | 141 21% |
| 91.203.192.0/23 | No ROA | Other origin only | 672 100% |
| 91.203.194.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 195.22.148.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 195.22.152.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 2a03:5a00:1::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 195.22.148.0/24 | Valid | Nonecovered by 195.22.148.0/23 | 673 100% |
| 195.22.149.0/24 | Valid | Nonecovered by 195.22.148.0/23 | 673 100% |
| 195.22.152.0/24 | Valid | Nonecovered by 195.22.152.0/23 | 673 100% |
| 195.22.153.0/24 | Valid | Nonecovered by 195.22.152.0/23 | 673 100% |
| 45.143.136.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.143.136.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.143.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.143.139.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.210.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.212.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.213.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.217.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.219.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.203.192.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.203.193.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.203.194.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.203.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.128.120.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.128.120.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.128.121.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.128.122.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.128.123.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.128.124.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.128.125.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.128.126.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.128.127.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.173.212.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 46.173.214.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 46.173.216.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 46.173.218.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 195.128.124.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 46.173.211.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.143.138.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a0f:6f80::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS47196 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 12 are in fix.csv.
- ROA: origin1
- ROA: none5
- Route object: none6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 46.173.220.0/22 | ROAs covering it name AS56364, not AS47196. If AS47196 should announce it, add a ROA for AS47196. |
| Route object: none | 46.173.220.0/22 | Route objects for it name AS56364. Add a route object with origin AS47196 in the RIR database for the space. |
| ROA: none | 91.203.192.0/23 | No ROA covers it. Add a ROA for AS47196, maxLength 23. |
| Route object: none | 91.203.192.0/23 | Route objects for it name AS56364. Add a route object with origin AS47196 in the RIR database for the space. |
| ROA: none | 91.203.194.0/23 | No ROA covers it. Add a ROA for AS47196, maxLength 23. |
| ROA: none | 195.22.148.0/23 | No ROA covers it. Add a ROA for AS47196, maxLength 23. |
| ROA: none | 195.22.152.0/23 | No ROA covers it. Add a ROA for AS47196, maxLength 23. |
| ROA: none | 2a03:5a00:1::/48 | No ROA covers it. Add a ROA for AS47196, maxLength 48. |
| Route object: none | 195.22.148.0/24 | No route object for it. A route object for 195.22.148.0/23 with origin AS47196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47196 in the RIR database for the space. |
| Route object: none | 195.22.149.0/24 | No route object for it. A route object for 195.22.148.0/23 with origin AS47196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47196 in the RIR database for the space. |
| Route object: none | 195.22.152.0/24 | No route object for it. A route object for 195.22.152.0/23 with origin AS47196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47196 in the RIR database for the space. |
| Route object: none | 195.22.153.0/24 | No route object for it. A route object for 195.22.152.0/23 with origin AS47196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47196 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS47196 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.