bgpreport

Network · data from 2026-11-12

AS133232 SAMPARK ESTATES PVT. LTD.

Registry name: SAMPARKESTATES-AS-IN - SAMPARK ESTATES PVT. LTD., IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133232, 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.17.102.0/24 No ROA Other IRR onlyRADB 672 100% 66
103.17.159.0/24 No ROA Other IRR onlyRADB 672 100% 66
45.250.225.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.17.158.0/24 No ROA Other IRR onlyRADB 671 100% 66
103.26.225.0/24 No ROA Other IRR onlyRADB 671 100% 66
103.26.227.0/24 No ROA Other IRR onlyRADB 671 100% 66
150.107.24.0/24 No ROA Other IRR onlyRADB 671 100% 66
103.69.222.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
103.69.221.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 66
2001:df7:6e00::/48 Valid RIR databaseAPNIC, RADB, REACH 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS133232: AS133232:AS-CUSTOMERS. 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 (AS133232 isn't in the set, or no route object for AS133232 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 objectsAS133232 in itNot covered
AS133232:AS-CUSTOMERS RADB 33149,216 Yes 0
APNIC (also) 121658 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 82 are in fix.csv.

  • ROA: none9
  • Route object: RIR7
  • Route object: not announced66
ChangePrefix or setDetailFull-table peers
ROA: none103.17.102.0/24No ROA covers it. Add a ROA for AS133232, maxLength 24.672 of 673
Route object: RIR103.17.102.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.17.159.0/24No ROA covers it. Add a ROA for AS133232, maxLength 24.672 of 673
Route object: RIR103.17.159.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.250.225.0/24No ROA covers it. Add a ROA for AS133232, maxLength 24.671 of 673
Route object: RIR45.250.225.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.17.158.0/24No ROA covers it. Add a ROA for AS133232, maxLength 24.671 of 673
Route object: RIR103.17.158.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.26.225.0/24No ROA covers it. Add a ROA for AS133232, maxLength 24.671 of 673
Route object: RIR103.26.225.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.26.227.0/24No ROA covers it. Add a ROA for AS133232, maxLength 24.671 of 673
Route object: RIR103.26.227.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none150.107.24.0/24No ROA covers it. Add a ROA for AS133232, maxLength 24.671 of 673
Route object: RIR150.107.24.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.69.222.0/24No ROA covers it. Add a ROA for AS133232, maxLength 24.672 of 673
ROA: none103.69.221.0/24No ROA covers it. Add a ROA for AS133232, maxLength 24.671 of 673

Route objects not announced

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

43.243.80.0/24APNICInvalid: origin
43.243.81.0/24APNICInvalid: origin
43.243.82.0/24APNIC, RADBNo ROA
43.243.83.0/24APNICInvalid: origin
45.248.168.0/22APNICValid
45.248.168.0/23APNICValid
45.248.168.0/24APNICValid
45.248.169.0/24APNICValid
45.248.170.0/23APNICValid
45.248.170.0/24APNICValid
45.248.171.0/24APNICValid
45.250.224.0/24RADBNo ROA
45.250.226.0/24RADBNo ROA
103.17.128.0/22APNICValid
103.17.128.0/23APNICValid
103.17.128.0/24APNICValid
103.17.129.0/24APNICValid
103.17.130.0/23APNICValid
103.17.130.0/24APNIC, RADBValid
103.17.131.0/24APNICValid
103.17.156.0/24RADBNo ROA
103.17.157.0/24RADBNo ROA
103.26.224.0/24RADBNo ROA
103.26.226.0/24RADBNo ROA
103.69.220.0/24APNICInvalid: origin
103.69.223.0/24APNICInvalid: origin
103.80.112.0/22REACHInvalid: origin
103.80.112.0/24REACHInvalid: origin
103.80.113.0/24REACHInvalid: origin
103.80.114.0/24REACHInvalid: origin
103.80.115.0/24REACHInvalid: origin
103.107.174.0/24RADBNo ROA
103.110.166.0/24RADBNo ROA
103.120.248.0/24RADBNo ROA
103.120.249.0/24RADBNo ROA
103.120.250.0/24RADBNo ROA
103.120.251.0/24RADBNo ROA
103.150.138.0/24RADBNo ROA
103.150.139.0/24RADBNo ROA
103.206.134.0/24RADBNo ROA
103.230.220.0/24APNICInvalid: origin
103.230.221.0/24APNICInvalid: origin
103.230.222.0/24APNICInvalid: origin
103.230.223.0/24APNICInvalid: origin
103.232.236.0/24APNIC, RADBNo ROA
103.232.237.0/24APNIC, RADBNo ROA
103.232.238.0/24APNIC, RADBNo ROA
103.232.239.0/24APNICInvalid: origin
103.235.0.0/24APNICInvalid: origin
103.235.1.0/24APNICInvalid: origin
103.235.2.0/24APNICInvalid: origin
103.235.3.0/24APNICInvalid: origin
103.251.48.0/22APNICInvalid: origin
150.107.25.0/24RADBNo ROA
150.107.26.0/24RADBNo ROA
150.107.27.0/24RADBNo ROA
157.119.84.0/24RADBNo ROA
157.119.85.0/24RADBNo ROA
157.119.86.0/24RADBNo ROA
157.119.87.0/24RADBNo ROA
160.25.64.0/24RADBNo ROA
160.25.65.0/24RADBNo ROA
2001:df7:2e00::/48RADB, REACHNo ROA
2401:bb00::/32RADBNo ROA
2403:6040::/32RADBNo ROA
2403:7440::/32RADBNo ROA

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.