bgpreport

Network · data from 2026-11-12

AS37672 INQ DIGITAL CAMEROON SA

Registry name: INQ DIGITAL CAMEROON SA - INQ DIGITAL CAMEROON SA, CM · PeeringDB

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

Announced routes

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

102.208.81.0/24 Invalid: origin Other origin only 50 7%low visibility 27
217.14.84.0/24 No ROA Other origin only 669 99% 67
41.216.232.0/24 No ROA Other IRR onlyRADB 670 100% 67
41.216.233.0/24 No ROA Other IRR onlyRADB 669 99% 68
41.216.234.0/24 No ROA Other IRR onlyRADB 669 99% 68
41.216.235.0/24 No ROA Other IRR onlyRADB 669 99% 68

AS-SET

AS37672'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: origin1
  • ROA: none5
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin102.208.81.0/24ROAs covering it name AS329469, not AS37672. If AS37672 should announce it, add a ROA for AS37672.50 of 673
Route object: none102.208.81.0/24Route objects for it name AS329469. Add a route object with origin AS37672 in the RIR database for the space.50 of 673
ROA: none217.14.84.0/24No ROA covers it. Add a ROA for AS37672, maxLength 24.669 of 673
Route object: none217.14.84.0/24Route objects for it name AS16284, AS36994. Add a route object with origin AS37672 in the RIR database for the space.669 of 673
ROA: none41.216.232.0/24No ROA covers it. Add a ROA for AS37672, maxLength 24.670 of 673
Route object: RIR41.216.232.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none41.216.233.0/24No ROA covers it. Add a ROA for AS37672, maxLength 24.669 of 673
Route object: RIR41.216.233.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none41.216.234.0/24No ROA covers it. Add a ROA for AS37672, maxLength 24.669 of 673
Route object: RIR41.216.234.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none41.216.235.0/24No ROA covers it. Add a ROA for AS37672, maxLength 24.669 of 673
Route object: RIR41.216.235.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

41.216.232.0/22RADBNo 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.