bgpreport

Network · data from 2026-11-12

AS148993 DIANAHOSTLTD-AS-AP - Diana Host Ltd

Registry name: DIANAHOSTLTD-AS-AP - Diana Host Ltd, BD · not in PeeringDB

4IPv4 routes 50.0% RPKI valid · 50.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
2Route objects not announced registered with origin AS148993, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS148993, 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.
138.252.56.0/24 Invalid: origin Other origin only 0 0%low visibility 1
138.252.57.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.169.160.0/24 Valid RIR databaseAPNIC 673 100% 67
103.169.161.0/24 Valid RIR databaseAPNIC 672 100% 68

AS-SET

AS148993 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: origin2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin138.252.56.0/24ROAs covering it name AS134738, not AS148993. If AS148993 should announce it, add a ROA for AS148993.0 of 673
Route object: none138.252.56.0/24Route objects for it name AS134738. Add a route object with origin AS148993 in the RIR database for the space.0 of 673
ROA: origin138.252.57.0/24ROAs covering it name AS134738, not AS148993. If AS148993 should announce it, add a ROA for AS148993.0 of 673
Route object: none138.252.57.0/24Route objects for it name AS134738. Add a route object with origin AS148993 in the RIR database for the space.0 of 673

Route objects not announced

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

103.169.160.0/23APNICValid
2001:df0:7c0::/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.