bgpreport

Network · data from 2026-11-12

AS45194 Syscon Infoway

Registry name: SIPL-AS - Syscon Infoway Pvt. Ltd., IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45194, 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.

2401:a100:2::/48 Invalid: origin Nonecovered by 2401:a100::/32 19 3%low visibility 12
2401:a100:3::/48 Invalid: origin RIR databaseAPNIC 19 3%low visibility 12
2401:a100::/32 Invalid: origin RIR databaseAPNIC 2 0%low visibility 2
103.54.96.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.54.97.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.54.98.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.54.99.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.236.112.0/24 No ROA Other IRR onlyRADB 672 100% 67
45.114.156.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.114.157.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.114.158.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.114.159.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.51.153.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.51.154.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.58.7.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.97.180.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.97.182.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.199.139.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.231.2.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.231.3.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
137.59.64.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
137.59.65.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
137.59.66.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
137.59.67.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
137.59.68.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
137.59.69.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
45.117.212.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
45.124.48.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
45.124.51.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
154.84.223.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS45194: AS45194:AS-SYSCON-IN. 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 (AS45194 isn't in the set, or no route object for AS45194 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 objectsAS45194 in itNot covered
AS45194:AS-SYSCON-IN APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE 1,262144334,505 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 136 are in fix.csv.

  • ROA: origin3
  • ROA: none9
  • Route object: none1
  • Route object: RIR9
  • AS-SET: missing member5
  • Route object: not announced109
ChangePrefix or setDetailFull-table peers
ROA: origin2401:a100:2::/48ROAs covering it name AS151347, not AS45194. If AS45194 should announce it, add a ROA for AS45194.19 of 636
Route object: none2401:a100:2::/48No route object for it. A route object for 2401:a100::/32 with origin AS45194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45194 in the RIR database for the space.19 of 636
ROA: origin2401:a100:3::/48ROAs covering it name AS151347, not AS45194. If AS45194 should announce it, add a ROA for AS45194.19 of 636
ROA: origin2401:a100::/32ROAs covering it name AS151347, not AS45194. If AS45194 should announce it, add a ROA for AS45194.2 of 636
ROA: none103.54.96.0/24No ROA covers it. Add a ROA for AS45194, maxLength 24.672 of 673
Route object: RIR103.54.96.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.54.97.0/24No ROA covers it. Add a ROA for AS45194, maxLength 24.672 of 673
Route object: RIR103.54.97.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.54.98.0/24No ROA covers it. Add a ROA for AS45194, maxLength 24.672 of 673
Route object: RIR103.54.98.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.54.99.0/24No ROA covers it. Add a ROA for AS45194, maxLength 24.672 of 673
Route object: RIR103.54.99.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.236.112.0/24No ROA covers it. Add a ROA for AS45194, maxLength 24.672 of 673
Route object: RIR103.236.112.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.114.156.0/24No ROA covers it. Add a ROA for AS45194, maxLength 24.671 of 673
Route object: RIR45.114.156.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.114.157.0/24No ROA covers it. Add a ROA for AS45194, maxLength 24.671 of 673
Route object: RIR45.114.157.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.114.158.0/24No ROA covers it. Add a ROA for AS45194, maxLength 24.671 of 673
Route object: RIR45.114.158.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.114.159.0/24No ROA covers it. Add a ROA for AS45194, maxLength 24.671 of 673
Route object: RIR45.114.159.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
AS-SET: missing memberAS45194:AS-SYSCON-INAS45194:AS-SYSCON-IN (APNIC) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS45194:AS-SYSCON-INAS45194:AS-SYSCON-IN (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS45194:AS-SYSCON-INAS45194:AS-SYSCON-IN (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS45194:AS-SYSCON-INAS45194:AS-SYSCON-IN (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS45194:AS-SYSCON-INAS45194:AS-SYSCON-IN (APNIC) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

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

43.249.180.0/22APNICValid
43.249.180.0/24APNICValid
43.249.181.0/24APNICValid
43.249.182.0/24APNICValid
43.249.183.0/24APNICValid
45.117.212.0/22APNICValid
45.117.212.0/23APNICValid
45.117.213.0/24APNIC, RADBValid
45.117.214.0/23APNICValid
45.117.214.0/24APNIC, RADBValid
45.117.215.0/24APNIC, RADBValid
45.119.28.0/24RADBNo ROA
45.119.29.0/24RADBNo ROA
45.119.30.0/24RADBNo ROA
45.119.31.0/24RADBNo ROA
45.124.48.0/22APNIC, RADBValid
45.124.48.0/23APNICValid
45.124.49.0/24APNIC, RADBValid
45.124.50.0/23APNICValid
45.124.50.0/24APNIC, RADBValid
103.2.138.0/24RADBNo ROA
103.51.138.0/24RADBNo ROA
103.51.152.0/22APNICValid
103.51.152.0/23APNICValid
103.51.152.0/24APNIC, RADBValid
103.51.154.0/23APNICValid
103.51.155.0/24APNIC, RADBValid
103.58.4.0/22APNICValid
103.58.4.0/23APNICValid
103.58.4.0/24APNIC, RADBValid
103.58.5.0/24APNIC, RADBValid
103.58.6.0/23APNICValid
103.58.6.0/24APNIC, RADBValid
103.58.56.0/22RADBNo ROA
103.58.56.0/24RADBNo ROA
103.58.57.0/24RADBNo ROA
103.58.58.0/24RADBNo ROA
103.58.59.0/24RADBNo ROA
103.61.108.0/22APNICNo ROA
103.84.80.0/24APNICInvalid: origin
103.84.81.0/24APNICInvalid: origin
103.84.82.0/24APNICInvalid: origin
103.84.83.0/24APNICInvalid: origin
103.97.180.0/22APNICValid
103.97.180.0/23APNICValid
103.97.181.0/24APNIC, RADBValid
103.97.182.0/23APNICValid
103.97.183.0/24APNIC, RADBValid
103.118.4.0/24RADBNo ROA
103.118.5.0/24RADBNo ROA
103.118.6.0/24RADBNo ROA
103.118.7.0/24RADBNo ROA
103.142.107.0/24APNIC, RADBValid
103.172.74.0/24RADBNo ROA
103.172.75.0/24RADBNo ROA
103.183.25.0/24APNICValid
103.185.137.0/24RADBNo ROA
103.185.237.0/24APNIC, RADBValid
103.199.136.0/22APNICValid
103.199.136.0/23APNICValid
103.199.136.0/24APNIC, RADBValid
103.199.137.0/24APNIC, RADBValid
103.199.138.0/23APNICValid
103.199.138.0/24APNIC, RADBValid
103.204.164.0/24RADBNo ROA
103.204.165.0/24RADBNo ROA
103.204.166.0/24RADBNo ROA
103.204.167.0/24RADBNo ROA
103.209.36.0/24APNIC, RADBValid
103.209.37.0/24APNIC, RADBValid
103.212.140.0/24APNICInvalid: origin
103.212.141.0/24APNICInvalid: origin
103.212.142.0/24APNICInvalid: origin
103.212.143.0/24APNICInvalid: origin
103.231.0.0/22APNICValid
103.231.0.0/23APNICValid
103.231.0.0/24APNIC, RADBValid
103.231.1.0/24APNIC, RADBValid
103.231.2.0/23APNICValid
103.232.237.0/24RADBNo ROA
103.233.26.0/23RADBNo ROA
110.5.72.0/21APNIC, RADBNo ROA
110.5.72.0/24APNICInvalid: origin
110.5.73.0/24APNICInvalid: origin
110.5.74.0/24APNICInvalid: origin
110.5.75.0/24APNICInvalid: origin
110.5.76.0/24APNICInvalid: origin
110.5.77.0/24APNICInvalid: origin
110.5.78.0/24APNICInvalid: origin
110.5.79.0/24APNICInvalid: origin
137.59.64.0/22APNICValid
137.59.64.0/23APNICValid
137.59.66.0/23APNICValid
137.59.68.0/22APNICValid
137.59.68.0/23APNICValid
137.59.70.0/23APNICValid
137.59.70.0/24APNICValid
137.59.71.0/24APNIC, RADBValid
139.5.236.0/24APNICInvalid: origin
139.5.237.0/24APNICInvalid: origin
139.5.238.0/24APNICInvalid: origin
139.5.239.0/24APNICInvalid: origin
154.84.244.0/24AFRINICInvalid: origin
154.84.245.0/24AFRINICInvalid: origin
154.84.247.0/24AFRINICInvalid: origin
154.84.248.0/24AFRINICInvalid: origin
202.134.144.0/20RADBNo ROA
202.134.160.0/19RADBNo ROA
2401:a100:0:5::/64APNICInvalid: origin

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.