bgpreport

Network · data from 2026-11-12

AS17471 Grameen Cybernet

Registry name: CYBERNET-BD-AS - Grameen Cybernet Ltd. Bangladesh. AS for local peering and transit. Dhaka, BD · PeeringDB

61IPv4 routes 100.0% RPKI valid · 100.0% with a route object
24IPv6 routes 66.7% RPKI valid · 66.7% with a route object
8RPKI invalid 0 origin · 8 maxLength
0No ROA 8 with no route object for this origin
10Low visibility seen by under 10% of full-table peers
66Route objects not announced registered with origin AS17471, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17471, 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.
2407:f040:1000::/48 Invalid: maxLength Nonecovered by 2407:f040:1000::/36 0 0%low visibility 1
2407:f040:1100::/48 Invalid: maxLength Nonecovered by 2407:f040:1000::/36 0 0%low visibility 1
2407:f040:1200::/48 Invalid: maxLength Nonecovered by 2407:f040:1000::/36 0 0%low visibility 1
2407:f040:1400::/48 Invalid: maxLength Nonecovered by 2407:f040:1000::/36 0 0%low visibility 1
2407:f040:1500::/48 Invalid: maxLength Nonecovered by 2407:f040:1000::/36 0 0%low visibility 1
2407:f040:1600::/48 Invalid: maxLength Nonecovered by 2407:f040:1000::/36 0 0%low visibility 1
2407:f040:1700::/48 Invalid: maxLength Nonecovered by 2407:f040:1000::/36 0 0%low visibility 1
2407:f040:1800::/48 Invalid: maxLength Nonecovered by 2407:f040:1000::/36 0 0%low visibility 1
103.7.112.0/22 Valid RIR databaseAPNIC 673 100% 69
122.99.96.0/22 Valid RIR databaseAPNIC 673 100% 69
122.99.98.0/24 Valid RIR databaseAPNIC 673 100% 70
122.99.100.0/22 Valid RIR databaseAPNIC 673 100% 69
122.99.101.0/24 Valid RIR databaseAPNIC 673 100% 70
203.83.160.0/19 Valid RIR databaseAPNIC 673 100% 69
203.83.170.0/24 Valid RIR databaseAPNIC 673 100% 70
203.191.32.0/23 Valid RIR databaseAPNIC 673 100% 69
103.7.112.0/24 Valid RIR databaseAPNIC 672 100% 68
103.7.113.0/24 Valid RIR databaseAPNIC 672 100% 68
103.7.114.0/24 Valid RIR databaseAPNIC 672 100% 68
103.7.115.0/24 Valid RIR databaseAPNIC 672 100% 68
122.99.96.0/24 Valid RIR databaseAPNIC 672 100% 68
122.99.97.0/24 Valid RIR databaseAPNIC 672 100% 68
122.99.99.0/24 Valid RIR databaseAPNIC 672 100% 68
122.99.100.0/24 Valid RIR databaseAPNIC 672 100% 67
122.99.102.0/24 Valid RIR databaseAPNIC 672 100% 68
122.99.103.0/24 Valid RIR databaseAPNIC 672 100% 68
202.125.65.0/24 Valid RIR databaseAPNIC 672 100% 68
202.125.69.0/24 Valid RIR databaseAPNIC 672 100% 68
202.125.70.0/24 Valid RIR databaseAPNIC 672 100% 68
202.125.71.0/24 Valid RIR databaseAPNIC 672 100% 68
202.125.73.0/24 Valid RIR databaseAPNIC 672 100% 68
202.125.74.0/24 Valid RIR databaseAPNIC 672 100% 68
202.125.75.0/24 Valid RIR databaseAPNIC 672 100% 68
202.125.76.0/24 Valid RIR databaseAPNIC 672 100% 68
202.125.77.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.160.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.161.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.162.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.163.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.164.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.165.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.166.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.167.0/24 Valid RIR databaseAPNIC 672 100% 67
203.83.168.0/24 Valid RIR databaseAPNIC 672 100% 67
203.83.169.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.171.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.172.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.173.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.174.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.175.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.176.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.177.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.178.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.179.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.180.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.181.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.182.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.183.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.184.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.185.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.186.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.187.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.188.0/24 Valid RIR databaseAPNIC 672 100% 68
203.83.189.0/24 Valid RIR databaseAPNIC 672 100% 67
203.83.191.0/24 Valid RIR databaseAPNIC 672 100% 68
203.191.32.0/24 Valid RIR databaseAPNIC 672 100% 67
203.191.33.0/24 Valid RIR databaseAPNIC 672 100% 67
2407:f040::/32 Valid RIR databaseAPNIC 635 100% 70
2407:f040:1000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:2000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:3000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:4000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:5000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:6000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:7000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:8000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:9000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:a000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:b000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:c000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:d000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:e000::/36 Valid RIR databaseAPNIC 635 100% 70
2407:f040:f000::/36 Valid RIR databaseAPNIC 635 100% 70
202.125.64.0/20 Valid RIR databaseAPNIC 4 1%low visibility 3
203.83.190.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

AS17471'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 82 are in fix.csv.

  • ROA: maxLength8
  • Route object: none8
  • Route object: not announced66
ChangePrefix or setDetailFull-table peers
ROA: maxLength2407:f040:1000::/48ROA 2407:f040::/32 AS17471 has maxLength 36; the route is a /48. Raise the maxLength, or add a ROA for 2407:f040:1000::/48.0 of 636
Route object: none2407:f040:1000::/48No route object for it. A route object for 2407:f040:1000::/36 with origin AS17471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17471 in the RIR database for the space.0 of 636
ROA: maxLength2407:f040:1100::/48ROA 2407:f040::/32 AS17471 has maxLength 36; the route is a /48. Raise the maxLength, or add a ROA for 2407:f040:1100::/48.0 of 636
Route object: none2407:f040:1100::/48No route object for it. A route object for 2407:f040:1000::/36 with origin AS17471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17471 in the RIR database for the space.0 of 636
ROA: maxLength2407:f040:1200::/48ROA 2407:f040::/32 AS17471 has maxLength 36; the route is a /48. Raise the maxLength, or add a ROA for 2407:f040:1200::/48.0 of 636
Route object: none2407:f040:1200::/48No route object for it. A route object for 2407:f040:1000::/36 with origin AS17471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17471 in the RIR database for the space.0 of 636
ROA: maxLength2407:f040:1400::/48ROA 2407:f040::/32 AS17471 has maxLength 36; the route is a /48. Raise the maxLength, or add a ROA for 2407:f040:1400::/48.0 of 636
Route object: none2407:f040:1400::/48No route object for it. A route object for 2407:f040:1000::/36 with origin AS17471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17471 in the RIR database for the space.0 of 636
ROA: maxLength2407:f040:1500::/48ROA 2407:f040::/32 AS17471 has maxLength 36; the route is a /48. Raise the maxLength, or add a ROA for 2407:f040:1500::/48.0 of 636
Route object: none2407:f040:1500::/48No route object for it. A route object for 2407:f040:1000::/36 with origin AS17471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17471 in the RIR database for the space.0 of 636
ROA: maxLength2407:f040:1600::/48ROA 2407:f040::/32 AS17471 has maxLength 36; the route is a /48. Raise the maxLength, or add a ROA for 2407:f040:1600::/48.0 of 636
Route object: none2407:f040:1600::/48No route object for it. A route object for 2407:f040:1000::/36 with origin AS17471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17471 in the RIR database for the space.0 of 636
ROA: maxLength2407:f040:1700::/48ROA 2407:f040::/32 AS17471 has maxLength 36; the route is a /48. Raise the maxLength, or add a ROA for 2407:f040:1700::/48.0 of 636
Route object: none2407:f040:1700::/48No route object for it. A route object for 2407:f040:1000::/36 with origin AS17471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17471 in the RIR database for the space.0 of 636
ROA: maxLength2407:f040:1800::/48ROA 2407:f040::/32 AS17471 has maxLength 36; the route is a /48. Raise the maxLength, or add a ROA for 2407:f040:1800::/48.0 of 636
Route object: none2407:f040:1800::/48No route object for it. A route object for 2407:f040:1000::/36 with origin AS17471 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17471 in the RIR database for the space.0 of 636

Route objects not announced

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

103.7.112.0/23APNICValid
103.7.114.0/23APNICValid
122.99.96.0/21APNIC, RADBValid
122.99.96.0/23APNICValid
122.99.98.0/23APNICValid
122.99.100.0/23APNICValid
122.99.102.0/23APNICValid
198.32.198.0/24RADBNo ROA
202.125.64.0/21APNIC, RADBValid
202.125.64.0/22APNICValid
202.125.68.0/22APNICValid
202.125.68.0/23APNICValid
202.125.70.0/23APNICValid
202.125.72.0/21APNICValid
202.125.72.0/22APNICValid
202.125.72.0/23APNICValid
202.125.74.0/23APNICValid
202.125.76.0/22APNICValid
202.125.76.0/23APNICValid
202.125.78.0/23APNICValid
203.83.160.0/20APNICValid
203.83.160.0/21APNICValid
203.83.160.0/22APNICValid
203.83.160.0/23APNICValid
203.83.162.0/23APNICValid
203.83.164.0/22APNICValid
203.83.164.0/23APNICValid
203.83.166.0/23APNICValid
203.83.168.0/21APNICValid
203.83.168.0/22APNICValid
203.83.168.0/23APNICValid
203.83.170.0/23APNICValid
203.83.172.0/22APNICValid
203.83.172.0/23APNICValid
203.83.174.0/23APNICValid
203.83.176.0/20APNICValid
203.83.176.0/21APNICValid
203.83.176.0/22APNICValid
203.83.176.0/23APNICValid
203.83.178.0/23APNICValid
203.83.180.0/22APNICValid
203.83.180.0/23APNICValid
203.83.182.0/23APNICValid
203.83.184.0/21APNICValid
203.83.184.0/22APNICValid
203.83.184.0/23APNICValid
203.83.186.0/23APNICValid
203.83.188.0/22APNICValid
203.83.188.0/23APNICValid
203.83.190.0/23APNICValid
203.105.128.0/19RADBNo ROA
2407:f040::/33APNICValid
2407:f040::/34APNICValid
2407:f040::/35APNICValid
2407:f040::/36APNICValid
2407:f040:2000::/35APNICValid
2407:f040:4000::/34APNICValid
2407:f040:4000::/35APNICValid
2407:f040:6000::/35APNICValid
2407:f040:8000::/33APNICValid
2407:f040:8000::/34APNICValid
2407:f040:8000::/35APNICValid
2407:f040:a000::/35APNICValid
2407:f040:c000::/34APNICValid
2407:f040:c000::/35APNICValid
2407:f040:e000::/35APNICValid

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.