bgpreport

Network · data from 2026-11-12

AS55740 Tata Indicom

Registry name: TTSLMEIS-AS-AP - TTSL-ISP DIVISION, IN · PeeringDB

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

Announced routes

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

49.249.1.0/24 Valid RIR databaseAPNIC 673 100% 66
49.249.27.0/24 Valid RIR databaseAPNIC 673 100% 66
14.97.20.0/24 Valid RIR databaseAPNIC 672 100% 66
14.97.48.0/24 Valid RIR databaseAPNIC 672 100% 66
27.107.200.0/24 Valid RIR databaseAPNIC 672 100% 66
14.195.124.0/24 Valid RIR databaseAPNIC 671 100% 66
27.107.201.0/24 Valid RIR databaseAPNIC 671 100% 66
27.107.202.0/24 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS55740'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 54 are in fix.csv.

  • Route object: not announced54

Route objects not announced

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

14.96.16.0/20APNICNo ROA
14.96.32.0/20APNICNo ROA
14.96.48.0/20APNICNo ROA
14.96.64.0/20APNICInvalid: origin
14.96.80.0/20APNICInvalid: origin
14.96.96.0/20APNICInvalid: origin
14.96.112.0/20APNICInvalid: origin
14.96.128.0/20APNICNo ROA
14.96.144.0/20APNICNo ROA
14.96.160.0/20APNICNo ROA
14.96.176.0/20APNICNo ROA
14.96.183.0/24APNICValid
14.96.192.0/20APNICNo ROA
14.96.208.0/20APNICNo ROA
14.96.224.0/20APNICNo ROA
14.96.240.0/20APNICNo ROA
14.96.240.0/21APNICInvalid: origin
14.97.0.0/20APNICNo ROA
14.97.16.0/20APNICNo ROA
14.97.32.0/20APNICNo ROA
14.97.48.0/20APNICNo ROA
14.97.64.0/20APNICNo ROA
14.97.80.0/20APNICNo ROA
14.97.96.0/20APNICNo ROA
14.97.112.0/20APNICNo ROA
14.97.128.0/20APNICNo ROA
14.97.144.0/20APNICNo ROA
14.97.160.0/20APNICNo ROA
14.97.176.0/20APNICNo ROA
14.97.192.0/20APNICNo ROA
14.97.208.0/20APNICNo ROA
14.97.224.0/20APNICNo ROA
14.97.240.0/20APNICNo ROA
14.99.32.0/20APNICInvalid: origin
14.99.48.0/20APNICNo ROA
14.99.64.0/20APNICNo ROA
14.99.80.0/20APNICNo ROA
14.99.96.0/20APNICInvalid: origin
14.99.192.0/20APNICNo ROA
14.99.208.0/20APNICNo ROA
14.99.224.0/20APNICNo ROA
14.99.240.0/20APNICNo ROA
14.195.78.0/24APNICValid
14.195.79.0/24APNICValid
14.195.91.0/24APNICValid
103.1.124.0/22APNICNo ROA
103.1.124.0/24APNICNo ROA
2406:e00::/32APNICNo ROA
2406:e00::/35APNICNo ROA
2406:e00:100::/47APNICNo ROA
2406:e00:104::/47APNICNo ROA
2406:e00:10e::/48APNICNo ROA
2406:e00:10f::/48APNICNo ROA
2406:e00:800::/48APNICValid

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.