bgpreport

Network · data from 2026-11-12

AS152966 ALGO-VN - ALGO DATA SERVICES COMPANY LIMITED

Registry name: ALGO-VN - ALGO DATA SERVICES COMPANY LIMITED, VN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS152966, 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.53.50/32 Invalid: maxLength Nonecovered by 160.30.52.0/23 0 0%low visibility 1
160.30.53.51/32 Invalid: maxLength Nonecovered by 160.30.52.0/23 0 0%low visibility 1
160.30.53.52/32 Invalid: maxLength Nonecovered by 160.30.52.0/23 0 0%low visibility 1
2401:42e0::/48 No ROA None 631 99% 68
160.30.52.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
2001:df4:21c0::/48 Valid RIR databaseAPNIC, RADB 635 100% 69

AS-SET

AS152966 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 8 are in fix.csv.

  • ROA: maxLength3
  • ROA: none1
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: maxLength160.30.53.50/32ROA 160.30.52.0/23 AS152966 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 160.30.53.50/32.0 of 673
Route object: none160.30.53.50/32No route object for it. A route object for 160.30.52.0/23 with origin AS152966 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS152966 in the RIR database for the space.0 of 673
ROA: maxLength160.30.53.51/32ROA 160.30.52.0/23 AS152966 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 160.30.53.51/32.0 of 673
Route object: none160.30.53.51/32No route object for it. A route object for 160.30.52.0/23 with origin AS152966 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS152966 in the RIR database for the space.0 of 673
ROA: maxLength160.30.53.52/32ROA 160.30.52.0/23 AS152966 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 160.30.53.52/32.0 of 673
Route object: none160.30.53.52/32No route object for it. A route object for 160.30.52.0/23 with origin AS152966 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS152966 in the RIR database for the space.0 of 673
ROA: none2401:42e0::/48No ROA covers it. Add a ROA for AS152966, maxLength 48.631 of 636
Route object: none2401:42e0::/48No route object for it. Add a route object with origin AS152966 in the RIR database for the space.631 of 636

Route objects not announced

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