bgpreport

Network · data from 2026-11-12

AS42235 Internet Solutions Moçambique

Registry name: IDC-AS INTRA DATA COMMUNICATION, MZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42235, 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.
196.40.112.0/21 No ROA Nonecovered by 196.40.112.0/20 12 2%low visibility 8
196.40.124.0/23 No ROA Nonecovered by 196.40.112.0/20 12 2%low visibility 8
41.76.0.0/21 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
41.77.32.0/21 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
196.40.112.0/20 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
197.242.160.0/20 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
2c0f:fb90::/32 No ROA RIR databaseAFRINIC 634 100% 69

AS-SET

AS42235'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 13 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none196.40.112.0/21No ROA covers it. Add a ROA for AS42235, maxLength 21.12 of 673
Route object: none196.40.112.0/21No route object for it. A route object for 196.40.112.0/20 with origin AS42235 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42235 in the RIR database for the space.12 of 673
ROA: none196.40.124.0/23No ROA covers it. Add a ROA for AS42235, maxLength 23.12 of 673
Route object: none196.40.124.0/23No route object for it. A route object for 196.40.112.0/20 with origin AS42235 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42235 in the RIR database for the space.12 of 673
ROA: none41.76.0.0/21No ROA covers it. Add a ROA for AS42235, maxLength 21.672 of 673
Route object: RIR41.76.0.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none41.77.32.0/21No ROA covers it. Add a ROA for AS42235, maxLength 21.672 of 673
Route object: RIR41.77.32.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none196.40.112.0/20No ROA covers it. Add a ROA for AS42235, maxLength 20.672 of 673
Route object: RIR196.40.112.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none197.242.160.0/20No ROA covers it. Add a ROA for AS42235, maxLength 20.672 of 673
Route object: RIR197.242.160.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2c0f:fb90::/32No ROA covers it. Add a ROA for AS42235, maxLength 32.634 of 636

Route objects not announced

Every route object with origin AS42235 is announced.

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.