Neotel Wimax Latency Test requests

M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,474
Reaction score
43
Location
Nice try FBI / I won't say NSA
Hi everyone,

I would like to gauge the quality of the Neotel Wimax offering with regards to latency and throughput.
(Please, no bashing of Neotel etc...just technical facts please).

So, if at all possible, could you perform a couple of test for me if you are using Neotel WImax, I will really appreciate your help.

The tests:
ping 196.38.180.2 -n 20
ping 196.43.22.222 -n 20
www.speedtest.net (closest server and UK server)
www.pingtest.net (closest server)
finally, please do a traceroute to www.microsoft.com and to 196.38.180.2


If you don't want to do all the tests its fine, please just do a www.pingtest.net then.

Thanks in advance.

(Why ? I'm done battling with an ADSL latency of 100-250, telkom can run to the ground for all I care)
 
Pinging 196.38.180.2 with 32 bytes of data:
Reply from 196.38.180.2: bytes=32 time=45ms TTL=56
Reply from 196.38.180.2: bytes=32 time=39ms TTL=56
Reply from 196.38.180.2: bytes=32 time=37ms TTL=56
Reply from 196.38.180.2: bytes=32 time=36ms TTL=56
Reply from 196.38.180.2: bytes=32 time=44ms TTL=56
Reply from 196.38.180.2: bytes=32 time=42ms TTL=56
Reply from 196.38.180.2: bytes=32 time=40ms TTL=56
Reply from 196.38.180.2: bytes=32 time=38ms TTL=56
Reply from 196.38.180.2: bytes=32 time=36ms TTL=56
Reply from 196.38.180.2: bytes=32 time=34ms TTL=56
Reply from 196.38.180.2: bytes=32 time=43ms TTL=56
Reply from 196.38.180.2: bytes=32 time=40ms TTL=56
Reply from 196.38.180.2: bytes=32 time=87ms TTL=56
Reply from 196.38.180.2: bytes=32 time=35ms TTL=56
Reply from 196.38.180.2: bytes=32 time=34ms TTL=56
Reply from 196.38.180.2: bytes=32 time=93ms TTL=56
Reply from 196.38.180.2: bytes=32 time=39ms TTL=56
Reply from 196.38.180.2: bytes=32 time=37ms TTL=56
Reply from 196.38.180.2: bytes=32 time=93ms TTL=56
Reply from 196.38.180.2: bytes=32 time=43ms TTL=56

Ping statistics for 196.38.180.2:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 93ms, Average = 46ms




Pinging 196.43.22.222 with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=40ms TTL=245
Reply from 196.43.22.222: bytes=32 time=39ms TTL=245
Reply from 196.43.22.222: bytes=32 time=39ms TTL=245
Reply from 196.43.22.222: bytes=32 time=41ms TTL=245
Reply from 196.43.22.222: bytes=32 time=46ms TTL=245
Reply from 196.43.22.222: bytes=32 time=43ms TTL=245
Reply from 196.43.22.222: bytes=32 time=39ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=35ms TTL=245
Reply from 196.43.22.222: bytes=32 time=43ms TTL=245
Reply from 196.43.22.222: bytes=32 time=41ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=35ms TTL=245
Reply from 196.43.22.222: bytes=32 time=43ms TTL=245
Reply from 196.43.22.222: bytes=32 time=41ms TTL=245
Reply from 196.43.22.222: bytes=32 time=39ms TTL=245
Reply from 196.43.22.222: bytes=32 time=39ms TTL=245
Reply from 196.43.22.222: bytes=32 time=44ms TTL=245
Reply from 196.43.22.222: bytes=32 time=44ms TTL=245
Reply from 196.43.22.222: bytes=32 time=41ms TTL=245

Ping statistics for 196.43.22.222:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 46ms, Average = 40ms

http://www.speedtest.net/result/964101800.png

http://www.speedtest.net/result/964102895.png

http://www.pingtest.net/result/24658287.png
 
Can someone link me to this Neotel Wimax option that the tests are being run for.
 
Recently converted to Wimax from Neoflex (I'm impressed)

http://www.speedtest.net/result/981987554.png
http://www.speedtest.net/result/981990881.png
http://www.pingtest.net/result/25610192.png

Usage experience:
1. Apple TV
  • Trailers play immediately; previously neoflex would take up to 15 minutes to cache.
  • Youtube 10 min videos load immediately; previously slow to cache with inconsistent streaming.
  • Movie rentals take +-5 minutes before play; previously > 40 mins.
2. Download / Internet
  • No complaints so far, not sure how this compares to DSL but for me this has been a big improvement on the CDMA Neoflex technology.
  • With Speed tests, the needle goes up to the top speed and sticks there for the duration; with Neoflex it would constantly jump around (good, bad, terrible, excellent, ....)

Thanks Neotel, you've got a happy customer. Note: Before you comment about Neotel keep in mind that I have been a Neoflex customer for the past 20 months, yes I have lived through the good :D to extremely bad times :mad:, and back to acceptable times :sick: (most likely due to the loss of customers)

For those that have Neoflex I suggest you at least try Wimax as an option, who knows? like me you might be pleasantly surprised.


Results for Mr Jax:

PING 196.38.180.2 (196.38.180.2): 56 data bytes
64 bytes from 196.38.180.2: icmp_seq=0 ttl=56 time=38.720 ms
64 bytes from 196.38.180.2: icmp_seq=1 ttl=56 time=38.261 ms
64 bytes from 196.38.180.2: icmp_seq=2 ttl=56 time=38.838 ms
64 bytes from 196.38.180.2: icmp_seq=3 ttl=56 time=37.760 ms
64 bytes from 196.38.180.2: icmp_seq=4 ttl=56 time=37.354 ms
64 bytes from 196.38.180.2: icmp_seq=5 ttl=56 time=37.679 ms
64 bytes from 196.38.180.2: icmp_seq=6 ttl=56 time=40.036 ms
64 bytes from 196.38.180.2: icmp_seq=7 ttl=56 time=37.095 ms
64 bytes from 196.38.180.2: icmp_seq=8 ttl=56 time=37.693 ms
64 bytes from 196.38.180.2: icmp_seq=9 ttl=56 time=37.404 ms
64 bytes from 196.38.180.2: icmp_seq=10 ttl=56 time=36.887 ms
64 bytes from 196.38.180.2: icmp_seq=11 ttl=56 time=35.316 ms
64 bytes from 196.38.180.2: icmp_seq=12 ttl=56 time=35.812 ms
64 bytes from 196.38.180.2: icmp_seq=13 ttl=56 time=35.412 ms
64 bytes from 196.38.180.2: icmp_seq=14 ttl=56 time=34.462 ms
64 bytes from 196.38.180.2: icmp_seq=15 ttl=56 time=44.302 ms
64 bytes from 196.38.180.2: icmp_seq=16 ttl=56 time=34.779 ms
64 bytes from 196.38.180.2: icmp_seq=17 ttl=56 time=44.406 ms
64 bytes from 196.38.180.2: icmp_seq=18 ttl=56 time=34.287 ms
64 bytes from 196.38.180.2: icmp_seq=19 ttl=56 time=35.992 ms

--- 196.38.180.2 ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 34.287/37.625/44.406/2.701 ms


PING 196.43.22.222 (196.43.22.222): 56 data bytes
64 bytes from 196.43.22.222: icmp_seq=0 ttl=245 time=35.722 ms
64 bytes from 196.43.22.222: icmp_seq=1 ttl=245 time=36.106 ms
64 bytes from 196.43.22.222: icmp_seq=2 ttl=245 time=37.883 ms
64 bytes from 196.43.22.222: icmp_seq=3 ttl=245 time=36.747 ms
64 bytes from 196.43.22.222: icmp_seq=4 ttl=245 time=35.228 ms
64 bytes from 196.43.22.222: icmp_seq=5 ttl=245 time=64.379 ms
64 bytes from 196.43.22.222: icmp_seq=6 ttl=245 time=44.037 ms
64 bytes from 196.43.22.222: icmp_seq=7 ttl=245 time=43.729 ms
64 bytes from 196.43.22.222: icmp_seq=8 ttl=245 time=44.364 ms
64 bytes from 196.43.22.222: icmp_seq=9 ttl=245 time=43.308 ms
64 bytes from 196.43.22.222: icmp_seq=10 ttl=245 time=83.030 ms
64 bytes from 196.43.22.222: icmp_seq=11 ttl=245 time=43.122 ms
64 bytes from 196.43.22.222: icmp_seq=12 ttl=245 time=42.519 ms
64 bytes from 196.43.22.222: icmp_seq=13 ttl=245 time=42.046 ms
64 bytes from 196.43.22.222: icmp_seq=14 ttl=245 time=42.369 ms
64 bytes from 196.43.22.222: icmp_seq=15 ttl=245 time=42.683 ms
64 bytes from 196.43.22.222: icmp_seq=16 ttl=245 time=45.879 ms
64 bytes from 196.43.22.222: icmp_seq=17 ttl=245 time=45.271 ms
64 bytes from 196.43.22.222: icmp_seq=18 ttl=245 time=42.339 ms
64 bytes from 196.43.22.222: icmp_seq=19 ttl=245 time=44.643 ms

--- 196.43.22.222 ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 35.228/44.770/83.030/10.594 ms

traceroute to 196.38.180.2 (196.38.180.2), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 2.255 ms 0.692 ms 0.508 ms
2 41.160.160.2 (41.160.160.2) 28.064 ms 39.531 ms 30.087 ms
3 41.160.0.242 (41.160.0.242) 39.730 ms 29.198 ms 40.017 ms
4 is.jinx.net.za (198.32.142.10) 39.954 ms 38.828 ms 81.837 ms
5 168.209.1.139 (168.209.1.139) 38.857 ms
196.26.0.60 (196.26.0.60) 36.671 ms
168.209.1.139 (168.209.1.139) 41.316 ms
6 168.209.100.242 (168.209.100.242) 41.248 ms 39.344 ms 40.715 ms
7 168.209.217.22 (168.209.217.22) 38.526 ms
168.209.218.22 (168.209.218.22) 38.565 ms 37.607 ms
8 control.isgaming.co.za (196.38.180.2) 40.201 ms 39.182 ms 39.811 ms
 
Last edited:
Surprisingly stable..Not the best call centre experiences though..Im sure enough has been posted on that topic

PING 196.43.22.222 (196.43.22.222) 56(84) bytes of data.
64 bytes from 196.43.22.222: icmp_seq=0 ttl=237 time=25.2 ms
64 bytes from 196.43.22.222: icmp_seq=1 ttl=237 time=24.4 ms
64 bytes from 196.43.22.222: icmp_seq=2 ttl=237 time=24.4 ms
64 bytes from 196.43.22.222: icmp_seq=3 ttl=237 time=24.7 ms
64 bytes from 196.43.22.222: icmp_seq=4 ttl=237 time=24.6 ms
64 bytes from 196.43.22.222: icmp_seq=5 ttl=237 time=24.6 ms
64 bytes from 196.43.22.222: icmp_seq=6 ttl=237 time=24.2 ms
64 bytes from 196.43.22.222: icmp_seq=7 ttl=237 time=28.3 ms
64 bytes from 196.43.22.222: icmp_seq=8 ttl=237 time=25.4 ms
64 bytes from 196.43.22.222: icmp_seq=9 ttl=237 time=24.4 ms
64 bytes from 196.43.22.222: icmp_seq=10 ttl=237 time=24.4 ms
64 bytes from 196.43.22.222: icmp_seq=11 ttl=237 time=24.6 ms
64 bytes from 196.43.22.222: icmp_seq=12 ttl=237 time=24.3 ms
64 bytes from 196.43.22.222: icmp_seq=13 ttl=237 time=24.2 ms
64 bytes from 196.43.22.222: icmp_seq=14 ttl=237 time=23.9 ms
64 bytes from 196.43.22.222: icmp_seq=15 ttl=237 time=24.1 ms


PING 196.38.180.2 (196.38.180.2) 56(84) bytes of data.
64 bytes from 196.38.180.2: icmp_seq=0 ttl=47 time=22.3 ms
64 bytes from 196.38.180.2: icmp_seq=1 ttl=47 time=22.1 ms
64 bytes from 196.38.180.2: icmp_seq=2 ttl=47 time=21.4 ms
64 bytes from 196.38.180.2: icmp_seq=3 ttl=47 time=21.6 ms
64 bytes from 196.38.180.2: icmp_seq=4 ttl=47 time=21.8 ms
64 bytes from 196.38.180.2: icmp_seq=5 ttl=47 time=21.4 ms
64 bytes from 196.38.180.2: icmp_seq=6 ttl=47 time=22.4 ms
64 bytes from 196.38.180.2: icmp_seq=7 ttl=47 time=23.0 ms
64 bytes from 196.38.180.2: icmp_seq=8 ttl=47 time=22.4 ms
64 bytes from 196.38.180.2: icmp_seq=9 ttl=47 time=21.7 ms
64 bytes from 196.38.180.2: icmp_seq=10 ttl=47 time=22.0 ms
 
Those latencies are lovely to the isgaming website. Wish that it was slightly cheaper. I would cancel Telkom and ISP and buy:(
 
I spoke to a few guys now.

Apprently they do offer Neobroadband WiMax for home users, but its not marketed yet. Costing is R1000pm 1mb solution. I just need to findout how much installation costs as well as latencies throughout the day
 
jpmonster said:
I spoke to a few guys now.

Apprently they do offer Neobroadband WiMax for home users, but its not marketed yet. Costing is R1000pm 1mb solution. I just need to findout how much installation costs as well as latencies throughout the day
Click to expand...

Great news, please keep us updated! (the other offerings are unfortunately also too rich for my pocket :( )
 
Guys can we please get more latency tests. Mainly for the 1mb solution. Can you guys ping 196.38.180.45 -t after 8:30 and keep it running for 1minute maybe.

My line has been lagging after 7pm for the last 2 months, kinda over it. Spend more or less R1100 pm on 4mb+uncapped.
 
Confirmed the pricing for Home Users.

It is R1299 Vat Inclusive for 1mbps/uncapped/unshaped/ R1500 Installation Cost once off

0801111636 for site survey.

I just need to know how latencies are.
 
Generally I get between 40-70ms, but after 7:30pm i get about 200ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X