bgpreport

Network · data from 2026-11-12

AS214053 CLUSTERFAST-AS ClusterFast Network Limited

Registry name: CLUSTERFAST-AS ClusterFast Network Limited, HK · not in PeeringDB

1IPv4 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
0Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS214053, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS214053, 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.
206.206.100.0/24 Valid Other IRR onlyRADB 671 100% 68
2a0e:aa07:ec10::/44 Valid RIR databaseRADB, RIPE 636 100% 67

AS-SET

AS214053 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 17 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
Route object: RIR206.206.100.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

2a0e:aa07:ec10::/48RIPEValid
2a0e:aa07:ec11::/48RIPEValid
2a0e:aa07:ec12::/48RIPEValid
2a0e:aa07:ec13::/48RIPEValid
2a0e:aa07:ec14::/48RIPEValid
2a0e:aa07:ec15::/48RIPEValid
2a0e:aa07:ec16::/48RIPEValid
2a0e:aa07:ec17::/48RIPEValid
2a0e:aa07:ec18::/48RIPEValid
2a0e:aa07:ec19::/48RIPEValid
2a0e:aa07:ec1a::/48RIPEValid
2a0e:aa07:ec1b::/48RIPEValid
2a0e:aa07:ec1c::/48RIPEValid
2a0e:aa07:ec1d::/48RIPEValid
2a0e:aa07:ec1e::/48RIPEValid
2a0e:aa07:ec1f::/48RIPEValid

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.