bgpreport

Network · data from 2026-11-12

AS134331 Smartlink Solutions India

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS134331, 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:300::/40 Valid Nonecovered by 2402:dc40::/32 39 6%low visibility 29
2402:dc40:700::/40 Valid Nonecovered by 2402:dc40::/32 39 6%low visibility 29
43.254.32.0/23 Valid RIR databaseAPNIC 673 100% 66
43.254.33.0/24 Valid RIR databaseAPNIC 673 100% 67
43.254.35.0/24 Valid RIR databaseAPNIC 673 100% 66
103.79.32.0/24 Valid RIR databaseAPNIC 673 100% 67
103.96.220.0/24 Valid RIR databaseAPNIC 673 100% 66
103.96.221.0/24 Valid RIR databaseAPNIC 673 100% 66
103.96.222.0/24 Valid RIR databaseAPNIC 673 100% 66
103.96.223.0/24 Valid RIR databaseAPNIC 673 100% 66
103.98.109.0/24 Valid RIR databaseAPNIC 673 100% 67
103.98.110.0/24 Valid RIR databaseAPNIC 673 100% 66
103.98.111.0/24 Valid RIR databaseAPNIC 673 100% 67
103.197.132.0/24 Valid RIR databaseAPNIC 673 100% 66
103.197.133.0/24 Valid RIR databaseAPNIC 673 100% 66
103.197.134.0/24 Valid RIR databaseAPNIC 673 100% 66
103.197.135.0/24 Valid RIR databaseAPNIC 673 100% 66
103.243.40.0/24 Valid RIR databaseAPNIC 673 100% 66
220.158.176.0/24 Valid RIR databaseAPNIC 673 100% 67
220.158.177.0/24 Valid RIR databaseAPNIC 673 100% 67
220.158.178.0/24 Valid RIR databaseAPNIC 673 100% 67
220.158.179.0/24 Valid RIR databaseAPNIC 673 100% 67
161.248.65.0/24 Valid RIR databaseAPNIC 672 100% 67
43.254.32.0/22 Valid RIR databaseAPNIC 671 100% 67
43.254.32.0/24 Valid RIR databaseAPNIC 671 100% 67
103.48.104.0/22 Valid RIR databaseAPNIC 671 100% 67
103.79.32.0/22 Valid RIR databaseAPNIC 671 100% 67
103.96.220.0/22 Valid RIR databaseAPNIC 671 100% 67
103.98.108.0/24 Valid RIR databaseAPNIC 671 100% 67
103.197.132.0/22 Valid RIR databaseAPNIC 671 100% 67
103.243.40.0/22 Valid RIR databaseAPNIC 671 100% 67
161.248.64.0/24 Valid RIR databaseAPNIC 671 100% 67
220.158.176.0/22 Valid RIR databaseAPNIC 671 100% 67
2402:dc40::/32 Valid RIR databaseAPNIC 636 100% 67
103.48.104.0/24 Valid RIR databaseAPNIC 39 6%low visibility 28
103.48.105.0/24 Valid RIR databaseAPNIC 39 6%low visibility 28
103.48.106.0/24 Valid RIR databaseAPNIC 39 6%low visibility 28
103.48.107.0/24 Valid RIR databaseAPNIC 39 6%low visibility 28
103.79.33.0/24 Valid RIR databaseAPNIC 39 6%low visibility 28
103.79.34.0/24 Valid RIR databaseAPNIC 39 6%low visibility 28
103.243.41.0/24 Valid RIR databaseAPNIC 39 6%low visibility 28
103.243.42.0/24 Valid RIR databaseAPNIC 39 6%low visibility 28
103.243.43.0/24 Valid RIR databaseAPNIC 39 6%low visibility 28
103.98.108.0/22 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS134331: AS134331:AS-SLSPL. 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 (AS134331 isn't in the set, or no route object for AS134331 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 objectsAS134331 in itNot covered
AS134331:AS-SLSPL APNIC 161841 Yes 0

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

  • Route object: none2
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
Route object: none2402:dc40:300::/40No route object for it. A route object for 2402:dc40::/32 with origin AS134331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134331 in the RIR database for the space.39 of 636
Route object: none2402:dc40:700::/40No route object for it. A route object for 2402:dc40::/32 with origin AS134331 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134331 in the RIR database for the space.39 of 636

Route objects not announced

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

43.254.34.0/23APNICValid
43.254.34.0/24APNICValid
103.48.104.0/23APNICValid
103.48.106.0/23APNICValid
103.79.32.0/23APNICValid
103.79.34.0/23APNICValid
103.79.35.0/24APNICValid
103.96.220.0/23APNICValid
103.96.222.0/23APNICValid
103.98.108.0/23APNICValid
103.98.110.0/23APNICValid
103.143.212.0/23APNICValid
103.143.212.0/24APNICValid
103.143.213.0/24APNICValid
103.170.224.0/23APNICValid
103.170.224.0/24APNICValid
103.170.225.0/24APNICValid
103.197.132.0/23APNICValid
103.197.134.0/23APNICValid
103.243.40.0/23APNICValid
103.243.42.0/23APNICValid
161.248.64.0/23APNICValid
220.158.176.0/23APNICValid
220.158.178.0/23APNICValid
2001:df4:d6c0::/48APNICValid
2001:df6:7200::/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.