bgpreport

Network · data from 2026-11-12

AS45536 Readylink Internet

Registry name: READYLINK-AS-AP - Readylink Internet Services Limited, IN · PeeringDB

23IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
0Low visibility seen by under 10% of full-table peers
15Route objects not announced registered with origin AS45536, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45536, 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.
43.225.165.0/24 Valid RIR databaseAPNIC 673 100% 67
103.21.76.0/24 Valid RIR databaseAPNIC 673 100% 67
123.255.250.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.223.189.0/24 Valid RIR databaseAPNIC 673 100% 67
203.223.190.0/24 Valid RIR databaseAPNIC 673 100% 67
43.225.164.0/24 Valid RIR databaseAPNIC 671 100% 67
43.225.167.0/24 Valid RIR databaseAPNIC 671 100% 67
103.224.32.0/24 Valid RIR databaseAPNIC 671 100% 67
103.224.33.0/24 Valid RIR databaseAPNIC 671 100% 67
103.224.35.0/24 Valid RIR databaseAPNIC 671 100% 67
123.255.249.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
157.20.226.0/23 Valid RIR databaseAPNIC 671 100% 67
157.20.226.0/24 Valid RIR databaseAPNIC 671 100% 67
203.223.188.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
43.225.166.0/24 Valid RIR databaseAPNIC 670 100% 66
103.21.77.0/24 Valid RIR databaseAPNIC 670 100% 66
103.21.78.0/24 Valid RIR databaseAPNIC 670 100% 66
103.21.79.0/24 Valid RIR databaseAPNIC 670 100% 66
103.224.34.0/24 Valid RIR databaseAPNIC 670 100% 66
123.255.248.0/24 Valid RIR databaseAPNIC, RADB 670 100% 66
123.255.251.0/24 Valid RIR databaseAPNIC 670 100% 66
157.20.227.0/24 Valid RIR databaseAPNIC 670 100% 66
203.223.191.0/24 Valid RIR databaseAPNIC 670 100% 66
2405:e8c0::/32 Valid RIR databaseAPNIC 635 100% 67

AS-SET

AS45536'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 15 are in fix.csv.

  • Route object: not announced15

Route objects not announced

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

43.225.164.0/22APNICValid
43.225.164.0/23APNICValid
43.225.166.0/23APNICValid
103.21.76.0/22APNICValid
103.21.76.0/23APNICValid
103.21.78.0/23APNICValid
103.224.32.0/22APNICValid
103.224.32.0/23APNICValid
103.224.34.0/23APNICValid
123.255.248.0/22APNICValid
123.255.248.0/23APNICValid
123.255.250.0/23APNICValid
203.223.188.0/22APNICValid
203.223.188.0/23APNICValid
203.223.190.0/23APNICValid

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.