bgpreport

Network · data from 2026-11-12

AS149625 NETCLOUD1-AS-AP - NETCLOUD INTERNATIONAL DATA CENTRE LIMITED

Registry name: NETCLOUD1-AS-AP - NETCLOUD INTERNATIONAL DATA CENTRE LIMITED, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149625, 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.
103.157.28.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
103.157.29.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67
2001:df5:3280::/48 No ROA RIR databaseAPNIC 635 100% 70

AS-SET

AS149625 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: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none103.157.28.0/24No ROA covers it. Add a ROA for AS149625, maxLength 24.673 of 673
ROA: none103.157.29.0/24No ROA covers it. Add a ROA for AS149625, maxLength 24.671 of 673
ROA: none2001:df5:3280::/48No ROA covers it. Add a ROA for AS149625, maxLength 48.635 of 636

Route objects not announced

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

103.157.28.0/23APNIC, NTTCOM, RADBNo ROA

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.