bgpreport

Network · data from 2026-11-12

AS45625 LTITL-AS-AP - LTIMINDTREE LIMITED

Registry name: LTITL-AS-AP - LTIMINDTREE LIMITED, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45625, 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.
43.245.20.0/24 Valid RIR databaseAPNIC 673 100% 66
103.146.249.0/24 Valid RIR databaseAPNIC 673 100% 66
103.157.99.0/24 Valid RIR databaseAPNIC 673 100% 67
103.244.152.0/24 Valid RIR databaseAPNIC 673 100% 66
103.244.154.0/24 Valid RIR databaseAPNIC 673 100% 67
103.244.155.0/24 Valid RIR databaseAPNIC 673 100% 66
112.121.48.0/21 Valid RIR databaseAPNIC 673 100% 66
112.121.48.0/24 Valid RIR databaseAPNIC 673 100% 67
112.121.49.0/24 Valid RIR databaseAPNIC 673 100% 67
112.121.50.0/24 Valid RIR databaseAPNIC 673 100% 67
112.121.51.0/24 Valid RIR databaseAPNIC 673 100% 67
112.121.52.0/24 Valid RIR databaseAPNIC 673 100% 67
112.121.53.0/24 Valid RIR databaseAPNIC 673 100% 67
112.121.54.0/24 Valid RIR databaseAPNIC 673 100% 66
112.121.55.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
112.121.58.0/24 Valid RIR databaseAPNIC 673 100% 66
112.121.59.0/24 Valid RIR databaseAPNIC 673 100% 66
112.121.61.0/24 Valid RIR databaseAPNIC 673 100% 67
112.121.62.0/24 Valid RIR databaseAPNIC 673 100% 67
2407:bb00::/36 Valid RIR databaseAPNIC 635 100% 67
43.245.20.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2
43.245.21.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS45625 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 30 are in fix.csv.

  • Route object: not announced30

Route objects not announced

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

103.244.152.0/22APNICValid
103.244.152.0/23APNICValid
103.244.153.0/24APNICValid
103.244.154.0/23APNICValid
112.121.48.0/20APNICNo ROA
112.121.48.0/22APNICValid
112.121.48.0/23APNICValid
112.121.50.0/23APNICValid
112.121.52.0/22APNICValid
112.121.52.0/23APNICValid
112.121.54.0/23APNICValid
112.121.56.0/22APNICNo ROA
112.121.56.0/23APNICNo ROA
112.121.56.0/24APNICValid
112.121.57.0/24APNICValid
112.121.60.0/24APNICValid
112.121.63.0/24APNICValid
202.124.194.0/24APNICValid
2407:bb00::/44APNICInvalid: maxLength
2407:bb00::/48APNICInvalid: maxLength
2407:bb00:1::/48APNICInvalid: maxLength
2407:bb00:2::/48APNICInvalid: maxLength
2407:bb00:5000::/44APNICValid
2407:bb00:5000::/48APNICInvalid: maxLength
2407:bb00:5001::/48APNICInvalid: maxLength
2407:bb00:5002::/48APNICInvalid: maxLength
2407:bb00:5003::/48APNICInvalid: maxLength
2407:bb00:5004::/48APNICInvalid: maxLength
2407:bb00:5005::/48APNICInvalid: maxLength
2407:bb00:5006::/48APNICInvalid: maxLength

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.