PaulB_
Senior Member
Hi all, I posted this already in the Afrihost forum - but posting it again here, as this also involves Mweb - and I feel people with Mweb should also see this.
I’ve always noticed that streaming and other long-lived connections have been somewhat inconsistent over Afrihost, and others on this network have shared similar experiences. Because of that, I decided to dig into it a bit more, especially since I’ve consistently found Mweb to perform noticeably better in this regard.
For context, I’m based at a school where there is a shared Afrihost fibre line (1 Gbps). I also have my own separate Mweb fibre line (50 Mbps), which I originally installed before the Afrihost service was rolled out to the residences. I’ve kept the Mweb line due to consistently better performance, and have now started comparing the two more formally.
Lines:
Despite the large difference in available bandwidth, the Mweb line is consistently delivering a more stable experience to European-hosted services.
I’ve been running a sustained stream test (~25 minutes so far) to a server in Germany (152.53.124.56), and:
Traceroute comparison:
Afrihost:
<span>Cape Town → Liquid Telecom → EU<br>hu-0-0-0-11.luk-p1-gsw.liquidtelecom.net (~150ms entry)<br>→ some variation (~150–178ms) across EU hops</span>
Mweb:
<span>Cape Town → local backbone → EU<br>→ stabilises more quickly (~160–170ms)</span>
Takeaway:
The Afrihost route (via Liquid Telecom) appears to introduce more latency variation (jitter) once traffic reaches Europe, whereas Mweb’s path seems more consistent even at lower throughput.
This shows up in real-world usage as:
Questions:
Thanks
Quick update:
I’ve now been streaming a ~15GB 4K file from the same German server over the Mweb line for ~25 minutes with zero buffering.
Under the same conditions on Afrihost, playback becomes inconsistent with buffering.
This reinforces that the issue seems to be route stability rather than bandwidth.
I’ve always noticed that streaming and other long-lived connections have been somewhat inconsistent over Afrihost, and others on this network have shared similar experiences. Because of that, I decided to dig into it a bit more, especially since I’ve consistently found Mweb to perform noticeably better in this regard.
For context, I’m based at a school where there is a shared Afrihost fibre line (1 Gbps). I also have my own separate Mweb fibre line (50 Mbps), which I originally installed before the Afrihost service was rolled out to the residences. I’ve kept the Mweb line due to consistently better performance, and have now started comparing the two more formally.
Lines:
- Afrihost (1 Gbps, typically 300–400 Mbps throughput)
- Mweb (50 Mbps)
Despite the large difference in available bandwidth, the Mweb line is consistently delivering a more stable experience to European-hosted services.
I’ve been running a sustained stream test (~25 minutes so far) to a server in Germany (152.53.124.56), and:
- Mweb: stable playback throughout, no interruptions
- Afrihost: noticeably less consistent under the same conditions, with buffering occurring to the point where playback becomes difficult to sustain
- ~18–20 ms
- no packet loss
- minimal jitter
Traceroute comparison:
Afrihost:
<span>Cape Town → Liquid Telecom → EU<br>hu-0-0-0-11.luk-p1-gsw.liquidtelecom.net (~150ms entry)<br>→ some variation (~150–178ms) across EU hops</span>
Mweb:
<span>Cape Town → local backbone → EU<br>→ stabilises more quickly (~160–170ms)</span>
Takeaway:
The Afrihost route (via Liquid Telecom) appears to introduce more latency variation (jitter) once traffic reaches Europe, whereas Mweb’s path seems more consistent even at lower throughput.
This shows up in real-world usage as:
- Afrihost: higher speed but less consistent performance to EU
- Mweb: lower speed but more stable session behaviour
Questions:
- Is anyone else seeing similar behaviour with Afrihost international routing (EU specifically)?
- Could this be related to upstream/transit via Liquid Telecom?
- Any possibility of alternative routing or peering paths being used/considered?
Thanks
Quick update:
I’ve now been streaming a ~15GB 4K file from the same German server over the Mweb line for ~25 minutes with zero buffering.
Under the same conditions on Afrihost, playback becomes inconsistent with buffering.
This reinforces that the issue seems to be route stability rather than bandwidth.