bgpreport

Network · data from 2026-11-12

AS206733 Beeks HK

Registry name: BFC-HK Beeks Financial Cloud Ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206733, 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.100.73.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
46.235.37.0/24 No ROA RIR databaseNTTCOM, RADB, RIPE 672 100% 67
46.235.39.0/24 No ROA RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.96.247.0/24 No ROA RIR databaseNTTCOM, RADB, RIPE 655 97% 67
103.100.74.0/24 No ROA RIR databaseAPNIC 510 76% 66

AS-SET

AS206733's PeeringDB record names no 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 9 are in fix.csv.

  • ROA: none5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.100.73.0/24No ROA covers it. Add a ROA for AS206733, maxLength 24.673 of 673
ROA: none46.235.37.0/24No ROA covers it. Add a ROA for AS206733, maxLength 24.672 of 673
ROA: none46.235.39.0/24No ROA covers it. Add a ROA for AS206733, maxLength 24.672 of 673
ROA: none185.96.247.0/24No ROA covers it. Add a ROA for AS206733, maxLength 24.655 of 673
ROA: none103.100.74.0/24No ROA covers it. Add a ROA for AS206733, maxLength 24.510 of 673

Route objects not announced

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

103.73.124.0/24NTTCOM, RADBNo ROA
185.96.244.0/24NTTCOM, RADBNo ROA
185.96.245.0/24NTTCOM, RADBNo ROA
185.96.246.0/24NTTCOM, 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.