bgpreport

Network · data from 2026-11-12

AS152945 DMX-VN - DAINTY CLOUD INC

Registry name: DMX-VN - DAINTY CLOUD INC, VN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS152945, 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.
2001:df4:6c0::/48 No ROA None 636 100% 67
160.25.88.0/23 Valid RIR databaseAPNIC 673 100% 66

AS-SET

AS152945 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 2 are in fix.csv.

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none2001:df4:6c0::/48No ROA covers it. Add a ROA for AS152945, maxLength 48.636 of 636
Route object: none2001:df4:6c0::/48No route object for it. Add a route object with origin AS152945 in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS152945 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.