Current IBurst Speeds - 15 Dec 2004

[Bishop]

Since a lot of people are asking for it, both in private mail to me and on the forum, I ran some quick tests last night. I am in Douglasdale, connecting to the Bryanston tower ( I think, there is no way to tell for sure that I know of ).

Local ping
----------
ping -n 20 196.43.10.86

Pinging 196.43.10.86 with 32 bytes of data:

Reply from 196.43.10.86: bytes=32 time=66ms TTL=248
Reply from 196.43.10.86: bytes=32 time=64ms TTL=248
Reply from 196.43.10.86: bytes=32 time=76ms TTL=248
Reply from 196.43.10.86: bytes=32 time=82ms TTL=248
Reply from 196.43.10.86: bytes=32 time=78ms TTL=248
Reply from 196.43.10.86: bytes=32 time=73ms TTL=248
Reply from 196.43.10.86: bytes=32 time=70ms TTL=248
Reply from 196.43.10.86: bytes=32 time=64ms TTL=248
Reply from 196.43.10.86: bytes=32 time=66ms TTL=248
Reply from 196.43.10.86: bytes=32 time=69ms TTL=248
Reply from 196.43.10.86: bytes=32 time=68ms TTL=248
Reply from 196.43.10.86: bytes=32 time=62ms TTL=248
Reply from 196.43.10.86: bytes=32 time=63ms TTL=248
Reply from 196.43.10.86: bytes=32 time=66ms TTL=248
Reply from 196.43.10.86: bytes=32 time=65ms TTL=248
Reply from 196.43.10.86: bytes=32 time=64ms TTL=248
Reply from 196.43.10.86: bytes=32 time=63ms TTL=248
Reply from 196.43.10.86: bytes=32 time=94ms TTL=248
Reply from 196.43.10.86: bytes=32 time=74ms TTL=248
Reply from 196.43.10.86: bytes=32 time=75ms TTL=248

Ping statistics for 196.43.10.86:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 94ms, Average = 70ms

International ping
-----------------
ping -n 20 www.blizzard.net

Pinging blizzard.net [64.202.167.129] with 32 bytes of data:

Reply from 64.202.167.129: bytes=32 time=350ms TTL=106
Reply from 64.202.167.129: bytes=32 time=373ms TTL=106
Reply from 64.202.167.129: bytes=32 time=361ms TTL=106
Reply from 64.202.167.129: bytes=32 time=360ms TTL=106
Reply from 64.202.167.129: bytes=32 time=359ms TTL=106
Reply from 64.202.167.129: bytes=32 time=387ms TTL=106
Reply from 64.202.167.129: bytes=32 time=367ms TTL=106
Reply from 64.202.167.129: bytes=32 time=361ms TTL=106
Reply from 64.202.167.129: bytes=32 time=336ms TTL=106
Reply from 64.202.167.129: bytes=32 time=439ms TTL=106
Reply from 64.202.167.129: bytes=32 time=358ms TTL=106
Reply from 64.202.167.129: bytes=32 time=356ms TTL=106
Reply from 64.202.167.129: bytes=32 time=361ms TTL=106
Reply from 64.202.167.129: bytes=32 time=404ms TTL=106
Reply from 64.202.167.129: bytes=32 time=373ms TTL=106
Reply from 64.202.167.129: bytes=32 time=398ms TTL=106
Reply from 64.202.167.129: bytes=32 time=352ms TTL=106
Reply from 64.202.167.129: bytes=32 time=372ms TTL=106
Reply from 64.202.167.129: bytes=32 time=364ms TTL=106
Reply from 64.202.167.129: bytes=32 time=369ms TTL=106

Ping statistics for 64.202.167.129:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:
Minimum = 336ms, Maximum = 439ms, Average = 370ms

MyAdsl Local Speed test
------------------
28.8 kbps dial-up
33.6 kbps dial-up
53.3 kbps dial-up
56 kbps ISDN
128 kbps ISDN
384 kbps DSL
768 kbps DSL
868.7 kbps YOU
1000 kbps DSL
1500 kbps DSL/T1/Cable Modem


International Speed test
-----------------------
TCP/Web100 Network Diagnostic Tool v5.2.1e
click START to begin
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 100.31Kb/s running 10s inbound test (server to client) . . . . . . 388.67kb/s Your PC is connected to a Cable/DSL modem
Information: Other network traffic is congesting the link

click START to re-test

Current Status
--------------
Very Happy!

 

[TheYak]

Also very happy wrt speeds here.

What I have noticed though, is that every now and again, my connection slows down, and I have to disconnect and reconnect to get it working again. I run the connection from an SMC BarricadeG wireless access point.

Anyone else getting the slowdown problem?

Usually after I reconnect, it's fine again.

 

[ic]

[u]ping -n 20 196.43.10.86[/u]

Pinging 196.43.10.86 with 32 bytes of data:

Reply from 196.43.10.86: bytes=32 time=80ms TTL=248
Reply from 196.43.10.86: bytes=32 time=150ms TTL=248
Reply from 196.43.10.86: bytes=32 time=190ms TTL=248
Reply from 196.43.10.86: bytes=32 time=131ms TTL=248
Reply from 196.43.10.86: bytes=32 time=90ms TTL=248
Reply from 196.43.10.86: bytes=32 time=70ms TTL=248
Reply from 196.43.10.86: bytes=32 time=190ms TTL=248
Reply from 196.43.10.86: bytes=32 time=100ms TTL=248
Reply from 196.43.10.86: bytes=32 time=50ms TTL=248
Reply from 196.43.10.86: bytes=32 time=150ms TTL=248
Reply from 196.43.10.86: bytes=32 time=220ms TTL=248
Reply from 196.43.10.86: bytes=32 time=130ms TTL=248
Reply from 196.43.10.86: bytes=32 time=71ms TTL=248
Reply from 196.43.10.86: bytes=32 time=240ms TTL=248
Reply from 196.43.10.86: bytes=32 time=141ms TTL=248
Reply from 196.43.10.86: bytes=32 time=210ms TTL=248
Reply from 196.43.10.86: bytes=32 time=431ms TTL=248
Reply from 196.43.10.86: bytes=32 time=90ms TTL=248
Reply from 196.43.10.86: bytes=32 time=120ms TTL=248
Reply from 196.43.10.86: bytes=32 time=110ms TTL=248

Ping statistics for 196.43.10.86:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum =  431ms, Average =  148ms

[u]ping -n 20 [url]www.blizzard[/url][/u]

Pinging blizzard.net [64.202.167.129] with 32 bytes of data:

Reply from 64.202.167.129: bytes=32 time=360ms TTL=107
Reply from 64.202.167.129: bytes=32 time=411ms TTL=107
Reply from 64.202.167.129: bytes=32 time=721ms TTL=107
Reply from 64.202.167.129: bytes=32 time=651ms TTL=107
Reply from 64.202.167.129: bytes=32 time=360ms TTL=107
Reply from 64.202.167.129: bytes=32 time=361ms TTL=107
Reply from 64.202.167.129: bytes=32 time=370ms TTL=107
Reply from 64.202.167.129: bytes=32 time=381ms TTL=107
Reply from 64.202.167.129: bytes=32 time=400ms TTL=107
Reply from 64.202.167.129: bytes=32 time=541ms TTL=107
Reply from 64.202.167.129: bytes=32 time=401ms TTL=107
Reply from 64.202.167.129: bytes=32 time=410ms TTL=107
Reply from 64.202.167.129: bytes=32 time=601ms TTL=107
Reply from 64.202.167.129: bytes=32 time=490ms TTL=107
Reply from 64.202.167.129: bytes=32 time=441ms TTL=107
Reply from 64.202.167.129: bytes=32 time=510ms TTL=107
Reply from 64.202.167.129: bytes=32 time=471ms TTL=107
Reply from 64.202.167.129: bytes=32 time=520ms TTL=107
Reply from 64.202.167.129: bytes=32 time=431ms TTL=107
Reply from 64.202.167.129: bytes=32 time=641ms TTL=107

Ping statistics for 64.202.167.129:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 360ms, Maximum =  721ms, Average =  473ms

[u]MyADSL Local (South African) Speed Test[/u]
Your current bandwidth reading is:
389.30kbps
which means you can download at 48.66 KB/sec. from our servers.
[b]This was the best of 5 with cache cleared & set to 0 in FireFox[/b]

[u]MyADSL International Text Based Speed Test[/u]
Download start time: 	1103115281527
Download end time: 	1103115289789
Download time: 	8.262
Download size in thousands of bytes: 	50
Throughput in Kilobits per Second: 	49.4
Throughput in Kilobytes per Second:  	6.1

 

[alchamy]

Also very happy wrt speeds here.

What I have noticed though, is that every now and again, my connection slows down, and I have to disconnect and reconnect to get it working again. I run the connection from an SMC BarricadeG wireless access point.

Anyone else getting the slowdown problem?

Usually after I reconnect, it's fine again.

Yeah, also noticed the slowdown issue, quite annoying really. I'm using an Asus WL-500g running Oleg's Custom Firmware and Busybox.

I have configured Cron to reboot the box at midnight. Ofcourse thats the advantage of Linux Embedded routers.

I have also noticed that my routers WAN port hangs on occasion, which is unique to my Iburst modem being plugged into it. Once again the scheduled reboot minimises irritation. (I think its got to do with the log files getting too big)