bgpreport

Network · data from 2026-11-12

AS153304 RAHATECHNOLOGY-AS-AP - Raha Technology

Registry name: RAHATECHNOLOGY-AS-AP - Raha Technology, BD · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 0.0% 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
0Route objects not announced registered with origin AS153304, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS153304, 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.
160.30.176.0/24 Invalid: origin Other origin only 3 0%low visibility 3
160.30.177.0/24 Invalid: origin Other origin only 3 0%low visibility 3

AS-SET

AS153304 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 4 are in fix.csv.

  • ROA: origin2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin160.30.176.0/24ROAs covering it name AS150180, not AS153304. If AS153304 should announce it, add a ROA for AS153304.3 of 673
Route object: none160.30.176.0/24Route objects for it name AS150180. Add a route object with origin AS153304 in the RIR database for the space.3 of 673
ROA: origin160.30.177.0/24ROAs covering it name AS150180, not AS153304. If AS153304 should announce it, add a ROA for AS153304.3 of 673
Route object: none160.30.177.0/24Route objects for it name AS150180. Add a route object with origin AS153304 in the RIR database for the space.3 of 673

Route objects not announced

Every route object with origin AS153304 is announced.

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.