bgpreport

Network · data from 2026-11-12

AS18196 7 Star Dot Com Pvt. Ltd

Registry name: SEVENSTAR-AS - Seven Star Internet Service Provider, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18196, 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.207.56.0/24 No ROA RIR databaseAPNIC 672 100% 67
103.207.57.0/24 No ROA RIR databaseAPNIC 672 100% 67
103.207.58.0/24 No ROA RIR databaseAPNIC 672 100% 67
103.207.59.0/24 No ROA RIR databaseAPNIC 672 100% 67
210.16.112.0/24 No ROA RIR databaseAPNIC 671 100% 67
210.16.113.0/24 No ROA RIR databaseAPNIC 671 100% 67
210.16.114.0/24 No ROA RIR databaseAPNIC 671 100% 67
210.16.115.0/24 No ROA RIR databaseAPNIC 671 100% 67
103.72.204.0/24 Valid RIR databaseAPNIC 672 100% 67
103.72.205.0/24 Valid RIR databaseAPNIC 672 100% 67
103.72.206.0/24 Valid RIR databaseAPNIC 672 100% 67
103.72.207.0/24 Valid RIR databaseAPNIC 672 100% 67
103.97.249.0/24 Valid RIR databaseAPNIC 672 100% 67
103.115.21.0/24 Valid RIR databaseAPNIC 672 100% 67
103.122.6.0/24 Valid RIR databaseAPNIC 672 100% 67
103.122.12.0/24 Valid RIR databaseAPNIC 672 100% 67
103.123.36.0/24 Valid RIR databaseAPNIC 672 100% 67
103.123.37.0/24 Valid RIR databaseAPNIC 672 100% 67
103.255.113.0/24 Valid RIR databaseAPNIC 672 100% 67
160.202.12.0/24 Valid RIR databaseAPNIC 672 100% 67
160.202.15.0/24 Valid RIR databaseAPNIC 672 100% 67
202.134.154.0/24 Valid RIR databaseAPNIC 672 100% 67
202.134.155.0/24 Valid RIR databaseAPNIC 672 100% 67
202.134.160.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.134.163.0/24 Valid RIR databaseAPNIC 672 100% 67
202.134.164.0/24 Valid RIR databaseAPNIC 672 100% 67
202.134.165.0/24 Valid RIR databaseAPNIC 672 100% 67
202.134.166.0/24 Valid RIR databaseAPNIC 672 100% 67
202.134.169.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.134.172.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.134.184.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.134.185.0/24 Valid RIR databaseAPNIC 672 100% 67
202.134.186.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.134.187.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.134.190.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.134.191.0/24 Valid RIR databaseAPNIC 672 100% 67
103.123.27.0/24 Valid RIR databaseAPNIC 671 100% 67
202.134.189.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
2402:f200::/32 Valid RIR databaseAPNIC 636 100% 70
2001:df5:1700::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3c20::/32 Valid RIR databaseAPNIC 635 100% 67

AS-SET

AS18196'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 48 are in fix.csv.

  • ROA: none8
  • Route object: not announced40
ChangePrefix or setDetailFull-table peers
ROA: none103.207.56.0/24No ROA covers it. Add a ROA for AS18196, maxLength 24.672 of 673
ROA: none103.207.57.0/24No ROA covers it. Add a ROA for AS18196, maxLength 24.672 of 673
ROA: none103.207.58.0/24No ROA covers it. Add a ROA for AS18196, maxLength 24.672 of 673
ROA: none103.207.59.0/24No ROA covers it. Add a ROA for AS18196, maxLength 24.672 of 673
ROA: none210.16.112.0/24No ROA covers it. Add a ROA for AS18196, maxLength 24.671 of 673
ROA: none210.16.113.0/24No ROA covers it. Add a ROA for AS18196, maxLength 24.671 of 673
ROA: none210.16.114.0/24No ROA covers it. Add a ROA for AS18196, maxLength 24.671 of 673
ROA: none210.16.115.0/24No ROA covers it. Add a ROA for AS18196, maxLength 24.671 of 673

Route objects not announced

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

45.117.128.0/22APNICValid
45.117.128.0/24APNICValid
45.117.129.0/24APNICValid
45.117.130.0/24APNICValid
45.117.131.0/24APNICValid
103.72.204.0/22APNICValid
103.122.12.0/23APNICValid
103.122.13.0/24APNICValid
103.123.36.0/23APNICValid
103.171.118.0/24APNICValid
103.207.56.0/22APNICNo ROA
103.255.112.0/22APNICNo ROA
103.255.112.0/24APNICValid
103.255.114.0/24APNICValid
103.255.115.0/24APNICInvalid: origin
160.202.12.0/22APNICValid
160.202.13.0/24APNICValid
160.202.14.0/24APNICValid
202.134.144.0/20APNICNo ROA
202.134.145.0/24APNICInvalid: origin
202.134.147.0/24APNICInvalid: origin
202.134.148.0/24APNICInvalid: origin
202.134.149.0/24APNICInvalid: origin
202.134.150.0/24APNICInvalid: origin
202.134.152.0/24APNICInvalid: origin
202.134.156.0/24APNICValid
202.134.158.0/24APNICInvalid: origin
202.134.159.0/24APNICInvalid: origin
202.134.160.0/19APNICNo ROA
202.134.161.0/24APNIC, RADBValid
202.134.162.0/24APNIC, RADBValid
202.134.167.0/24APNICValid
202.134.170.0/24APNIC, RADBValid
202.134.171.0/24APNIC, RADBValid
202.134.173.0/24APNIC, RADBValid
202.134.174.0/24APNIC, RADBValid
202.134.175.0/24APNIC, RADBValid
210.16.112.0/22APNICNo ROA
2001:df2:700::/48APNICValid
2406:e880::/32APNICValid

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.