bgpreport

Network · data from 2026-11-12

AS29918 IMPERIAL

Registry name: Imperial IT , a division of Imperial Group Ltd - Imperial IT , a division of Imperial Group Ltd, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29918, 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.
41.203.160.0/20 No ROA Other IRR onlyNTTCOM 672 100% 66
196.46.136.0/21 No ROA Other IRR onlyNTTCOM 672 100% 66
197.211.64.0/19 No ROA Other IRR onlyNTTCOM 672 100% 66

AS-SET

AS29918'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 26 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: none41.203.160.0/20No ROA covers it. Add a ROA for AS29918, maxLength 20.672 of 673
Route object: RIR41.203.160.0/20Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none196.46.136.0/21No ROA covers it. Add a ROA for AS29918, maxLength 21.672 of 673
Route object: RIR196.46.136.0/21Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none197.211.64.0/19No ROA covers it. Add a ROA for AS29918, maxLength 19.672 of 673
Route object: RIR197.211.64.0/19Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

41.203.160.0/24AFRINICNo ROA
41.203.161.0/24AFRINICNo ROA
41.203.162.0/24AFRINICNo ROA
41.203.163.0/24AFRINICNo ROA
41.203.164.0/24AFRINICNo ROA
41.203.165.0/24AFRINICNo ROA
41.203.166.0/24AFRINICNo ROA
41.203.167.0/24AFRINICNo ROA
41.203.168.0/24AFRINICNo ROA
41.203.169.0/24AFRINICNo ROA
41.203.170.0/24AFRINICNo ROA
41.203.171.0/24AFRINICNo ROA
41.203.172.0/24AFRINICNo ROA
41.203.173.0/24AFRINICNo ROA
41.203.174.0/24AFRINICNo ROA
196.15.171.0/24RADBNo ROA
196.15.172.0/24RADBNo ROA
196.25.40.0/24RADBNo ROA
196.25.41.0/24RADBNo ROA
196.46.137.0/24AFRINICNo 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.