bgpreport

Network · data from 2026-11-12

AS56201 Zoho-IN

Registry name: ZOHO-IN - Zoho Corporation Pvt. Ltd,, IN · PeeringDB

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

Announced routes

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

169.148.178.0/23 No ROA Other IRR onlyRADB 671 100% 67
74.188.228.0/23 Valid RIR databaseAPNIC 673 100% 67
103.84.216.0/23 Valid RIR databaseAPNIC 673 100% 67
103.84.218.0/23 Valid RIR databaseAPNIC 673 100% 67
103.89.74.0/23 Valid RIR databaseAPNIC 673 100% 66
103.103.196.0/23 Valid RIR databaseAPNIC 673 100% 66
103.103.198.0/23 Valid RIR databaseAPNIC 673 100% 66
103.117.158.0/23 Valid RIR databaseAPNIC 673 100% 66
169.148.136.0/23 Valid RIR databaseAPNIC 673 100% 66
169.148.148.0/23 Valid RIR databaseAPNIC 673 100% 66
169.148.150.0/24 Valid RIR databaseAPNIC 673 100% 66
199.67.76.0/23 Valid RIR databaseAPNIC 673 100% 66
74.188.230.0/23 Valid RIR databaseAPNIC 672 100% 66
169.148.134.0/23 Valid RIR databaseAPNIC 672 100% 66
169.148.146.0/23 Valid RIR databaseAPNIC 672 100% 66
199.67.78.0/23 Valid RIR databaseAPNIC 672 100% 66
199.67.94.0/23 Valid RIR databaseAPNIC 672 100% 67
43.239.212.0/23 Valid RIR databaseAPNIC 671 100% 66
43.239.214.0/23 Valid RIR databaseAPNIC 671 100% 66
74.188.224.0/23 Valid RIR databaseAPNIC 671 100% 66
74.188.226.0/23 Valid RIR databaseAPNIC 671 100% 66
169.148.132.0/24 Valid RIR databaseAPNIC 671 100% 66
169.148.133.0/24 Valid RIR databaseAPNIC 671 100% 66
169.148.138.0/24 Valid RIR databaseAPNIC 671 100% 66
169.148.139.0/24 Valid RIR databaseAPNIC 671 100% 67
169.148.140.0/23 Valid RIR databaseAPNIC 671 100% 67
169.148.142.0/23 Valid RIR databaseAPNIC 671 100% 66
169.148.144.0/23 Valid RIR databaseAPNIC 671 100% 66
169.148.172.0/23 Valid RIR databaseAPNIC, RADB 671 100% 66
169.148.173.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
169.148.174.0/23 Valid RIR databaseAPNIC, RADB 671 100% 66
169.148.180.0/24 Valid RIR databaseAPNIC 671 100% 66
169.148.176.0/23 Valid RIR databaseAPNIC 670 100% 67
2400:6d20:10::/47 Valid RIR databaseAPNIC 635 100% 69
2400:6d20:fc00::/47 Valid RIR databaseAPNIC 635 100% 69
2400:6d20:fc02::/47 Valid RIR databaseAPNIC 635 100% 69
103.84.216.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
169.148.144.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
199.67.94.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
169.148.149.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

AS56201'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 81 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced79
ChangePrefix or setDetailFull-table peers
ROA: none169.148.178.0/23No ROA covers it. Add a ROA for AS56201, maxLength 23.671 of 673
Route object: RIR169.148.178.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

43.239.212.0/24APNICValid
43.239.213.0/24APNIC, RADBValid
43.239.214.0/24APNICValid
43.239.215.0/24APNICValid
43.246.104.0/23RADBValid
43.246.104.0/24RADBValid
43.246.105.0/24RADBValid
43.246.106.0/23RADBValid
43.246.106.0/24RADBValid
43.246.107.0/24RADBValid
74.188.224.0/24APNICValid
74.188.225.0/24APNICValid
74.188.226.0/24APNICValid
74.188.227.0/24APNICValid
74.188.228.0/24APNICValid
74.188.229.0/24APNICValid
74.188.230.0/24APNICValid
74.188.231.0/24APNICValid
74.188.232.0/23APNICValid
74.188.234.0/23APNICValid
74.188.236.0/23APNICValid
74.188.238.0/23APNICValid
103.84.217.0/24APNICValid
103.84.218.0/24APNICValid
103.84.219.0/24APNICValid
103.89.74.0/24APNICValid
103.89.75.0/24APNICValid
103.103.196.0/22APNICValid
103.103.196.0/24APNICValid
103.103.197.0/24APNICValid
103.103.198.0/24APNICValid
103.103.199.0/24APNICValid
103.117.158.0/24APNICValid
103.117.159.0/24APNICValid
103.122.78.0/24APNICValid
136.143.172.0/24ARINValid
136.143.173.0/24ARINValid
169.148.134.0/24APNICValid
169.148.135.0/24APNICValid
169.148.136.0/24APNICValid
169.148.137.0/24APNICValid
169.148.138.0/23APNICValid
169.148.140.0/24APNICValid
169.148.141.0/24APNICValid
169.148.142.0/24APNICValid
169.148.143.0/24APNICValid
169.148.145.0/24APNICValid
169.148.146.0/24APNICValid
169.148.147.0/24APNICValid
169.148.148.0/24APNICValid
169.148.151.0/24ARINValid
169.148.152.0/23ARINValid
169.148.152.0/24ARINValid
169.148.162.0/24ARINValid
169.148.172.0/24APNIC, RADBValid
169.148.174.0/24APNIC, RADBValid
169.148.175.0/24APNIC, RADBValid
169.148.176.0/24APNICValid
169.148.177.0/24APNICValid
169.148.178.0/24RADBNo ROA
169.148.179.0/24RADBNo ROA
199.67.76.0/24APNICValid
199.67.77.0/24APNICValid
199.67.78.0/24APNICValid
199.67.79.0/24APNICValid
199.67.95.0/24APNICValid
202.0.112.0/24APNICNo ROA
2001:df0:217::/48APNICValid
2400:6d20::/47APNICValid
2400:6d20::/48APNICValid
2400:6d20:1::/48APNICValid
2400:6d20:2::/47APNICValid
2400:6d20:2::/48APNICValid
2400:6d20:3::/48APNICValid
2400:6d20:12::/47APNICValid
2602:801:c00a::/48ARINValid
2602:801:c00b::/48ARINValid
2602:801:c00c::/48ARINValid
2602:801:c00d::/48ARINNo 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.