bgpreport

Network · data from 2026-11-12

AS136134 INDEPENDENT-AS-AP - Independent Univeristy, Bangladesh

Registry name: INDEPENDENT-AS-AP - Independent Univeristy, Bangladesh, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136134, 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.166.94.0/24 Invalid: origin Other origin only 4 1%low visibility 4
103.81.70.0/23 Invalid: maxLength Nonecovered by 103.81.68.0/22 111 16% 47
103.81.68.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.81.68.0/24 Valid RIR databaseAPNIC 673 100% 69
103.81.71.0/24 Valid RIR databaseAPNIC 673 100% 68
103.81.69.0/24 Valid RIR databaseAPNIC 672 100% 68

AS-SET

AS136134 isn't in PeeringDB, where networks name their 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 6 are in fix.csv.

  • ROA: origin1
  • ROA: maxLength1
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin103.166.94.0/24ROAs covering it name AS134136, not AS136134. If AS136134 should announce it, add a ROA for AS136134.4 of 673
Route object: none103.166.94.0/24Route objects for it name AS134136. Add a route object with origin AS136134 in the RIR database for the space.4 of 673
ROA: maxLength103.81.70.0/23ROA 103.81.68.0/22 AS136134 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 103.81.70.0/23.111 of 673
Route object: none103.81.70.0/23No route object for it. A route object for 103.81.68.0/22 with origin AS136134 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136134 in the RIR database for the space.111 of 673

Route objects not announced

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

103.81.70.0/24APNICValid
2402:bc0::/32APNICValid

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.