Network · data from 2026-11-12
AS207569 I-SERVERS-NORTH-EU IHOR HOSTING LTD
Registry name: I-SERVERS-NORTH-EU IHOR HOSTING LTD, GB · not in PeeringDB
73IPv4 routes
98.6% RPKI valid · 95.9% with a route object
4IPv6 routes
100.0% RPKI valid · 100.0% with a route object
1RPKI invalid
1 origin · 0 maxLength
0No ROA
3 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
14Route objects not announced
registered with origin AS207569, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS207569, 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.
| 5.101.88.0/24 | Invalid: origin | Other origin only | 137 20% |
| 194.63.140.0/24 | Valid | Other origin only | 650 97% |
| 194.63.142.0/24 | Valid | Other origin only | 650 97% |
| 45.9.74.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.132.253.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.133.245.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.17.106.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.243.1.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.243.4.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.243.6.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 83.147.222.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.209.0.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.209.3.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.81.79.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.81.113.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.81.126.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.81.127.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.214.8.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 103.71.22.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 103.71.23.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 103.82.103.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 103.85.114.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 103.85.115.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.69.61.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 132.243.24.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 132.243.25.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 135.136.176.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 135.136.177.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 135.136.186.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 135.136.187.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 139.28.220.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 139.28.221.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.228.142.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.228.143.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.228.146.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.228.147.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.228.184.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 157.228.185.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.255.32.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.255.33.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.253.16.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.17.2.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.58.207.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.94.167.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.104.250.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.105.118.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.109.21.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.112.83.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.112.100.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.125.228.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.125.230.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.125.231.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.188.181.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.229.65.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.229.66.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.109.84.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.109.85.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.124.180.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.124.181.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.36.177.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.53.54.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.67.200.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.66.87.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 198.105.124.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 198.105.125.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.81.92.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 95.81.117.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.106.95.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.252.116.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.89.64.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.133.246.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 5.180.136.0/24 | Valid | RIR databaseRIPE | 658 98% |
| 5.180.137.0/24 | Valid | RIR databaseRIPE | 658 98% |
| 2a0a:9300:1::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:5d00:1002::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:5d00:2002::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:5d06:2002::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS207569 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 18 are in fix.csv.
- ROA: origin1
- Route object: none3
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 5.101.88.0/24 | ROAs covering it name AS50113, not AS207569. If AS207569 should announce it, add a ROA for AS207569. |
| Route object: none | 5.101.88.0/24 | Route objects for it name AS50113. Add a route object with origin AS207569 in the RIR database for the space. |
| Route object: none | 194.63.140.0/24 | Route objects for it name AS50113. Add a route object with origin AS207569 in the RIR database for the space. |
| Route object: none | 194.63.142.0/24 | Route objects for it name AS50113. Add a route object with origin AS207569 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS207569 whose prefix no peer sees AS207569 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.186.220.0/23 | RIPE | Invalid: origin |
| 104.128.131.0/24 | RIPE | Invalid: origin |
| 157.228.146.0/23 | RIPE | Valid |
| 157.228.184.0/23 | RIPE | Valid |
| 159.255.32.0/23 | RIPE | Valid |
| 185.37.195.0/24 | RIPE | Valid |
| 198.105.124.0/23 | RIPE | Valid |
| 2a0a:9300::/32 | RIPE | No ROA |
| 2a0a:9300:aaaa::/48 | RIPE | Valid |
| 2a0a:9301::/32 | RIPE | No ROA |
| 2a0b:da00::/32 | RIPE | Valid |
| 2a0b:da01::/32 | RIPE | Valid |
| 2a0b:da02::/32 | RIPE | Valid |
| 2a0b:da03::/32 | 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.