bgpreport

Network · data from 2026-11-12

AS149089 CLOUDFLY-VN - CLOUDFLY CORPORATION

Registry name: CLOUDFLY-VN - CLOUDFLY CORPORATION, VN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149089, 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.82.36.0/22 Valid RIR databaseAPNIC 673 100% 66
103.82.132.0/22 Valid RIR databaseAPNIC 673 100% 66
2407:5b40::/48 Valid RIR databaseAPNIC 636 100% 69
103.82.132.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
103.82.133.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
103.82.134.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS149089 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 16 are in fix.csv.

  • Route object: not announced16

Route objects not announced

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

103.82.36.0/23APNICValid
103.82.36.0/24APNICValid
103.82.37.0/24APNICValid
103.82.38.0/23APNICValid
103.82.38.0/24APNICValid
103.82.39.0/24APNICValid
103.82.132.0/23APNICValid
103.82.134.0/23APNICValid
103.82.135.0/24APNICValid
103.82.192.0/22APNICValid
103.82.192.0/23APNICValid
103.82.192.0/24APNICValid
103.82.193.0/24APNICValid
103.82.194.0/23APNICValid
103.82.194.0/24APNICValid
103.82.195.0/24APNICValid

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.