bgpreport

Network · data from 2026-11-12

AS153383 NAZIMHOST-AS-AP - Nazim Host

Registry name: NAZIMHOST-AS-AP - Nazim Host, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS153383, 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.
64.69.108.0/24 Invalid: origin Other origin only 2 0%low visibility 2
64.69.109.0/24 Invalid: origin Other origin only 2 0%low visibility 2
69.33.68.0/22 Valid Other IRR onlyRADB 673 100% 66
69.33.76.0/22 Valid Other IRR onlyRADB 673 100% 66
82.163.24.0/24 Valid Other IRR onlyRADB 673 100% 66
82.163.25.0/24 Valid Other IRR onlyRADB 673 100% 66
82.163.26.0/24 Valid Other IRR onlyRADB 673 100% 66
82.163.27.0/24 Valid Other IRR onlyRADB 673 100% 66
64.69.107.0/24 Valid RIR databaseARIN, RADB 673 100% 66
64.69.110.0/24 Valid RIR databaseARIN, RADB 673 100% 66
64.69.111.0/24 Valid RIR databaseARIN, RADB 673 100% 66
69.33.164.0/22 Valid RIR databaseARIN, RADB 673 100% 66
69.33.172.0/22 Valid RIR databaseARIN, RADB 673 100% 66
69.33.184.0/22 Valid RIR databaseARIN, RADB 673 100% 66
72.244.32.0/22 Valid RIR databaseARIN, RADB 673 100% 68
82.139.208.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
82.139.209.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
82.139.210.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
82.139.211.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
82.139.212.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
82.139.213.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
82.139.240.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
104.145.216.0/24 Valid RIR databaseARIN, RADB 673 100% 66
104.145.217.0/24 Valid RIR databaseARIN, RADB 673 100% 66
104.145.218.0/24 Valid RIR databaseARIN, RADB 673 100% 66
104.145.219.0/24 Valid RIR databaseARIN, RADB 673 100% 66

AS-SET

AS153383 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 11 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin64.69.108.0/24ROAs covering it name AS834, AS21769, not AS153383. If AS153383 should announce it, add a ROA for AS153383.2 of 673
Route object: none64.69.108.0/24Route objects for it name AS834. Add a route object with origin AS153383 in the RIR database for the space.2 of 673
ROA: origin64.69.109.0/24ROAs covering it name AS834, AS21769, not AS153383. If AS153383 should announce it, add a ROA for AS153383.2 of 673
Route object: none64.69.109.0/24Route objects for it name AS834. Add a route object with origin AS153383 in the RIR database for the space.2 of 673
Route object: RIR69.33.68.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR69.33.76.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.163.24.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.163.25.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.163.26.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.163.27.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

2001:df4:87c0::/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.