bgpreport

Network · data from 2026-11-12

AS41362 BGNET Royal London Management Services Limited

Registry name: BGNET Royal London Management Services Limited, GB · not in PeeringDB

13IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
13No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
24Route objects not announced registered with origin AS41362, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41362, 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.
194.35.20.0/23 No ROA Other IRR onlyRADB 672 100% 66
194.35.20.0/24 No ROA RIR databaseRADB, RIPE 673 100% 66
194.35.21.0/24 No ROA RIR databaseRADB, RIPE 673 100% 66
89.250.32.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
89.250.33.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
89.250.34.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
89.250.36.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
89.250.39.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
89.250.40.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
89.250.42.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
89.250.44.0/24 No ROA RIR databaseRIPE 672 100% 67
89.250.45.0/24 No ROA RIR databaseRIPE 672 100% 67
89.250.46.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67

AS-SET

AS41362 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 38 are in fix.csv.

  • ROA: none13
  • Route object: RIR1
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
ROA: none194.35.20.0/23No ROA covers it. Add a ROA for AS41362, maxLength 23.672 of 673
Route object: RIR194.35.20.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none194.35.20.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.673 of 673
ROA: none194.35.21.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.673 of 673
ROA: none89.250.32.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.672 of 673
ROA: none89.250.33.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.672 of 673
ROA: none89.250.34.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.672 of 673
ROA: none89.250.36.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.672 of 673
ROA: none89.250.39.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.672 of 673
ROA: none89.250.40.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.672 of 673
ROA: none89.250.42.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.672 of 673
ROA: none89.250.44.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.672 of 673
ROA: none89.250.45.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.672 of 673
ROA: none89.250.46.0/24No ROA covers it. Add a ROA for AS41362, maxLength 24.672 of 673

Route objects not announced

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

89.250.32.0/20RIPENo ROA
89.250.32.0/22RIPENo ROA
89.250.34.0/23RIPENo ROA
89.250.36.0/23RIPENo ROA
89.250.37.0/24RADBNo ROA
89.250.38.0/23RIPENo ROA
89.250.42.0/23RIPENo ROA
89.250.44.0/22RIPENo ROA
89.250.44.0/23RADBNo ROA
89.250.47.0/24RIPENo ROA
194.35.16.0/24RIPENo ROA
194.35.17.0/24RADB, RIPENo ROA
194.35.18.0/24RIPENo ROA
194.35.19.0/24RIPENo ROA
194.35.22.0/24RIPENo ROA
194.35.23.0/24RIPENo ROA
194.35.24.0/24RIPENo ROA
194.35.25.0/24RIPENo ROA
194.35.26.0/24RIPENo ROA
194.35.27.0/24RIPENo ROA
194.35.28.0/24RIPENo ROA
194.35.29.0/24RIPENo ROA
194.35.30.0/24RIPENo ROA
194.35.31.0/24RADB, RIPENo ROA

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.