Network · data from 2026-11-12

AS17652 Mauritius Telecom Ltd - Mauritius Telecom Ltd

Registry name: Mauritius Telecom Ltd - Mauritius Telecom Ltd, MU · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 0.0% with a route object

0IPv6 routes

3RPKI invalid 3 origin · 0 maxLength

0No ROA 3 with no route object for this origin

3Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS17652, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17652, 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.136.197.0/24	Invalid: origin	None	3 0%low visibility	3
196.20.164.0/22	Invalid: origin	Other origin only	3 0%low visibility	3
197.225.174.0/23	Invalid: origin	None	3 0%low visibility	3

41.136.197.0/24

Invalid: origin

None

3 0%low visibility

196.20.164.0/22

Invalid: origin

Other origin only

3 0%low visibility

197.225.174.0/23

Invalid: origin

None

3 0%low visibility

AS-SET

AS17652 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 6 are in fix.csv.

ROA: origin3
Route object: none3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	41.136.197.0/24	ROAs covering it name AS4755, AS6453, AS23889, not AS17652. If AS17652 should announce it, add a ROA for AS17652.	3 of 673
Route object: none	41.136.197.0/24	No route object for it. Add a route object with origin AS17652 in the RIR database for the space.	3 of 673
ROA: origin	196.20.164.0/22	ROAs covering it name AS4755, AS6453, AS23889, not AS17652. If AS17652 should announce it, add a ROA for AS17652.	3 of 673
Route object: none	196.20.164.0/22	Route objects for it name AS23889. Add a route object with origin AS17652 in the RIR database for the space.	3 of 673
ROA: origin	197.225.174.0/23	ROAs covering it name AS4755, AS6453, AS23889, not AS17652. If AS17652 should announce it, add a ROA for AS17652.	3 of 673
Route object: none	197.225.174.0/23	No route object for it. Add a route object with origin AS17652 in the RIR database for the space.	3 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

41.136.197.0/24

ROAs covering it name AS4755, AS6453, AS23889, not AS17652. If AS17652 should announce it, add a ROA for AS17652.

3 of 673

Route object: none

41.136.197.0/24

No route object for it. Add a route object with origin AS17652 in the RIR database for the space.

3 of 673

ROA: origin

196.20.164.0/22

ROAs covering it name AS4755, AS6453, AS23889, not AS17652. If AS17652 should announce it, add a ROA for AS17652.

3 of 673

Route object: none

196.20.164.0/22

Route objects for it name AS23889. Add a route object with origin AS17652 in the RIR database for the space.

3 of 673

ROA: origin

197.225.174.0/23

ROAs covering it name AS4755, AS6453, AS23889, not AS17652. If AS17652 should announce it, add a ROA for AS17652.

3 of 673

Route object: none

197.225.174.0/23

No route object for it. Add a route object with origin AS17652 in the RIR database for the space.

3 of 673

Route objects not announced

Every route object with origin AS17652 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.