bgpreport

Network · data from 2026-11-12

AS38207 Rajesh Multi Channel

Registry name: RAJESHDIGITAL-IN-TRANSIT-AS-AP - RAJESH DIGITAL & DATACOM PRIVATE LIMITED, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38207, 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.
110.172.16.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
110.172.16.0/23 Valid RIR databaseAPNIC, RADB 672 100% 67
110.172.20.0/22 Valid RIR databaseAPNIC 672 100% 67
110.172.20.0/23 Valid RIR databaseAPNIC 672 100% 67
219.90.96.0/20 Valid RIR databaseAPNIC 672 100% 67
2402:4300::/32 Valid RIR databaseAPNIC 635 100% 67
110.172.16.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
110.172.17.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
110.172.18.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
110.172.19.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
110.172.20.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
110.172.21.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
110.172.22.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
110.172.23.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
219.90.101.0/24 Valid RIR databaseAPNIC, RADB 42 6%low visibility 29
219.90.102.0/24 Valid RIR databaseAPNIC, RADB 42 6%low visibility 29
219.90.103.0/24 Valid RIR databaseAPNIC, RADB 42 6%low visibility 29
2402:4300::/40 Valid RIR databaseAPNIC 42 7%low visibility 29

AS-SET

AS38207'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 35 are in fix.csv.

  • Route object: not announced35

Route objects not announced

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

110.172.16.0/21APNIC, RADBValid
110.172.18.0/23APNICValid
110.172.22.0/23APNICValid
203.188.224.0/24REACHInvalid: origin
203.188.228.0/24REACHInvalid: origin
203.188.229.0/24REACHInvalid: origin
203.188.230.0/24REACHInvalid: origin
203.188.231.0/24REACHInvalid: origin
219.90.96.0/21APNIC, RADBValid
219.90.96.0/22APNIC, RADBValid
219.90.96.0/23APNIC, RADBValid
219.90.96.0/24APNIC, RADBValid
219.90.97.0/24APNIC, RADBValid
219.90.98.0/23APNIC, RADBValid
219.90.98.0/24APNIC, RADBValid
219.90.99.0/24APNIC, RADBValid
219.90.100.0/22APNIC, RADBValid
219.90.100.0/23APNIC, RADBValid
219.90.100.0/24APNIC, RADBValid
219.90.102.0/23APNIC, RADBValid
219.90.104.0/21APNIC, RADBValid
219.90.104.0/22APNIC, RADBValid
219.90.104.0/23APNIC, RADBValid
219.90.104.0/24APNIC, RADBValid
219.90.105.0/24APNIC, RADBValid
219.90.106.0/23APNIC, RADBValid
219.90.106.0/24APNIC, RADBValid
219.90.107.0/24APNIC, RADBValid
219.90.108.0/22APNIC, RADBValid
219.90.108.0/23APNIC, RADBValid
219.90.108.0/24APNIC, REACHValid
219.90.109.0/24APNIC, REACHValid
219.90.110.0/23APNIC, RADBValid
219.90.110.0/24APNIC, REACHValid
219.90.111.0/24APNIC, REACHValid

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.