bgpreport

Network · data from 2026-11-12

AS132770 Gazon Communications India Limited

Registry name: GAZON-AS-IN - Gazon Communications India Limited, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132770, 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.113.138.0/24 Invalid: origin None 2 0%low visibility 2
103.113.139.0/24 Invalid: origin None 2 0%low visibility 2
103.83.214.0/24 No ROA Other origin only 671 100% 67
43.227.20.0/24 Valid RIR databaseAPNIC 673 100% 67
43.227.21.0/24 Valid RIR databaseAPNIC 673 100% 67
43.227.22.0/24 Valid RIR databaseAPNIC 673 100% 67
43.227.23.0/24 Valid RIR databaseAPNIC 673 100% 67
43.228.73.0/24 Valid RIR databaseAPNIC 673 100% 67
43.228.74.0/24 Valid RIR databaseAPNIC 673 100% 67
43.228.75.0/24 Valid RIR databaseAPNIC 673 100% 67
43.241.25.0/24 Valid RIR databaseAPNIC 673 100% 67
103.59.104.0/24 Valid RIR databaseAPNIC 673 100% 67
103.94.59.0/24 Valid RIR databaseAPNIC 673 100% 66
103.211.61.0/24 Valid RIR databaseAPNIC 673 100% 66
103.211.62.0/24 Valid RIR databaseAPNIC 673 100% 67
103.239.84.0/24 Valid RIR databaseAPNIC 673 100% 67
103.241.83.0/24 Valid RIR databaseAPNIC 673 100% 67
103.243.115.0/24 Valid RIR databaseAPNIC 673 100% 67
103.254.52.0/24 Valid RIR databaseAPNIC 673 100% 66
103.254.54.0/24 Valid RIR databaseAPNIC 673 100% 67
103.254.55.0/24 Valid RIR databaseAPNIC 673 100% 67
43.228.72.0/24 Valid RIR databaseAPNIC 672 100% 67
43.241.24.0/24 Valid RIR databaseAPNIC 672 100% 67
43.241.26.0/24 Valid RIR databaseAPNIC 672 100% 67
43.241.27.0/24 Valid RIR databaseAPNIC 672 100% 67
103.93.240.0/24 Valid RIR databaseAPNIC 672 100% 67
103.126.68.0/24 Valid RIR databaseAPNIC 672 100% 67
103.126.69.0/24 Valid RIR databaseAPNIC 672 100% 67
103.126.70.0/24 Valid RIR databaseAPNIC 672 100% 67
103.126.71.0/24 Valid RIR databaseAPNIC 672 100% 67
103.127.164.0/24 Valid RIR databaseAPNIC 672 100% 67
103.127.165.0/24 Valid RIR databaseAPNIC 672 100% 67
103.127.167.0/24 Valid RIR databaseAPNIC 672 100% 67
103.148.121.0/24 Valid RIR databaseAPNIC 672 100% 67
103.178.206.0/24 Valid RIR databaseAPNIC 672 100% 67
103.184.86.0/24 Valid RIR databaseAPNIC 672 100% 67
103.184.87.0/24 Valid RIR databaseAPNIC 672 100% 67
103.211.60.0/24 Valid RIR databaseAPNIC 672 100% 67
103.211.63.0/24 Valid RIR databaseAPNIC 672 100% 67
103.221.72.0/24 Valid RIR databaseAPNIC 672 100% 67
103.221.73.0/24 Valid RIR databaseAPNIC 672 100% 67
103.221.75.0/24 Valid RIR databaseAPNIC 672 100% 67
103.239.85.0/24 Valid RIR databaseAPNIC 672 100% 67
103.239.87.0/24 Valid RIR databaseAPNIC 672 100% 67
103.243.112.0/24 Valid RIR databaseAPNIC 672 100% 67
103.243.114.0/24 Valid RIR databaseAPNIC 672 100% 67
103.249.240.0/24 Valid RIR databaseAPNIC 672 100% 67
103.249.242.0/24 Valid RIR databaseAPNIC 672 100% 67
103.251.208.0/24 Valid RIR databaseAPNIC 672 100% 67
103.251.209.0/24 Valid RIR databaseAPNIC 672 100% 67
103.251.211.0/24 Valid RIR databaseAPNIC 672 100% 67
103.254.53.0/24 Valid RIR databaseAPNIC 672 100% 67
150.129.128.0/24 Valid RIR databaseAPNIC 672 100% 67
150.129.129.0/24 Valid RIR databaseAPNIC 672 100% 67
150.129.130.0/24 Valid RIR databaseAPNIC 672 100% 67
150.129.131.0/24 Valid RIR databaseAPNIC 672 100% 67
150.129.156.0/24 Valid RIR databaseAPNIC 672 100% 67
150.129.157.0/24 Valid RIR databaseAPNIC 672 100% 67
150.129.159.0/24 Valid RIR databaseAPNIC 672 100% 67
157.10.150.0/24 Valid RIR databaseAPNIC 672 100% 67
157.10.151.0/24 Valid RIR databaseAPNIC 672 100% 67
160.22.232.0/24 Valid RIR databaseAPNIC 672 100% 67
160.22.233.0/24 Valid RIR databaseAPNIC 672 100% 67
163.53.200.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
163.53.201.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.136.68.0/24 Valid RIR databaseAPNIC 672 100% 67
202.136.69.0/24 Valid RIR databaseAPNIC 672 100% 67
202.136.70.0/24 Valid RIR databaseAPNIC 672 100% 67
45.119.57.0/24 Valid RIR databaseAPNIC 671 100% 67
45.119.58.0/24 Valid RIR databaseAPNIC 671 100% 67
45.252.72.0/24 Valid RIR databaseAPNIC 671 100% 66
45.252.75.0/24 Valid RIR databaseAPNIC 671 100% 67
103.81.36.0/24 Valid RIR databaseAPNIC 671 100% 66
103.81.37.0/24 Valid RIR databaseAPNIC 671 100% 66
103.81.38.0/24 Valid RIR databaseAPNIC 671 100% 66
103.81.39.0/24 Valid RIR databaseAPNIC 671 100% 66
103.93.241.0/24 Valid RIR databaseAPNIC 671 100% 66
103.93.242.0/24 Valid RIR databaseAPNIC 671 100% 66
103.93.243.0/24 Valid RIR databaseAPNIC 671 100% 66
103.94.57.0/24 Valid RIR databaseAPNIC 671 100% 66
103.125.72.0/24 Valid RIR databaseAPNIC 671 100% 66
103.125.73.0/24 Valid RIR databaseAPNIC 671 100% 66
103.127.166.0/24 Valid RIR databaseAPNIC 671 100% 66
103.178.207.0/24 Valid RIR databaseAPNIC 671 100% 66
103.204.36.0/24 Valid RIR databaseAPNIC 671 100% 66
103.204.37.0/24 Valid RIR databaseAPNIC 671 100% 66
103.204.38.0/24 Valid RIR databaseAPNIC 671 100% 66
103.204.39.0/24 Valid RIR databaseAPNIC 671 100% 66
103.221.74.0/24 Valid RIR databaseAPNIC 671 100% 66
103.239.86.0/24 Valid RIR databaseAPNIC 671 100% 66
103.241.80.0/24 Valid RIR databaseAPNIC 671 100% 66
103.241.81.0/24 Valid RIR databaseAPNIC 671 100% 66
103.241.82.0/24 Valid RIR databaseAPNIC 671 100% 66
103.243.113.0/24 Valid RIR databaseAPNIC 671 100% 66
103.249.241.0/24 Valid RIR databaseAPNIC 671 100% 66
103.249.243.0/24 Valid RIR databaseAPNIC 671 100% 66
103.251.210.0/24 Valid RIR databaseAPNIC 671 100% 66
150.129.158.0/24 Valid RIR databaseAPNIC 671 100% 66
160.30.72.0/24 Valid RIR databaseAPNIC 671 100% 66
160.30.73.0/24 Valid RIR databaseAPNIC 671 100% 66
163.53.202.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
163.53.203.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
165.99.226.0/24 Valid RIR databaseAPNIC 671 100% 66
165.99.227.0/24 Valid RIR databaseAPNIC 671 100% 66
165.101.109.0/24 Valid RIR databaseAPNIC 671 100% 66
165.101.204.0/24 Valid RIR databaseAPNIC 671 100% 66
202.136.71.0/24 Valid RIR databaseAPNIC 671 100% 66
45.119.59.0/24 Valid RIR databaseAPNIC 670 100% 66
45.252.73.0/24 Valid RIR databaseAPNIC 670 100% 66
45.252.74.0/24 Valid RIR databaseAPNIC 670 100% 66
2404:24c0::/32 Valid RIR databaseAPNIC 635 100% 67
2404:4980::/32 Valid RIR databaseAPNIC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS132770: AS132770:AS-GAZONCUSTOMERS. 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 (AS132770 isn't in the set, or no route object for AS132770 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 objectsAS132770 in itNot covered
AS132770:AS-GAZONCUSTOMERS APNIClists itself further down6 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS151747:AS-PARVEZ2 … 1,472191339,591 Yes 3

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

  • ROA: origin2
  • ROA: none1
  • Route object: none3
  • AS-SET: missing member6
  • Route object: not announced62
ChangePrefix or setDetailFull-table peers
ROA: origin103.113.138.0/24ROAs covering it name AS136334, not AS132770. If AS132770 should announce it, add a ROA for AS132770.2 of 673
Route object: none103.113.138.0/24No route object for it. Add a route object with origin AS132770 in the RIR database for the space.2 of 673
ROA: origin103.113.139.0/24ROAs covering it name AS136334, not AS132770. If AS132770 should announce it, add a ROA for AS132770.2 of 673
Route object: none103.113.139.0/24No route object for it. Add a route object with origin AS132770 in the RIR database for the space.2 of 673
ROA: none103.83.214.0/24No ROA covers it. Add a ROA for AS132770, maxLength 24.671 of 673
Route object: none103.83.214.0/24Route objects for it name AS135785. Add a route object with origin AS132770 in the RIR database for the space.671 of 673
AS-SET: missing memberAS132770:AS-GAZONCUSTOMERSAS132770:AS-GAZONCUSTOMERS (APNIC) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS132770:AS-GAZONCUSTOMERSAS132770:AS-GAZONCUSTOMERS (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS132770:AS-GAZONCUSTOMERSAS132770:AS-GAZONCUSTOMERS (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS132770:AS-GAZONCUSTOMERSAS132770:AS-GAZONCUSTOMERS (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS132770:AS-GAZONCUSTOMERSAS132770:AS-GAZONCUSTOMERS (APNIC) lists AS151747:AS-PARVEZ2; no IRR database read has it.
AS-SET: missing memberAS132770:AS-GAZONCUSTOMERSAS132770:AS-GAZONCUSTOMERS (APNIC) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

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

43.227.20.0/22APNICValid
43.227.20.0/23APNICValid
43.227.22.0/23APNICValid
43.228.72.0/22APNICValid
43.228.72.0/23APNICValid
43.228.74.0/23APNICValid
43.241.24.0/22APNICValid
43.241.24.0/23APNICValid
43.241.26.0/23APNICValid
43.243.172.0/24APNICInvalid: origin
43.243.173.0/24APNICInvalid: origin
43.243.175.0/24APNICInvalid: origin
45.252.72.0/22APNICValid
45.252.72.0/23APNICValid
45.252.74.0/23APNICValid
103.59.105.0/24APNICInvalid: origin
103.59.106.0/24APNICInvalid: origin
103.59.107.0/24APNICInvalid: origin
103.94.56.0/22APNICValid
103.94.56.0/23APNICValid
103.94.58.0/23APNICValid
103.125.72.0/23APNICValid
103.126.68.0/22APNICValid
103.126.68.0/23APNICValid
103.126.70.0/23APNICValid
103.178.206.0/23APNICValid
103.221.72.0/22APNICValid
103.221.72.0/23APNICValid
103.221.74.0/23APNICValid
103.226.168.0/24APNICInvalid: origin
103.226.169.0/24APNICInvalid: origin
103.226.170.0/24APNICInvalid: origin
103.226.171.0/24APNICInvalid: origin
103.239.84.0/22APNICValid
103.239.84.0/23APNICValid
103.239.86.0/23APNICValid
103.243.112.0/22APNICValid
103.243.112.0/23APNICValid
103.243.114.0/23APNICValid
103.249.240.0/22APNICValid
103.249.240.0/23APNICValid
103.249.242.0/23APNICValid
103.251.208.0/22APNICValid
103.251.208.0/23APNICValid
103.251.210.0/23APNICValid
103.254.52.0/22APNICValid
103.254.52.0/23APNICValid
103.254.54.0/23APNICValid
150.129.128.0/22APNICValid
150.129.128.0/23APNICValid
150.129.130.0/23APNICValid
150.129.156.0/22APNICValid
150.129.156.0/23APNICValid
150.129.158.0/23APNICValid
157.10.150.0/23APNICValid
160.30.72.0/23APNICValid
163.53.200.0/22APNICValid
163.53.200.0/23APNICValid
163.53.202.0/23APNICValid
165.99.226.0/23APNICValid
165.101.229.0/24APNICValid
2401:73e0::/32APNICValid

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.