bgpreport

Network · data from 2026-11-12

AS11031 ORBIS-INVESTMENTS - Orbis Investments (Canada) Limited

Registry name: ORBIS-INVESTMENTS - Orbis Investments (Canada) Limited, CA · not in PeeringDB

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

Announced routes

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

162.219.233.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
162.219.234.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
185.108.14.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.58.182.0/23 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
162.219.235.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
162.219.236.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
162.219.237.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
162.219.238.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
185.108.12.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.61.42.0/23 No ROA Other IRR onlyRADB 669 99% 67
162.219.232.0/24 No ROA Other IRR onlyNTTCOM, RADB 669 99% 67

AS-SET

AS11031 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: none11
  • Route object: RIR11
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none162.219.233.0/24No ROA covers it. Add a ROA for AS11031, maxLength 24.672 of 673
Route object: RIR162.219.233.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none162.219.234.0/24No ROA covers it. Add a ROA for AS11031, maxLength 24.672 of 673
Route object: RIR162.219.234.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none185.108.14.0/24No ROA covers it. Add a ROA for AS11031, maxLength 24.672 of 673
Route object: RIR185.108.14.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.58.182.0/23No ROA covers it. Add a ROA for AS11031, maxLength 23.671 of 673
Route object: RIR103.58.182.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none162.219.235.0/24No ROA covers it. Add a ROA for AS11031, maxLength 24.671 of 673
Route object: RIR162.219.235.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none162.219.236.0/24No ROA covers it. Add a ROA for AS11031, maxLength 24.671 of 673
Route object: RIR162.219.236.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none162.219.237.0/24No ROA covers it. Add a ROA for AS11031, maxLength 24.671 of 673
Route object: RIR162.219.237.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none162.219.238.0/24No ROA covers it. Add a ROA for AS11031, maxLength 24.671 of 673
Route object: RIR162.219.238.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none185.108.12.0/24No ROA covers it. Add a ROA for AS11031, maxLength 24.671 of 673
Route object: RIR185.108.12.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.61.42.0/23No ROA covers it. Add a ROA for AS11031, maxLength 23.669 of 673
Route object: RIR103.61.42.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none162.219.232.0/24No ROA covers it. Add a ROA for AS11031, maxLength 24.669 of 673
Route object: RIR162.219.232.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

103.58.182.0/24NTTCOM, RADBNo ROA
103.58.183.0/24NTTCOM, RADBNo ROA
103.61.42.0/24RADBNo ROA
103.61.43.0/24RADBNo ROA
162.219.232.0/21NTTCOM, RADBNo ROA
162.219.232.0/22NTTCOM, RADBNo ROA
162.219.232.0/23NTTCOM, RADBNo ROA
162.219.234.0/23NTTCOM, RADBNo ROA
162.219.236.0/22NTTCOM, RADBNo ROA
162.219.236.0/23NTTCOM, RADBNo ROA
162.219.238.0/23NTTCOM, RADBNo ROA
162.219.239.0/24NTTCOM, RADBNo ROA
185.108.12.0/22RADBNo ROA
185.108.13.0/24RADBNo ROA
185.108.15.0/24RADBNo 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.