bgpreport

Network · data from 2026-11-12

AS198550 NODE HOST

Registry name: nodehost-as NODE HOST LIMITED, GB · PeeringDB

39IPv4 routes 87.2% RPKI valid · 61.5% with a route object
0IPv6 routes
5RPKI invalid 5 origin · 0 maxLength
0No ROA 15 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS198550, seen from no peer

Announced routes

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

87.120.108.0/24 Invalid: origin None 38 6%low visibility 22
45.128.235.0/24 Invalid: origin None 7 1%low visibility 7
87.120.196.0/24 Invalid: origin None 7 1%low visibility 7
94.125.102.0/24 Invalid: origin Other origin only 2 0%low visibility 2
94.125.103.0/24 Invalid: origin None 2 0%low visibility 2
2.26.125.0/24 Valid None 673 100% 67
144.31.28.0/24 Valid None 673 100% 67
191.217.204.0/24 Valid None 673 100% 67
81.90.25.0/24 Valid Other origin only 672 100% 67
2.26.124.0/24 Valid None 671 100% 67
191.217.205.0/24 Valid None 671 100% 67
191.217.206.0/24 Valid None 671 100% 67
81.90.21.0/24 Valid Other origin only 670 100% 67
150.241.87.0/24 Valid None 670 100% 67
81.90.17.0/24 Valid None 669 99% 67
2.27.13.0/24 Valid RIR databaseRIPE 673 100% 67
31.76.241.0/24 Valid RIR databaseRIPE 673 100% 67
87.232.123.0/24 Valid RIR databaseRIPE 673 100% 67
144.31.215.0/24 Valid RIR databaseRIPE 673 100% 67
150.241.68.0/24 Valid RIR databaseRIPE 673 100% 67
191.44.108.0/23 Valid RIR databaseRIPE 673 100% 67
191.44.112.0/24 Valid RIR databaseRIPE 673 100% 67
191.44.114.0/24 Valid RIR databaseRIPE 673 100% 67
2.27.15.0/24 Valid RIR databaseRIPE 672 100% 66
168.222.254.0/24 Valid RIR databaseRIPE 672 100% 67
2.26.254.0/24 Valid RIR databaseRIPE 671 100% 66
2.27.12.0/24 Valid RIR databaseRIPE 671 100% 66
2.27.14.0/24 Valid RIR databaseRIPE 671 100% 67
31.76.120.0/24 Valid RIR databaseRIPE 671 100% 67
31.76.240.0/24 Valid RIR databaseRIPE 671 100% 67
87.232.119.0/24 Valid RIR databaseRIPE 671 100% 68
150.241.65.0/24 Valid RIR databaseRIPE 671 100% 67
150.241.92.0/24 Valid RIR databaseRIPE 671 100% 66
185.23.19.0/24 Valid RIR databaseRIPE 671 100% 66
194.238.57.0/24 Valid RIR databaseRIPE 671 100% 67
2.26.187.0/24 Valid RIR databaseRIPE 669 99% 68
2.26.255.0/24 Valid RIR databaseRIPE 669 99% 68
191.44.113.0/24 Valid RIR databaseRIPE 669 99% 68
201.3.228.0/24 Valid RIR databaseRIPE 669 99% 68

AS-SET

AS198550's PeeringDB record names no 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 22 are in fix.csv.

  • ROA: origin5
  • Route object: none15
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin87.120.108.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS198550 should announce it, add a ROA for AS198550.38 of 673
Route object: none87.120.108.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.38 of 673
ROA: origin45.128.235.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS198550 should announce it, add a ROA for AS198550.7 of 673
Route object: none45.128.235.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.7 of 673
ROA: origin87.120.196.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS198550 should announce it, add a ROA for AS198550.7 of 673
Route object: none87.120.196.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.7 of 673
ROA: origin94.125.102.0/24ROAs covering it name AS209630, not AS198550. If AS198550 should announce it, add a ROA for AS198550.2 of 673
Route object: none94.125.102.0/24Route objects for it name AS209630. Add a route object with origin AS198550 in the RIR database for the space.2 of 673
ROA: origin94.125.103.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS198550 should announce it, add a ROA for AS198550.2 of 673
Route object: none94.125.103.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.2 of 673
Route object: none2.26.125.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.673 of 673
Route object: none144.31.28.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.673 of 673
Route object: none191.217.204.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.673 of 673
Route object: none81.90.25.0/24Route objects for it name AS208185. Add a route object with origin AS198550 in the RIR database for the space.672 of 673
Route object: none2.26.124.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.671 of 673
Route object: none191.217.205.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.671 of 673
Route object: none191.217.206.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.671 of 673
Route object: none81.90.21.0/24Route objects for it name AS48407. Add a route object with origin AS198550 in the RIR database for the space.670 of 673
Route object: none150.241.87.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.670 of 673
Route object: none81.90.17.0/24No route object for it. Add a route object with origin AS198550 in the RIR database for the space.669 of 673

Route objects not announced

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

191.217.207.0/24RIPEValid
2a10:ab80:3e2::/48RIPEValid

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.