bgpreport

Network · data from 2026-11-12

AS135709 Lightstorm Telecom Connectivity Private Limited

Registry name: LTCIN-AS-IN - Lightstorm Telecom Connectivity Private Limited, IN · PeeringDB

9IPv4 routes 44.4% RPKI valid · 33.3% with a route object
2IPv6 routes 50.0% RPKI valid · 50.0% with a route object
5RPKI invalid 5 origin · 0 maxLength
1No ROA 7 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS135709, seen from no peer

Announced routes

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

185.1.226.0/23 Invalid: origin None 4 1%low visibility 2
27.111.228.0/22 Invalid: origin None 3 0%low visibility 1
210.87.106.0/24 Invalid: origin Other origin only 2 0%low visibility 1
210.87.107.0/24 Invalid: origin Other origin only 1 0%low visibility 1
2401:5760::/32 Invalid: origin Other origin only 1 0%low visibility 1
223.31.200.0/24 No ROA None 390 58% 63
45.248.40.0/22 Valid Other origin only 673 100% 67
103.159.217.0/24 Valid RIR databaseAPNIC 673 100% 66
103.206.64.0/24 Valid RIR databaseAPNIC 673 100% 66
103.206.66.0/24 Valid RIR databaseAPNIC 673 100% 66
2406:dd40:2000::/35 Valid RIR databaseAPNIC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS135709: AS135709:AS-LTCIN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS135709 isn't in the set, or no route object for AS135709 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS135709 in itNot covered
AS135709:AS-LTCIN APNIClists itself further down5 member sets in no database: AS-149994, AS-DTIIG-139901, AS-FIRSTLINK-DOWN, AS135327:AS-CUSTOMERS, AS55915:AS-CUSTOMERS 2,23048195,511 Yes 7

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

  • ROA: origin5
  • ROA: none1
  • Route object: none7
  • AS-SET: missing member5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin185.1.226.0/23An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS135709 should announce it, add a ROA for AS135709.4 of 673
Route object: none185.1.226.0/23No route object for it. Add a route object with origin AS135709 in the RIR database for the space.4 of 673
ROA: origin27.111.228.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS135709 should announce it, add a ROA for AS135709.3 of 673
Route object: none27.111.228.0/22No route object for it. Add a route object with origin AS135709 in the RIR database for the space.3 of 673
ROA: origin210.87.106.0/24ROAs covering it name AS152144, not AS135709. If AS135709 should announce it, add a ROA for AS135709.2 of 673
Route object: none210.87.106.0/24Route objects for it name AS152144. Add a route object with origin AS135709 in the RIR database for the space.2 of 673
ROA: origin210.87.107.0/24ROAs covering it name AS152144, not AS135709. If AS135709 should announce it, add a ROA for AS135709.1 of 673
Route object: none210.87.107.0/24Route objects for it name AS152144. Add a route object with origin AS135709 in the RIR database for the space.1 of 673
ROA: origin2401:5760::/32ROAs covering it name AS152144, not AS135709. If AS135709 should announce it, add a ROA for AS135709.1 of 636
Route object: none2401:5760::/32Route objects for it name AS152144. Add a route object with origin AS135709 in the RIR database for the space.1 of 636
ROA: none223.31.200.0/24No ROA covers it. Add a ROA for AS135709, maxLength 24.390 of 673
Route object: none223.31.200.0/24No route object for it. Add a route object with origin AS135709 in the RIR database for the space.390 of 673
Route object: none45.248.40.0/22Route objects for it name AS134884. Add a route object with origin AS135709 in the RIR database for the space.673 of 673
AS-SET: missing memberAS135709:AS-LTCINAS135709:AS-LTCIN (APNIC) lists AS-149994; no IRR database read has it.
AS-SET: missing memberAS135709:AS-LTCINAS135709:AS-LTCIN (APNIC) lists AS-DTIIG-139901; no IRR database read has it.
AS-SET: missing memberAS135709:AS-LTCINAS135709:AS-LTCIN (APNIC) lists AS-FIRSTLINK-DOWN; no IRR database read has it.
AS-SET: missing memberAS135709:AS-LTCINAS135709:AS-LTCIN (APNIC) lists AS135327:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberAS135709:AS-LTCINAS135709:AS-LTCIN (APNIC) lists AS55915:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

103.206.64.0/22APNICValid
103.206.64.0/23APNICValid
103.206.65.0/24APNICValid
103.206.66.0/23APNICValid
103.206.67.0/24APNICValid

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.