bgpreport

Network · data from 2026-11-12

AS9730 Bharti Airtel AS9730

Registry name: BHARTITELESONIC-AS-IN-AP - Bharti Telesonic Ltd, IN · PeeringDB

9IPv4 routes 44.4% RPKI valid · 44.4% with a route object
2IPv6 routes 0.0% RPKI valid · 0.0% with a route object
5RPKI invalid 5 origin · 0 maxLength
2No ROA 7 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS9730, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9730, 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.
152.52.9.0/24 Invalid: origin Other origin only 152 23% 51
182.95.251.0/24 Invalid: origin Other origin only 140 21% 51
2401:4900:beff::/48 Invalid: origin None 92 14% 41
182.71.218.0/24 Invalid: origin Other origin only 5 1%low visibility 3
203.101.99.0/24 Invalid: origin Other origin only 3 0%low visibility 3
203.193.178.0/24 No ROA Other origin only 672 100% 67
2404:a800:4001::/48 No ROA None 636 100% 70
59.144.97.0/24 Valid RIR databaseAPNIC 672 100% 67
61.246.50.0/24 Valid RIR databaseAPNIC 672 100% 67
152.52.48.0/24 Valid RIR databaseAPNIC 672 100% 67
125.22.113.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS9730's PeeringDB record names no AS-SET.

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

  • ROA: origin5
  • ROA: none2
  • Route object: none7
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: origin152.52.9.0/24ROAs covering it name AS9498, not AS9730. If AS9730 should announce it, add a ROA for AS9730.152 of 673
Route object: none152.52.9.0/24Route objects for it name AS9498. Add a route object with origin AS9730 in the RIR database for the space.152 of 673
ROA: origin182.95.251.0/24ROAs covering it name AS9498, not AS9730. If AS9730 should announce it, add a ROA for AS9730.140 of 673
Route object: none182.95.251.0/24Route objects for it name AS9498. Add a route object with origin AS9730 in the RIR database for the space.140 of 673
ROA: origin2401:4900:beff::/48ROAs covering it name AS45609, not AS9730. If AS9730 should announce it, add a ROA for AS9730.92 of 636
Route object: none2401:4900:beff::/48No route object for it. Add a route object with origin AS9730 in the RIR database for the space.92 of 636
ROA: origin182.71.218.0/24ROAs covering it name AS9498, not AS9730. If AS9730 should announce it, add a ROA for AS9730.5 of 673
Route object: none182.71.218.0/24Route objects for it name AS9498. Add a route object with origin AS9730 in the RIR database for the space.5 of 673
ROA: origin203.101.99.0/24ROAs covering it name AS9498, AS24560, not AS9730. If AS9730 should announce it, add a ROA for AS9730.3 of 673
Route object: none203.101.99.0/24Route objects for it name AS9498. Add a route object with origin AS9730 in the RIR database for the space.3 of 673
ROA: none203.193.178.0/24No ROA covers it. Add a ROA for AS9730, maxLength 24.672 of 673
Route object: none203.193.178.0/24Route objects for it name AS4755, AS7633. Add a route object with origin AS9730 in the RIR database for the space.672 of 673
ROA: none2404:a800:4001::/48No ROA covers it. Add a ROA for AS9730, maxLength 48.636 of 636
Route object: none2404:a800:4001::/48No route object for it. Add a route object with origin AS9730 in the RIR database for the space.636 of 636

Route objects not announced

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

59.145.72.0/23APNICValid
59.145.72.0/24APNICValid
59.145.73.0/24APNICValid
122.185.26.0/24APNICValid
125.20.15.0/24APNICValid
125.62.189.0/24RADBNo ROA
164.164.121.0/24APNICValid
202.123.32.0/24RADB, REACHNo ROA
202.123.33.0/24RADB, REACHNo ROA
202.123.34.0/24RADB, REACHNo ROA
202.123.35.0/24RADBNo ROA
203.129.192.0/24RADBNo ROA
203.193.129.0/24RADBNo 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.