1 reviews | Active since Nov 2015
Webafrica Support Unable to Resolve Real-Time Network Issues – Session ***
Webafrica WhatsApp support technicians appear insufficiently trained to resolve complex connectivity issues, relying primarily on scripted responses.
Issue: I experience severe rubberbanding and jitter, despite stable ICMP ping results and full bandwidth availability. Using PingPlotter, the issue is consistently traced to a Webafrica-managed hop on the route to EU servers, showing ~50% packet loss.
Technicians are instructed to test only download speed and ping. If these two metrics appear normal, no further investigation is offered, even though the problem persists. Escalation beyond basic diagnostics requires a paid technician callout, which is not proportional for diagnosing packet-level issues.
Webafrica has also repeatedly attempted to attribute the problem to TT Connect, despite the affected hop clearly being registered to Webafrica:
inetnum: 168.210.4.0 - 168.210.7.255 netname: WEBAFRICA-03 descr: Delegated to WEBAFRICA on behalf of Dimensiondata AS3741 country: ZA admin-c: WA40-AFRINIC admin-c: JA50-AFRINIC admin-c: FH9-AFRINIC tech-c: WA40-AFRINIC tech-c: JA50-AFRINIC tech-c: FH9-AFRINIC status: ASSIGNED PA remarks: Delegated to WEBAFRICA on behalf of Dimensiondata AS3741 remarks: Send abuse emails to *** mnt-by: TF-***-MNT source: AFRINIC # Filtered parent: 168.209.0.0 - 168.210.255.255
Technical Note: ICMP ping and TCP-based download tests cannot detect intermittent packet loss, jitter, or UDP instability, which are the root causes of rubberbanding. The issue is real-time packet delivery instability on Webafrica’s own upstream infrastructure, not a problem with my local network or the destination server.
