bgpreport

Network · data from 2026-11-12

AS133287 Andhra Pradesh State FiberNet

Registry name: APSFL-AS - Andhra Pradesh State FiberNet Limited, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133287, 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.63.16.0/22 No ROA RIR databaseAPNIC 673 100% 67
103.63.124.0/22 No ROA RIR databaseAPNIC 673 100% 66
103.63.127.0/24 No ROA RIR databaseAPNIC 673 100% 67
45.123.4.0/22 No ROA RIR databaseAPNIC 672 100% 66
103.211.108.0/22 Valid Other IRR onlyRADB 673 100% 66
103.211.111.0/24 Valid Other IRR onlyRADB 673 100% 67
160.238.72.0/23 Valid Other IRR onlyRADB 673 100% 67
160.238.73.0/24 Valid Other IRR onlyRADB 673 100% 67
160.238.74.0/23 Valid Other IRR onlyRADB 673 100% 67
160.238.75.0/24 Valid Other IRR onlyRADB 673 100% 67
160.238.72.0/24 Valid Other IRR onlyRADB 672 100% 66
160.238.74.0/24 Valid Other IRR onlyRADB 672 100% 66
103.211.108.0/24 Valid Other IRR onlyRADB 42 6%low visibility 29
160.238.72.0/22 Valid Other IRR onlyRADB 42 6%low visibility 29
223.196.163.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.167.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.169.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.174.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.175.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.181.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.184.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.185.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.186.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.187.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.188.0/24 Valid RIR databaseAPNIC 672 100% 66
223.196.160.0/20 Valid RIR databaseAPNIC 671 100% 66
223.196.160.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.161.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.162.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.164.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.165.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.166.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.170.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.171.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.172.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.173.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.176.0/20 Valid RIR databaseAPNIC 671 100% 66
223.196.176.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.184.0/21 Valid RIR databaseAPNIC 671 100% 66
223.196.190.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.192.0/21 Valid RIR databaseAPNIC 671 100% 66
223.196.192.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.196.0/24 Valid RIR databaseAPNIC 671 100% 66
223.196.168.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
223.196.180.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
223.196.189.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
223.196.192.0/22 Valid RIR databaseAPNIC 42 6%low visibility 29
223.196.193.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
223.196.194.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
223.196.195.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
223.196.198.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
223.196.199.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
223.196.198.0/23 Valid RIR databaseAPNIC 35 5%low visibility 27

AS-SET

PeeringDB's irr_as_set for AS133287: AS-APFIBER. 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 (AS133287 isn't in the set, or no route object for AS133287 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 objectsAS133287 in itNot covered
AS-APFIBER In no IRR database read today.

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: none4
  • Route object: RIR10
  • AS-SET: not found1
  • Route object: not announced59
ChangePrefix or setDetailFull-table peers
ROA: none103.63.16.0/22No ROA covers it. Add a ROA for AS133287, maxLength 22.673 of 673
ROA: none103.63.124.0/22No ROA covers it. Add a ROA for AS133287, maxLength 22.673 of 673
ROA: none103.63.127.0/24No ROA covers it. Add a ROA for AS133287, maxLength 24.673 of 673
ROA: none45.123.4.0/22No ROA covers it. Add a ROA for AS133287, maxLength 22.672 of 673
Route object: RIR103.211.108.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.211.111.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR160.238.72.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR160.238.73.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR160.238.74.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR160.238.75.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR160.238.72.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR160.238.74.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.211.108.0/24Route object only in RADB. Add it in the RIR database for the space.42 of 673
Route object: RIR160.238.72.0/22Route object only in RADB. Add it in the RIR database for the space.42 of 673
AS-SET: not foundAS-APFIBERPeeringDB names AS-APFIBER; no IRR database read has it.

Route objects not announced

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

45.123.4.0/23APNICNo ROA
45.123.4.0/24APNICNo ROA
45.123.5.0/24APNICNo ROA
45.123.6.0/23APNICNo ROA
45.123.6.0/24APNICNo ROA
45.123.7.0/24APNICNo ROA
103.63.16.0/23APNICNo ROA
103.63.16.0/24APNICNo ROA
103.63.17.0/24APNICNo ROA
103.63.18.0/23APNICNo ROA
103.63.18.0/24APNICNo ROA
103.63.19.0/24APNICNo ROA
103.63.124.0/23APNICNo ROA
103.63.124.0/24APNICNo ROA
103.63.125.0/24APNICNo ROA
103.63.126.0/23APNICNo ROA
103.63.126.0/24APNICNo ROA
103.211.109.0/24RADBValid
103.211.110.0/24RADBValid
223.196.160.0/19APNICValid
223.196.160.0/21APNICValid
223.196.160.0/22APNICValid
223.196.160.0/23APNICValid
223.196.162.0/23APNICValid
223.196.164.0/22APNICValid
223.196.164.0/23APNICValid
223.196.166.0/23APNICValid
223.196.168.0/21APNICValid
223.196.168.0/22APNICValid
223.196.168.0/23APNICValid
223.196.170.0/23APNICValid
223.196.172.0/22APNICValid
223.196.172.0/23APNICValid
223.196.174.0/23APNICValid
223.196.176.0/21APNICValid
223.196.176.0/22APNICValid
223.196.176.0/23APNICValid
223.196.177.0/24APNICValid
223.196.178.0/23APNICValid
223.196.178.0/24APNICValid
223.196.179.0/24APNICValid
223.196.180.0/22APNICValid
223.196.180.0/23APNICValid
223.196.182.0/23APNICValid
223.196.182.0/24APNICValid
223.196.183.0/24APNICValid
223.196.184.0/22APNICValid
223.196.184.0/23APNICValid
223.196.186.0/23APNICValid
223.196.188.0/22APNICValid
223.196.188.0/23APNICValid
223.196.190.0/23APNICValid
223.196.191.0/24APNICValid
223.196.192.0/23APNICValid
223.196.194.0/23APNICValid
223.196.196.0/22APNICValid
223.196.196.0/23APNICValid
223.196.197.0/24APNICValid
2404:c580::/32APNICNo 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.