Network · data from 2026-11-12

AS37622 Mahanagar Telephone (Mauritius)

Registry name: Mahanagar Telephone (Mauritius) Ltd - Mahanagar Telephone (Mauritius) Ltd, MU · PeeringDB

7IPv4 routes 100.0% RPKI valid · 85.7% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

1Route objects not announced registered with origin AS37622, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS37622, 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.131.48.0/21	Valid	None	672 100%	67
41.223.76.0/23	Valid	Other IRR onlyRIPE-NONAUTH	671 100%	68
41.223.78.0/24	Valid	Other IRR onlyRIPE-NONAUTH	671 100%	68
41.223.79.0/24	Valid	Other IRR onlyRIPE-NONAUTH	671 100%	68
154.65.8.0/22	Valid	Other IRR onlyRIPE-NONAUTH	671 100%	68
41.222.96.0/22	Valid	RIR databaseAFRINIC	671 100%	68
41.222.100.0/22	Valid	RIR databaseAFRINIC	671 100%	68

AS-SET

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

Route object: none1
Route object: RIR4
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: none	102.131.48.0/21	No route object for it. Add a route object with origin AS37622 in the RIR database for the space.	672 of 673
Route object: RIR	41.223.76.0/23	Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.	671 of 673
Route object: RIR	41.223.78.0/24	Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.	671 of 673
Route object: RIR	41.223.79.0/24	Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.	671 of 673
Route object: RIR	154.65.8.0/22	Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

102.131.48.0/21

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

672 of 673

Route object: RIR

41.223.76.0/23

Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.

671 of 673

Route object: RIR

41.223.78.0/24

Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.

671 of 673

Route object: RIR

41.223.79.0/24

Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.

671 of 673

Route object: RIR

154.65.8.0/22

Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.

671 of 673

Route objects not announced

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


41.222.96.0/21	RIPE-NONAUTH	Valid

41.222.96.0/21

RIPE-NONAUTH

Valid

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.