bgpreport

Network · data from 2026-11-12

AS134970 Tuhin Enterprise Bangladesh

Registry name: TUHINENTERPRISE-AS-AP - Tuhin Enterprise Bangladesh, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS134970, 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:7380::/32 No ROA None 634 100% 68
2407:7380:b000::/48 No ROA None 634 100% 68
2407:7380:c000::/48 No ROA None 634 100% 68
2407:7380:d000::/48 No ROA None 634 100% 68
2407:7380:e000::/48 No ROA None 634 100% 68
2407:7380:f000::/48 No ROA None 634 100% 68
103.251.246.0/24 Valid RIR databaseAPNIC 673 100% 69
220.247.131.0/24 Valid RIR databaseAPNIC 673 100% 69
103.251.245.0/24 Valid RIR databaseAPNIC 672 100% 67
103.251.247.0/24 Valid RIR databaseAPNIC 672 100% 67
220.247.128.0/24 Valid RIR databaseAPNIC 672 100% 67
220.247.130.0/24 Valid RIR databaseAPNIC 672 100% 67
2407:7380::/48 Valid RIR databaseAPNIC 635 100% 70
2407:7380:1000::/48 Valid RIR databaseAPNIC 635 100% 69
2407:7380:2000::/48 Valid RIR databaseAPNIC 635 100% 69
2407:7380:3000::/48 Valid RIR databaseAPNIC 635 100% 69
2407:7380:4000::/48 Valid RIR databaseAPNIC 635 100% 69
2407:7380:5000::/48 Valid RIR databaseAPNIC 635 100% 69
2407:7380:6000::/48 Valid RIR databaseAPNIC 635 100% 69
2407:7380:7000::/48 Valid RIR databaseAPNIC 635 100% 69
2407:7380:8000::/48 Valid RIR databaseAPNIC 635 100% 69
2407:7380:9000::/48 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS134970'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 16 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2407:7380::/32No ROA covers it. Add a ROA for AS134970, maxLength 32.634 of 636
Route object: none2407:7380::/32No route object for it. Add a route object with origin AS134970 in the RIR database for the space.634 of 636
ROA: none2407:7380:b000::/48No ROA covers it. Add a ROA for AS134970, maxLength 48.634 of 636
Route object: none2407:7380:b000::/48No route object for it. Add a route object with origin AS134970 in the RIR database for the space.634 of 636
ROA: none2407:7380:c000::/48No ROA covers it. Add a ROA for AS134970, maxLength 48.634 of 636
Route object: none2407:7380:c000::/48No route object for it. Add a route object with origin AS134970 in the RIR database for the space.634 of 636
ROA: none2407:7380:d000::/48No ROA covers it. Add a ROA for AS134970, maxLength 48.634 of 636
Route object: none2407:7380:d000::/48No route object for it. Add a route object with origin AS134970 in the RIR database for the space.634 of 636
ROA: none2407:7380:e000::/48No ROA covers it. Add a ROA for AS134970, maxLength 48.634 of 636
Route object: none2407:7380:e000::/48No route object for it. Add a route object with origin AS134970 in the RIR database for the space.634 of 636
ROA: none2407:7380:f000::/48No ROA covers it. Add a ROA for AS134970, maxLength 48.634 of 636
Route object: none2407:7380:f000::/48No route object for it. Add a route object with origin AS134970 in the RIR database for the space.634 of 636

Route objects not announced

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

220.247.130.0/23APNICValid
2407:7380:b::/48APNICValid
2407:7380:c::/48APNICValid
2407:7380:d::/48APNICValid

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.