bgpreport

Network · data from 2026-11-12

AS17747 Siti Cable Network Limited

Registry name: SITINETWORS-IN-AP - SITI NETWORKS LIMITED, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17747, 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.199.226.0/23 No ROA None 672 100% 67
203.81.240.0/23 No ROA None 671 100% 67
203.81.242.0/23 No ROA None 671 100% 67
103.199.224.0/22 No ROA None 670 100% 66
103.199.224.0/23 No ROA None 670 100% 66
203.81.240.0/22 No ROA None 670 100% 66
45.249.84.0/23 Valid Nonecovered by 45.249.84.0/22 671 100% 67
45.249.86.0/23 Valid Nonecovered by 45.249.84.0/22 671 100% 67
103.217.244.0/23 Valid Nonecovered by 103.217.244.0/22 671 100% 67
103.217.244.0/24 Valid Nonecovered by 103.217.244.0/22 671 100% 67
103.217.246.0/23 Valid Nonecovered by 103.217.244.0/22 671 100% 67
45.249.86.0/24 Valid Nonecovered by 45.249.84.0/22 670 100% 67
103.217.245.0/24 Valid Nonecovered by 103.217.244.0/22 670 100% 66
103.217.246.0/24 Valid Nonecovered by 103.217.244.0/22 670 100% 66
103.217.247.0/24 Valid Nonecovered by 103.217.244.0/22 670 100% 66
45.249.84.0/24 Valid Nonecovered by 45.249.84.0/22 1 0%low visibility 1
45.249.85.0/24 Valid Nonecovered by 45.249.84.0/22 1 0%low visibility 1
45.249.87.0/24 Valid Nonecovered by 45.249.84.0/22 1 0%low visibility 1
103.199.226.0/24 Valid RIR databaseAPNIC 672 100% 66
103.199.227.0/24 Valid RIR databaseAPNIC 672 100% 66
103.171.100.0/24 Valid RIR databaseAPNIC 671 100% 67
103.171.101.0/24 Valid RIR databaseAPNIC 671 100% 67
150.107.9.0/24 Valid RIR databaseAPNIC 671 100% 66
45.249.84.0/22 Valid RIR databaseAPNIC 670 100% 66
103.184.74.0/23 Valid RIR databaseAPNIC 670 100% 66
103.184.74.0/24 Valid RIR databaseAPNIC 670 100% 66
103.184.75.0/24 Valid RIR databaseAPNIC 670 100% 66
103.217.244.0/22 Valid RIR databaseAPNIC 670 100% 66
150.107.8.0/23 Valid RIR databaseAPNIC 670 100% 66
150.107.8.0/24 Valid RIR databaseAPNIC 670 100% 66
202.142.109.0/24 Valid RIR databaseAPNIC, RADB 670 100% 66
202.142.111.0/24 Valid RIR databaseAPNIC 670 100% 66
202.142.117.0/24 Valid RIR databaseAPNIC 670 100% 66
202.142.121.0/24 Valid RIR databaseAPNIC 670 100% 66
202.142.122.0/24 Valid RIR databaseAPNIC 670 100% 66
2402:ea80::/32 Valid RIR databaseAPNIC 635 100% 69
2402:ea80::/48 Valid RIR databaseAPNIC 635 100% 69
203.81.240.0/24 Valid RIR databaseAPNIC 3 0%low visibility 3
203.81.241.0/24 Valid RIR databaseAPNIC 3 0%low visibility 3
203.81.243.0/24 Valid RIR databaseAPNIC 3 0%low visibility 3
103.199.225.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
103.199.224.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
203.81.242.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS17747: APNIC::AS17747: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 (AS17747 isn't in the set, or no route object for AS17747 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 objectsAS17747 in itNot covered
APNIC::AS17747:AS-CUSTOMERS APNIC 1711,290 Yes 6

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

  • ROA: none6
  • Route object: none18
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
ROA: none103.199.226.0/23No ROA covers it. Add a ROA for AS17747, maxLength 23.672 of 673
Route object: none103.199.226.0/23No route object for it. Add a route object with origin AS17747 in the RIR database for the space.672 of 673
ROA: none203.81.240.0/23No ROA covers it. Add a ROA for AS17747, maxLength 23.671 of 673
Route object: none203.81.240.0/23No route object for it. Add a route object with origin AS17747 in the RIR database for the space.671 of 673
ROA: none203.81.242.0/23No ROA covers it. Add a ROA for AS17747, maxLength 23.671 of 673
Route object: none203.81.242.0/23No route object for it. Add a route object with origin AS17747 in the RIR database for the space.671 of 673
ROA: none103.199.224.0/22No ROA covers it. Add a ROA for AS17747, maxLength 22.670 of 673
Route object: none103.199.224.0/22No route object for it. Add a route object with origin AS17747 in the RIR database for the space.670 of 673
ROA: none103.199.224.0/23No ROA covers it. Add a ROA for AS17747, maxLength 23.670 of 673
Route object: none103.199.224.0/23No route object for it. Add a route object with origin AS17747 in the RIR database for the space.670 of 673
ROA: none203.81.240.0/22No ROA covers it. Add a ROA for AS17747, maxLength 22.670 of 673
Route object: none203.81.240.0/22No route object for it. Add a route object with origin AS17747 in the RIR database for the space.670 of 673
Route object: none45.249.84.0/23No route object for it. A route object for 45.249.84.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.671 of 673
Route object: none45.249.86.0/23No route object for it. A route object for 45.249.84.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.671 of 673
Route object: none103.217.244.0/23No route object for it. A route object for 103.217.244.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.671 of 673
Route object: none103.217.244.0/24No route object for it. A route object for 103.217.244.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.671 of 673
Route object: none103.217.246.0/23No route object for it. A route object for 103.217.244.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.671 of 673
Route object: none45.249.86.0/24No route object for it. A route object for 45.249.84.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.670 of 673
Route object: none103.217.245.0/24No route object for it. A route object for 103.217.244.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.670 of 673
Route object: none103.217.246.0/24No route object for it. A route object for 103.217.244.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.670 of 673
Route object: none103.217.247.0/24No route object for it. A route object for 103.217.244.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.670 of 673
Route object: none45.249.84.0/24No route object for it. A route object for 45.249.84.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.1 of 673
Route object: none45.249.85.0/24No route object for it. A route object for 45.249.84.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.1 of 673
Route object: none45.249.87.0/24No route object for it. A route object for 45.249.84.0/22 with origin AS17747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17747 in the RIR database for the space.1 of 673

Route objects not announced

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

103.84.164.0/24APNICValid
103.171.100.0/23APNICValid
202.90.46.0/23RADBNo ROA
202.142.64.0/20RADBNo ROA
202.142.76.0/23RADBNo ROA
202.142.78.0/23RADBNo ROA
202.142.80.0/20RADBNo ROA
202.142.80.0/21RADBNo ROA
202.142.80.0/24APNICValid
202.142.82.0/24APNICValid
202.142.84.0/24APNICValid
202.142.88.0/24APNICValid
202.142.94.0/24APNICValid
202.142.96.0/21RADBNo ROA
202.142.104.0/22RADBNo ROA
202.142.104.0/23RADBNo ROA
202.142.108.0/22RADBNo ROA
202.142.108.0/23APNICValid
202.142.110.0/23RADBNo ROA
202.142.112.0/20RADBNo ROA
202.142.112.0/22RADBNo ROA
202.142.116.0/22RADBNo ROA
202.142.116.0/24APNICValid
202.142.120.0/23RADBNo ROA
202.142.122.0/23RADBNo ROA
202.142.124.0/23RADBNo 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.