Background & Current Setup
I’m located in Rwanda and have been testing FusionHub to bond multiple internet connections while obtaining a static IP address. I initially set up FusionHub on AWS (us-east-1, Virginia) but am experiencing significant performance degradation and considering moving to an on-premise solution.
Performance Test Results
Here are my speed test results showing the dramatic difference:
Direct Connection (SpaceX Starlink):
- Download: 163.84 Mbps
- Upload: 12.83 Mbps
- Ping: 226ms
Through AWS FusionHub (Virginia):
- Download: 65.80 Mbps (60% reduction)
- Upload: 2.40 Mbps (81% reduction)
- Ping: 259ms
My Question
I’m considering deploying FusionHub locally on a Protectli Vault to avoid the geographic routing penalty while still getting the bonding benefits and a public IP. However, I want to understand:
- What kind of performance impact should I expect from an on-premise FusionHub compared to direct internet access?
- Has anyone deployed FusionHub locally in Africa or similar distant regions and can share their experience with speed retention?
- What are the typical overhead percentages you’ve seen with local FusionHub deployments versus cloud-based ones?
- Are there any specific considerations for bonding links through a local FusionHub in terms of hardware requirements or configuration optimizations?
Additional Context
- Primary use case: Reliable internet with static IP for business applications
- Current connections: Multiple ISPs including Starlink
- Location: Rwanda (significant distance from major AWS regions)
- Hardware consideration: Protectli Vault for local FusionHub
Any insights from the community would be greatly appreciated! The AWS performance hit is quite substantial, and I’m hoping a local deployment will give me the reliability benefits of bonding without sacrificing so much throughput.
Thanks in advance for any guidance!