bgpreport

Network · data from 2026-11-12

AS132761 Smartlink Solutions

Registry name: Smartlink-AS-IN - Smartlink Solutions Pvt. Ltd., IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132761, 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.
2402:dc40:100::/40 Invalid: origin None 3 0%low visibility 1
103.249.24.0/24 Valid RIR databaseAPNIC 673 100% 66
103.249.25.0/24 Valid RIR databaseAPNIC 673 100% 66
103.249.26.0/24 Valid RIR databaseAPNIC 673 100% 66
103.249.27.0/24 Valid RIR databaseAPNIC 673 100% 66
43.247.160.0/22 Valid RIR databaseAPNIC 671 100% 67
43.247.160.0/24 Valid RIR databaseAPNIC 671 100% 67
43.247.161.0/24 Valid RIR databaseAPNIC 671 100% 67
43.247.162.0/24 Valid RIR databaseAPNIC 671 100% 67
43.247.163.0/24 Valid RIR databaseAPNIC 671 100% 67
103.249.24.0/22 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS132761'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 10 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin2402:dc40:100::/40ROAs covering it name AS134331, not AS132761. If AS132761 should announce it, add a ROA for AS132761.3 of 636
Route object: none2402:dc40:100::/40No route object for it. Add a route object with origin AS132761 in the RIR database for the space.3 of 636

Route objects not announced

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

43.247.160.0/23APNICValid
43.247.162.0/23APNICValid
103.48.104.0/24APNICInvalid: origin
103.48.105.0/24APNICInvalid: origin
103.48.106.0/24APNICInvalid: origin
103.48.107.0/24APNICInvalid: origin
103.249.24.0/23APNICValid
103.249.26.0/23APNICValid

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.