Same upload speeds

[EasyUp Web Hosting]

Same upload speeds.

I moved today, same complex, only the house next door. Now my Iburst is useless. ;( Can't understand it, it's like 10m and 1/2m (lower) away from where it was.

If I don't come right with something else (internet wise) this coming week, I will get the flat panel antenna.

Edit:
Link Information Link Status Connected
Link Speed 0 / 0 kbps
Frame Error 0.00 % (this jumps around)
Signal Strength 100 %

Total Byte Received 407213 KByte
Total Byte Sent 19481 KByte

C:\Users\(username)>ping www.google.co.za -t

Pinging www.l.google.com [74.125.233.17] with 32 bytes of data:
Reply from 74.125.233.17: bytes=32 time=139ms TTL=50
Reply from 74.125.233.17: bytes=32 time=92ms TTL=50
Reply from 74.125.233.17: bytes=32 time=91ms TTL=50
Reply from 74.125.233.17: bytes=32 time=106ms TTL=50
Reply from 74.125.233.17: bytes=32 time=90ms TTL=50
Reply from 74.125.233.17: bytes=32 time=106ms TTL=50
Reply from 74.125.233.17: bytes=32 time=106ms TTL=50
Reply from 74.125.233.17: bytes=32 time=106ms TTL=50
Reply from 74.125.233.17: bytes=32 time=324ms TTL=50
Reply from 74.125.233.17: bytes=32 time=90ms TTL=50
Reply from 74.125.233.17: bytes=32 time=90ms TTL=50
Reply from 74.125.233.17: bytes=32 time=121ms TTL=50
Reply from 74.125.233.17: bytes=32 time=105ms TTL=50
Reply from 74.125.233.17: bytes=32 time=105ms TTL=50
Reply from 74.125.233.17: bytes=32 time=105ms TTL=50
Reply from 74.125.233.17: bytes=32 time=214ms TTL=50
Reply from 74.125.233.17: bytes=32 time=89ms TTL=50
Reply from 74.125.233.17: bytes=32 time=308ms TTL=50
Reply from 74.125.233.17: bytes=32 time=89ms TTL=50
Reply from 74.125.233.17: bytes=32 time=198ms TTL=50
Reply from 74.125.233.17: bytes=32 time=104ms TTL=50
Reply from 74.125.233.17: bytes=32 time=88ms TTL=50
Reply from 74.125.233.17: bytes=32 time=87ms TTL=50
Reply from 74.125.233.17: bytes=32 time=87ms TTL=50
Reply from 74.125.233.17: bytes=32 time=87ms TTL=50
Reply from 74.125.233.17: bytes=32 time=118ms TTL=50
Reply from 74.125.233.17: bytes=32 time=212ms TTL=50
Reply from 74.125.233.17: bytes=32 time=87ms TTL=50
Reply from 74.125.233.17: bytes=32 time=71ms TTL=50
Reply from 74.125.233.17: bytes=32 time=102ms TTL=50
Reply from 74.125.233.17: bytes=32 time=102ms TTL=50
Reply from 74.125.233.17: bytes=32 time=102ms TTL=50
Reply from 74.125.233.17: bytes=32 time=102ms TTL=50
Reply from 74.125.233.17: bytes=32 time=102ms TTL=50
Reply from 74.125.233.17: bytes=32 time=102ms TTL=50
Reply from 74.125.233.17: bytes=32 time=70ms TTL=50
Reply from 74.125.233.17: bytes=32 time=86ms TTL=50
Reply from 74.125.233.17: bytes=32 time=86ms TTL=50
Reply from 74.125.233.17: bytes=32 time=86ms TTL=50
Reply from 74.125.233.17: bytes=32 time=70ms TTL=50
Reply from 74.125.233.17: bytes=32 time=148ms TTL=50
Reply from 74.125.233.17: bytes=32 time=101ms TTL=50
Reply from 74.125.233.17: bytes=32 time=241ms TTL=50
Reply from 74.125.233.17: bytes=32 time=100ms TTL=50
Reply from 74.125.233.17: bytes=32 time=209ms TTL=50
Reply from 74.125.233.17: bytes=32 time=99ms TTL=50
Reply from 74.125.233.17: bytes=32 time=223ms TTL=50
Reply from 74.125.233.17: bytes=32 time=98ms TTL=50
Reply from 74.125.233.17: bytes=32 time=192ms TTL=50
Reply from 74.125.233.17: bytes=32 time=223ms TTL=50
Reply from 74.125.233.17: bytes=32 time=114ms TTL=50
Reply from 74.125.233.17: bytes=32 time=223ms TTL=50
Request timed out.
Reply from 74.125.233.17: bytes=32 time=198ms TTL=50
Reply from 74.125.233.17: bytes=32 time=57ms TTL=50
Reply from 74.125.233.17: bytes=32 time=151ms TTL=50
Reply from 74.125.233.17: bytes=32 time=73ms TTL=50
Reply from 74.125.233.17: bytes=32 time=88ms TTL=50
Reply from 74.125.233.17: bytes=32 time=119ms TTL=50
Reply from 74.125.233.17: bytes=32 time=197ms TTL=50
Reply from 74.125.233.17: bytes=32 time=213ms TTL=50
Reply from 74.125.233.17: bytes=32 time=103ms TTL=50
Reply from 74.125.233.17: bytes=32 time=102ms TTL=50
Reply from 74.125.233.17: bytes=32 time=211ms TTL=50
Reply from 74.125.233.17: bytes=32 time=85ms TTL=50
Reply from 74.125.233.17: bytes=32 time=116ms TTL=50
Reply from 74.125.233.17: bytes=32 time=115ms TTL=50
Reply from 74.125.233.17: bytes=32 time=99ms TTL=50
Reply from 74.125.233.17: bytes=32 time=114ms TTL=50

 

[EasyUp Web Hosting]

Okay, so my iburst has been useless since I moved and since the cell companies are running nice specials, I thought of changing.

First off, I tested last night with my wife's Nokia C5 and my CellC contract and things didn't go so well. Couldn't even do a speed test.

Then I used her MTN contract and got 1mbps+ down and up and pings of about 70ms, which is better than what I am getting now with iburst. Then i played 2 matches online in COD BO and even though it's not ADSL pings, I at least didn't have any spikes.

I think I still have a VC pre-paid sim at home, so I will test that next.

My point is, these 2GB packages are cheaper than iburst, faster and currently, better for online gaming for me. Yes, they don't have the mid-month topup or r00igev@@r working for them, but that's the way it is...

Thorough testing will follow with nice print screens... Maybe tomorrow.

 

[Cyberbeast]

I would like to see some feedback... because from what I've seen, Cell C is on a downhill path, heading to one massive crash! There are lots of people moaning about poor speeds and no service.

Keep us updated

 

[r00igev@@r]

Keep your iBurst modem in reserve. We are adding a fibre into Centurion and another to the Westrand (scheduled for 20th May if the provider keeps their promise).

We still have loads to do in our pipeline.

BTW: If you visit the IEC nerve centre, after walking past all the Telkom signs, switch on your wifi and see who is there...

http://maps.google.com/maps?f=q&sou...d=8V-6zZrk5qIl6yL9RS-07Q&cbp=12,35.79,,0,-0.9

 

[EasyUp Web Hosting]

I would like to see some feedback... because from what I've seen, Cell C is on a downhill path, heading to one massive crash! There are lots of people moaning about poor speeds and no service.

Keep us updated

Yeah, will start tomorrow with the testing, but can tell you now that CellC had nice pings, but also spiked a lot.

BTW: Nokia C5 3G = HSDPA, 10.2 Mbps; HSUPA, 2 Mbps

Keep your iBurst modem in reserve. We are adding a fibre into Centurion and another to the Westrand (scheduled for 20th May if the provider keeps their promise).

We still have loads to do in our pipeline.

BTW: If you visit the IEC nerve centre, after walking past all the Telkom signs, switch on your wifi and see who is there...

http://maps.google.com/maps?f=q&sou...d=8V-6zZrk5qIl6yL9RS-07Q&cbp=12,35.79,,0,-0.9

LoL dude, I will miss you the most. If I change, that is. I've told you before and I will tell you again, the only wireless solution that I am interested in is Wimax and maybe LTE. LTE sounds to good to be true...

 

[r00igev@@r]

the only wireless solution that I am interested in is Wimax and maybe LTE. LTE sounds to good to be true...

The best wireless technology is next generation iBurst, but no mobile operator will install or fund the towers as it will kill their cash cow in efficiency. They will rather stick with expensive and dated protocols that protect their base in voice.

 

[Jagtiger]

The best wireless technology is next generation iBurst, but no mobile operator will install or fund the towers as it will kill their cash cow in efficiency. They will rather stick with expensive and dated protocols that protect their base in voice.

How fast is it (per user)? What ping for last mile? Weather stability?

 

[EasyUp Web Hosting]

So, iburst is unplayable today, which means I have nothing to do cept for the tests...

1. Iburst

ping -n 20 -l 3200 196.28.69.60

Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 448ms, Maximum = 649ms, Average = 517ms

2. MTN

ping -n 20 -l 3200 196.28.69.60

Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 251ms, Maximum = 492ms, Average = 294ms

3. CellC

ping -n 20 -l 3200 196.28.69.60

Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 175ms, Maximum = 463ms, Average = 265ms

4. Vodacom

ping -n 20 -l 3200 196.28.69.60

Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 413ms, Maximum = 934ms, Average = 614ms

Note that I stay +-1KM away from vodaworld