bgpreport

Network · data from 2026-11-12

AS205220 RHC-Hosting RH & Co. IT Services Ltd

Registry name: RHC-Hosting RH & Co. IT Services Ltd, GB · not in PeeringDB

13IPv4 routes 92.3% RPKI valid · 76.9% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 3 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
32Route objects not announced registered with origin AS205220, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS205220, 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.

192.129.70.0/24 No ROA Other origin only 5 1%low visibility 4
173.247.238.0/24 Valid Nonecovered by 173.247.238.0/23 667 99% 67
173.247.239.0/24 Valid Nonecovered by 173.247.238.0/23 2 0%low visibility 1
194.180.37.0/24 Valid Other IRR onlyRADB 667 99% 67
5.10.219.0/24 Valid RIR databaseRIPE 667 99% 67
23.26.86.0/24 Valid RIR databaseARIN, RADB 667 99% 67
23.131.32.0/24 Valid RIR databaseARIN 667 99% 67
94.176.215.0/24 Valid RIR databaseRIPE 667 99% 67
104.164.61.0/24 Valid RIR databaseARIN 667 99% 67
166.0.118.0/24 Valid RIR databaseARIN 667 99% 67
188.209.136.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
216.107.130.0/24 Valid RIR databaseARIN, RADB 667 99% 67
45.38.153.0/24 Valid RIR databaseARIN 666 99% 67

AS-SET

AS205220 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 37 are in fix.csv.

  • ROA: none1
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none192.129.70.0/24No ROA covers it. Add a ROA for AS205220, maxLength 24.5 of 673
Route object: none192.129.70.0/24Route objects for it name AS834, AS55036. Add a route object with origin AS205220 in the RIR database for the space.5 of 673
Route object: none173.247.238.0/24No route object for it. A route object for 173.247.238.0/23 with origin AS205220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205220 in the RIR database for the space.667 of 673
Route object: none173.247.239.0/24No route object for it. A route object for 173.247.238.0/23 with origin AS205220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205220 in the RIR database for the space.2 of 673
Route object: RIR194.180.37.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

Route objects with origin AS205220 whose prefix no peer sees AS205220 announce. Many are kept on purpose (backup routes, space announced only in some places).

13.143.207.0/24RIPEValid
86.38.182.0/23RIPENo ROA
89.116.130.0/23RIPENo ROA
89.116.148.0/23RIPEValid
89.117.24.0/23RIPEValid
89.117.70.0/23RIPEValid
89.117.226.0/23RIPENo ROA
96.126.65.0/24RADBNo ROA
102.135.52.0/24AFRINICNo ROA
116.90.115.0/24APNICValid
142.249.79.0/24ARINValid
153.52.84.0/24RIPEValid
160.19.95.0/24RIPEValid
163.5.71.0/24RIPEValid
173.247.238.0/23ARIN, RADBValid
181.215.74.0/23RIPENo ROA
181.215.76.0/23RIPENo ROA
185.115.163.0/24RIPEValid
192.5.56.0/24RADBNo ROA
192.34.90.0/24RADBNo ROA
192.42.146.0/24ALTDBNo ROA
192.73.17.0/24ALTDBNo ROA
198.41.4.0/24RADBNo ROA
198.96.160.0/24ALTDBNo ROA
198.160.213.0/24RADBNo ROA
199.5.21.0/24RADBNo ROA
205.142.36.0/24ALTDBNo ROA
205.172.142.0/24ALTDBNo ROA
206.220.75.0/24ALTDBNo ROA
209.126.88.0/24RADBNo ROA
209.126.89.0/24ARINValid
2a0a:c640::/29RIPEValid

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.