8ta throughput terrible

K

knightfourtwo

Member
Joined
Jul 8, 2010
Messages
22
Reaction score
0
In the last while my 8ta has been performing poorly - not for a lack of signal, but rather due to poor throughput - the following shows what I have come to expect - with a RSSI of -61dBm. Basically the speeds fluctuate a lot, but overall it averages out at terrible.



This is in the Douglasdale area - JHB
 
Boet,That connection is fantastic,your latency is under 100ms which is fantastic for 3G and also that is 0.7 MB/s,change your speedtest settings to show mbps not MBps,that is basically a 7meg adsl line that you gettting
 
sorry my bad,didnt see the zero before the 9.in that case something is not right,your rssi is in the optimum range of -60/-70 and your latency is good.There have been some issues on the IP connects on some networks since Friday,should be resolved by now but wait a couple days to be safe.
 
knightfourtwo said:
In the last while my 8ta has been performing poorly - not for a lack of signal, but rather due to poor throughput - the following shows what I have come to expect - with a RSSI of -61dBm. Basically the speeds fluctuate a lot, but overall it averages out at terrible.



This is in the Douglasdale area - JHB
Click to expand...
Hi knightfourtwo
We would like to investigate.
Please email your 8ta number, contact details and physical address to [email protected].
Please also mention MyBroadband and your username in the subject line.
Thank you
8ta
 
I have sent a mail through with all my details thanks.

As a matter of interest, still having terrible throughput, getting worse...

 
To show how erratic the performance is, I pinged a internal 8ta address and an external mweb address (Which performed exactly the same) with 1024 bytes of data... See the results below. time ranges between 65ms and 9227ms.

ping -w 10000 -l 1024 172.16.2.129 -t

Pinging 172.16.2.129 with 1024 bytes of data:
Reply from 172.16.2.129: bytes=1024 time=4289ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=88ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=1045ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=68ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=136ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=114ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=122ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=120ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=1148ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=98ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=1126ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=9227ms TTL=252
Request timed out.
Reply from 172.16.2.129: bytes=1024 time=2226ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=348ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=345ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=83ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=81ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=129ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=117ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=65ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=233ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=271ms TTL=252
Reply from 172.16.2.129: bytes=1024 time=279ms TTL=252
Request timed out.

Ping statistics for 172.16.2.129:
Packets: Sent = 25, Received = 23, Lost = 2 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 65ms, Maximum = 9227ms, Average = 946ms

ping -w 10000 -l 1024 196.2.45.101 -t

Pinging 196.2.45.101 with 1024 bytes of data:
Reply from 196.2.45.101: bytes=1024 time=4007ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=108ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=1056ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=98ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=106ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=104ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=102ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=100ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=1118ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=158ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=1126ms TTL=52
Request timed out.
Request timed out.
Reply from 196.2.45.101: bytes=1024 time=257ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=105ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=172ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=150ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=188ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=136ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=115ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=133ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=390ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=388ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=516ms TTL=52
Request timed out.

Ping statistics for 196.2.45.101:
Packets: Sent = 25, Received = 22, Lost = 3 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 4007ms, Average = 483ms
 
Similar to my problem (Today is a good day connection wise):
ping -w 10000 -l 1024 196.2.45.101 -t

Pinging 196.2.45.101 with 1024 bytes of data:
Reply from 196.2.45.101: bytes=1024 time=333ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=533ms TTL=52
Request timed out.
Reply from 196.2.45.101: bytes=1024 time=212ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=351ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=1208ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=2260ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=494ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=95ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=1216ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=139ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=117ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=437ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=747ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=265ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=360ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=830ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=928ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=1036ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=188ms TTL=52
Reply from 196.2.45.101: bytes=1024 time=219ms TTL=52

Ping statistics for 196.2.45.101:
Packets: Sent = 21, Received = 20, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 2260ms, Average = 598ms

Keep us posted if 8ta resolves anything for you.
 
Still haven't received any feedback from 8ta from my mail... How long does a guy have to wait to get some service?
 
I conducted a little experiment using 3 different modems and using MDMA, and have some interesting results.

I have 3 modems - zte k3520-z (7.2 HSDPA), huawei e1820 (21 HSPA+), hauwei e367 (21 HSPA+) (Brand new from 8ta).

I ran speedtests, pingtests and played Battlefield 3 using each modem.

When using the ZTE with HSDPA, the latency is generally higher (over 100ms) - but I don't have throughput issues, there are no dark spots where there is no data being transferred, and I can play games no problem. In fact I get the BEST user experience on HSDPA with this device.

When using either of the Huawei modems on HSPA+, I get low latency (under 100ms) but the throughput is terrible, there are spots where no data is being transferred, and online games are unplayable - I cannot play Battlefield with either of these devices on HSPA+ - it keeps having connection issues - and all this with a RSSI of -59dBm on the E367!!

Bottom line - there is an issue with HSPA+ ... It SHOULD be performing better overall.

Tests using the ZTE when the RAT is HSDPA and the RSSI is -73dBm


Test using the E1820 when the RAT is HSPA+ and the RSSI is -75dBm


Test using the E367 when the RAT is HSPA+ and the RSSI is -59dBm!
 
Man i am getting download speeds of 8kbps...i live in a building with an 8ta tower built on top of it, in Paarl. I have contacted 8ta but these people are not replying...
 
Hey there KnightFourtwo

Any response from 8ta yet? I have exactly the same problem. Used to have a proper connection, good signal, and a nice throughput.
That was since I got it in October 2011. The past 6 to 8 weeks, I can't even do my banking, let alone play Battlefield 3... I've tested it with 8ta speedtest and got an average of 0.85mb/s down and 0.16mb/s up. To think I pay for that...
Contacted 8ta through email but haven't received any feedback... Suppose that's a dead-end.

8ta if you follow this thread, my account is [email protected], and I'm fedup wit this!!!!! See you tomorrow!!!
 
BenjaminF said:
Hey there KnightFourtwo

Any response from 8ta yet? I have exactly the same problem. Used to have a proper connection, good signal, and a nice throughput.
That was since I got it in October 2011. The past 6 to 8 weeks, I can't even do my banking, let alone play Battlefield 3... I've tested it with 8ta speedtest and got an average of 0.85mb/s down and 0.16mb/s up. To think I pay for that...
Contacted 8ta through email but haven't received any feedback... Suppose that's a dead-end.

8ta if you follow this thread, my account is [email protected], and I'm fedup wit this!!!!! See you tomorrow!!!
Click to expand...

Hi there

Apologies for the delay in response - we have new staff who need training etc. Please complete the template and we will take this further for you.

Regards,
Social Media Team
 
BenjaminF said:
Hey there KnightFourtwo

Any response from 8ta yet? I have exactly the same problem. Used to have a proper connection, good signal, and a nice throughput.
That was since I got it in October 2011. The past 6 to 8 weeks, I can't even do my banking, let alone play Battlefield 3... I've tested it with 8ta speedtest and got an average of 0.85mb/s down and 0.16mb/s up. To think I pay for that...
Contacted 8ta through email but haven't received any feedback... Suppose that's a dead-end.

8ta if you follow this thread, my account is [email protected], and I'm fedup wit this!!!!! See you tomorrow!!!
Click to expand...

Hi BenjaminF!

We see your query is being dealt with on reference number 1090417. We the technician's report is currently being analyzed and you will be contacted with feedback.

Regards,
Social Media Team
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X