Network · data from 2026-11-12

AS132931 Ficus Telecom Pvt Ltd..

Registry name: FICUSTELECOM-AS - FICUS TELECOM PRIVATE LIMITED, IN · PeeringDB

13IPv4 routes 92.3% RPKI valid · 92.3% with a route object

9IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 1 with no route object for this origin

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

11Route objects not announced registered with origin AS132931, seen from no peer

Announced routes

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


103.59.187.0/24	No ROA	Nonecovered by 103.59.184.0/22	673 100%	66
103.52.52.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.52.53.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.52.54.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.52.55.0/24	Valid	RIR databaseAPNIC	673 100%	66
45.65.36.0/24	Valid	RIR databaseAPNIC	672 100%	66
45.65.37.0/24	Valid	RIR databaseAPNIC	672 100%	66
45.65.38.0/24	Valid	RIR databaseAPNIC	672 100%	66
45.65.39.0/24	Valid	RIR databaseAPNIC	672 100%	66
45.119.128.0/24	Valid	RIR databaseAPNIC	672 100%	66
45.119.129.0/24	Valid	RIR databaseAPNIC	672 100%	66
45.119.130.0/24	Valid	RIR databaseAPNIC	672 100%	66
45.119.131.0/24	Valid	RIR databaseAPNIC	672 100%	66
2403:7b40:1::/48	Valid	RIR databaseAPNIC	32 5%low visibility	26
2403:7b40:2::/48	Valid	RIR databaseAPNIC	32 5%low visibility	26
2403:7b40:3::/48	Valid	RIR databaseAPNIC	32 5%low visibility	26
2403:7b40:4::/48	Valid	RIR databaseAPNIC	32 5%low visibility	26
2403:7b40:5::/48	Valid	RIR databaseAPNIC	32 5%low visibility	26
2403:7b40:6::/48	Valid	RIR databaseAPNIC	32 5%low visibility	26
2403:7b40:7::/48	Valid	RIR databaseAPNIC	32 5%low visibility	26
2403:7b40:8::/48	Valid	RIR databaseAPNIC	32 5%low visibility	26
2403:7b40:9::/48	Valid	RIR databaseAPNIC	32 5%low visibility	26

103.59.187.0/24

No ROA

Nonecovered by 103.59.184.0/22

673 100%

103.52.52.0/24

Valid

RIR databaseAPNIC

673 100%

103.52.53.0/24

Valid

RIR databaseAPNIC

673 100%

103.52.54.0/24

Valid

RIR databaseAPNIC

673 100%

103.52.55.0/24

Valid

RIR databaseAPNIC

673 100%

45.65.36.0/24

Valid

RIR databaseAPNIC

672 100%

45.65.37.0/24

Valid

RIR databaseAPNIC

672 100%

45.65.38.0/24

Valid

RIR databaseAPNIC

672 100%

45.65.39.0/24

Valid

RIR databaseAPNIC

672 100%

45.119.128.0/24

Valid

RIR databaseAPNIC

672 100%

45.119.129.0/24

Valid

RIR databaseAPNIC

672 100%

45.119.130.0/24

Valid

RIR databaseAPNIC

672 100%

45.119.131.0/24

Valid

RIR databaseAPNIC

672 100%

2403:7b40:1::/48

Valid

RIR databaseAPNIC

32 5%low visibility

2403:7b40:2::/48

Valid

RIR databaseAPNIC

32 5%low visibility

2403:7b40:3::/48

Valid

RIR databaseAPNIC

32 5%low visibility

2403:7b40:4::/48

Valid

RIR databaseAPNIC

32 5%low visibility

2403:7b40:5::/48

Valid

RIR databaseAPNIC

32 5%low visibility

2403:7b40:6::/48

Valid

RIR databaseAPNIC

32 5%low visibility

2403:7b40:7::/48

Valid

RIR databaseAPNIC

32 5%low visibility

2403:7b40:8::/48

Valid

RIR databaseAPNIC

32 5%low visibility

2403:7b40:9::/48

Valid

RIR databaseAPNIC

32 5%low visibility

AS-SET

AS132931'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: none1
Route object: none1
Route object: not announced11

Change	Prefix or set	Detail	Full-table peers
ROA: none	103.59.187.0/24	No ROA covers it. Add a ROA for AS132931, maxLength 24.	673 of 673
Route object: none	103.59.187.0/24	No route object for it. A route object for 103.59.184.0/22 with origin AS132931 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132931 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

103.59.187.0/24

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

673 of 673

Route object: none

103.59.187.0/24

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

673 of 673

Route objects not announced

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


45.65.36.0/22	APNIC	Valid
45.65.36.0/23	APNIC	Valid
45.65.38.0/23	APNIC	Valid
45.119.128.0/22	APNIC	Valid
45.119.128.0/23	APNIC	Valid
45.119.130.0/23	APNIC	Valid
103.52.52.0/22	APNIC	Valid
103.52.52.0/23	APNIC	Valid
103.52.54.0/23	APNIC	Valid
103.59.184.0/22	APNIC	No ROA
103.59.185.0/24	APNIC	Valid

45.65.36.0/22

APNIC

Valid

45.65.36.0/23

APNIC

Valid

45.65.38.0/23

APNIC

Valid

45.119.128.0/22

APNIC

Valid

45.119.128.0/23

APNIC

Valid

45.119.130.0/23

APNIC

Valid

103.52.52.0/22

APNIC

Valid

103.52.52.0/23

APNIC

Valid

103.52.54.0/23

APNIC

Valid

103.59.184.0/22

APNIC

No ROA

103.59.185.0/24

APNIC

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.