Network · data from 2026-11-12

AS17825 MAHINDRABT-AS-AP - Tech Mahindra Ltd. Software Development Organisation India

Registry name: MAHINDRABT-AS-AP - Tech Mahindra Ltd. Software Development Organisation India, IN · not in PeeringDB

10IPv4 routes 0.0% RPKI valid · 60.0% with a route object

1IPv6 routes 0.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

11No ROA 4 with no route object for this origin

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

18Route objects not announced registered with origin AS17825, seen from no peer

Announced routes

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


202.67.4.0/24	No ROA	Nonecovered by 202.67.4.0/22	673 100%	67
202.67.5.0/24	No ROA	Nonecovered by 202.67.4.0/22	673 100%	67
203.143.186.0/24	No ROA	Nonecovered by 203.143.186.0/23	672 100%	67
203.143.187.0/24	No ROA	Nonecovered by 203.143.186.0/23	672 100%	67
202.41.204.0/24	No ROA	RIR databaseAPNIC	673 100%	67
202.67.7.0/24	No ROA	RIR databaseAPNIC, REACH	673 100%	67
203.143.176.0/24	No ROA	RIR databaseAPNIC, NTTCOM	673 100%	66
203.143.184.0/23	No ROA	RIR databaseAPNIC	672 100%	67
203.143.178.0/24	No ROA	RIR databaseAPNIC	671 100%	67
203.143.188.0/24	No ROA	RIR databaseAPNIC	671 100%	66
2400:6300::/48	No ROA	RIR databaseAPNIC	635 100%	67

AS-SET

AS17825 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 33 are in fix.csv.

ROA: none11
Route object: none4
Route object: not announced18

Change	Prefix or set	Detail	Full-table peers
ROA: none	202.67.4.0/24	No ROA covers it. Add a ROA for AS17825, maxLength 24.	673 of 673
Route object: none	202.67.4.0/24	No route object for it. A route object for 202.67.4.0/22 with origin AS17825 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17825 in the RIR database for the space.	673 of 673
ROA: none	202.67.5.0/24	No ROA covers it. Add a ROA for AS17825, maxLength 24.	673 of 673
Route object: none	202.67.5.0/24	No route object for it. A route object for 202.67.4.0/22 with origin AS17825 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17825 in the RIR database for the space.	673 of 673
ROA: none	203.143.186.0/24	No ROA covers it. Add a ROA for AS17825, maxLength 24.	672 of 673
Route object: none	203.143.186.0/24	No route object for it. A route object for 203.143.186.0/23 with origin AS17825 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17825 in the RIR database for the space.	672 of 673
ROA: none	203.143.187.0/24	No ROA covers it. Add a ROA for AS17825, maxLength 24.	672 of 673
Route object: none	203.143.187.0/24	No route object for it. A route object for 203.143.186.0/23 with origin AS17825 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17825 in the RIR database for the space.	672 of 673
ROA: none	202.41.204.0/24	No ROA covers it. Add a ROA for AS17825, maxLength 24.	673 of 673
ROA: none	202.67.7.0/24	No ROA covers it. Add a ROA for AS17825, maxLength 24.	673 of 673
ROA: none	203.143.176.0/24	No ROA covers it. Add a ROA for AS17825, maxLength 24.	673 of 673
ROA: none	203.143.184.0/23	No ROA covers it. Add a ROA for AS17825, maxLength 23.	672 of 673
ROA: none	203.143.178.0/24	No ROA covers it. Add a ROA for AS17825, maxLength 24.	671 of 673
ROA: none	203.143.188.0/24	No ROA covers it. Add a ROA for AS17825, maxLength 24.	671 of 673
ROA: none	2400:6300::/48	No ROA covers it. Add a ROA for AS17825, maxLength 48.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

202.67.4.0/24

No ROA covers it. Add a ROA for AS17825, maxLength 24.

673 of 673

Route object: none

202.67.4.0/24

No route object for it. A route object for 202.67.4.0/22 with origin AS17825 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17825 in the RIR database for the space.

673 of 673

ROA: none

202.67.5.0/24

No ROA covers it. Add a ROA for AS17825, maxLength 24.

673 of 673

Route object: none

202.67.5.0/24

673 of 673

ROA: none

203.143.186.0/24

No ROA covers it. Add a ROA for AS17825, maxLength 24.

672 of 673

Route object: none

203.143.186.0/24

No route object for it. A route object for 203.143.186.0/23 with origin AS17825 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17825 in the RIR database for the space.

672 of 673

ROA: none

203.143.187.0/24

No ROA covers it. Add a ROA for AS17825, maxLength 24.

672 of 673

Route object: none

203.143.187.0/24

672 of 673

ROA: none

202.41.204.0/24

No ROA covers it. Add a ROA for AS17825, maxLength 24.

673 of 673

ROA: none

202.67.7.0/24

No ROA covers it. Add a ROA for AS17825, maxLength 24.

673 of 673

ROA: none

203.143.176.0/24

No ROA covers it. Add a ROA for AS17825, maxLength 24.

673 of 673

ROA: none

203.143.184.0/23

No ROA covers it. Add a ROA for AS17825, maxLength 23.

672 of 673

ROA: none

203.143.178.0/24

No ROA covers it. Add a ROA for AS17825, maxLength 24.

671 of 673

ROA: none

203.143.188.0/24

No ROA covers it. Add a ROA for AS17825, maxLength 24.

671 of 673

ROA: none

2400:6300::/48

No ROA covers it. Add a ROA for AS17825, maxLength 48.

635 of 636

Route objects not announced

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


202.52.2.0/23	APNIC	No ROA
202.52.2.0/24	RADB	No ROA
202.67.4.0/22	APNIC	No ROA
202.67.6.0/24	APNIC	No ROA
202.162.188.0/24	APNIC	Invalid: origin
203.143.176.0/20	APNIC	No ROA
203.143.177.0/24	APNIC	No ROA
203.143.179.0/24	APNIC	No ROA
203.143.180.0/24	APNIC	No ROA
203.143.181.0/24	APNIC	No ROA
203.143.182.0/24	APNIC	No ROA
203.143.183.0/24	APNIC	No ROA
203.143.186.0/23	APNIC	No ROA
203.143.189.0/24	APNIC	No ROA
203.143.190.0/24	APNIC	No ROA
203.143.191.0/24	APNIC	No ROA
2400:6300::/64	APNIC	No ROA
2400:6300:0:1::/64	APNIC	No ROA

202.52.2.0/23

APNIC

No ROA

202.52.2.0/24

RADB

No ROA

202.67.4.0/22

APNIC

No ROA

202.67.6.0/24

APNIC

No ROA

202.162.188.0/24

APNIC

Invalid: origin

203.143.176.0/20

APNIC

No ROA

203.143.177.0/24

APNIC

No ROA

203.143.179.0/24

APNIC

No ROA

203.143.180.0/24

APNIC

No ROA

203.143.181.0/24

APNIC

No ROA

203.143.182.0/24

APNIC

No ROA

203.143.183.0/24

APNIC

No ROA

203.143.186.0/23

APNIC

No ROA

203.143.189.0/24

APNIC

No ROA

203.143.190.0/24

APNIC

No ROA

203.143.191.0/24

APNIC

No ROA

2400:6300::/64

APNIC

No ROA

2400:6300:0:1::/64

APNIC

No 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.