Broadband pings/download speed.

jonski

Originally posted by Texta
Could anyone post pings d/l speeds for UTV Clicksilver

sorry about the delay

using clicksliver


C:\>ping www.boards.ie

Pinging www.boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=72ms TTL=53
Reply from 217.114.166.147: bytes=32 time=77ms TTL=53
Reply from 217.114.166.147: bytes=32 time=77ms TTL=53
Reply from 217.114.166.147: bytes=32 time=77ms TTL=53

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 77ms, Average = 75ms

C:\>ping clarity.jolt.co.uk

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=60ms TTL=56
Reply from 195.149.21.11: bytes=32 time=62ms TTL=56
Reply from 195.149.21.11: bytes=32 time=62ms TTL=56
Reply from 195.149.21.11: bytes=32 time=62ms TTL=56

Ping statistics for 195.149.21.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 62ms, Average = 61ms

C:\>

BKtje

Finally get to add my pings to this thread

Product: Esat Business
Speed: 512/256
Downtime: none (have had 6 hrs )

Download speeds 63kb/s and upload at 32.5 or so.

Jolt:
Reply from 195.149.21.11: bytes=32 time=20ms TTL=57
Reply from 195.149.21.11: bytes=32 time=20ms TTL=57
Reply from 195.149.21.11: bytes=32 time=20ms TTL=57
Reply from 195.149.21.11: bytes=32 time=20ms TTL=57

Boards:
Reply from 217.114.166.147: bytes=32 time=10ms TTL=55
Reply from 217.114.166.147: bytes=32 time=10ms TTL=55
Reply from 217.114.166.147: bytes=32 time=10ms TTL=55
Reply from 217.114.166.147: bytes=32 time=10ms TTL=55

German:
Reply from 62.26.219.41: bytes=32 time=40ms TTL=54
Reply from 62.26.219.41: bytes=32 time=30ms TTL=54
Reply from 62.26.219.41: bytes=32 time=30ms TTL=54
Reply from 62.26.219.41: bytes=32 time=50ms TTL=54

melachi

BK GIMME THAT YOU DIRTY BASTIGE!

BKtje

hehe mel.

The above is misleading, thats what my ping should be at (and is after 7) but the Esat routers are at 90% capacity to the UK or something so during the day i ping closer to 90. They gonna fix it tho. (or so ronin says )
Downloads still top notch tho

BKtje

lol and they back down to 20ms again.

bit of a yoyo atm

steve-hosting36

Esat BT seem to be scoring the best on this;

Jolt
Reply from 195.149.21.11: bytes=32 time=19ms TTL=57
Reply from 195.149.21.11: bytes=32 time=20ms TTL=57
Reply from 195.149.21.11: bytes=32 time=19ms TTL=57
Reply from 195.149.21.11: bytes=32 time=19ms TTL=57

German
Reply from 62.26.219.41: bytes=32 time=35ms TTL=50
Reply from 62.26.219.41: bytes=32 time=35ms TTL=50
Reply from 62.26.219.41: bytes=32 time=34ms TTL=50
Reply from 62.26.219.41: bytes=32 time=35ms TTL=50

Boards
Doesnt count (too close)

I've not seen much better than Esats performance, is Esat/IOL the best gamers provider?!

sReq | uTeK

B-K my Esat/bt business is guna ownz urS

come on and install mine B-k what we regd about a week in the difference hopefully so I will have mine also by monday * The reality hits me and I notice this thing called fact and fiction *


:rolleyes:

sReq | uTeK

I finally get to ****ing post here

EsatBt Business
512/256

Waiting 3 weeks to get installed.

Pinging www.boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=14ms TTL=55
Reply from 217.114.166.147: bytes=32 time=15ms TTL=55
Reply from 217.114.166.147: bytes=32 time=14ms TTL=55
Reply from 217.114.166.147: bytes=32 time=15ms TTL=55

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 15ms, Average = 14ms

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=23ms TTL=57
Reply from 195.149.21.11: bytes=32 time=23ms TTL=57
Reply from 195.149.21.11: bytes=32 time=24ms TTL=57
Reply from 195.149.21.11: bytes=32 time=24ms TTL=57

Ping statistics for 195.149.21.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 24ms, Average = 23ms

Hrmm in game pings are anything between 30-40 at the mo to the uk this is because their routers are at 90 % effecency at the mo and all the businesses are running should drop down to about 10-20 after 6 pretty much the same as b-k

logic

Is Netsource still really bad for ping times.....the only reason I want to go with them is the no cap. Cant have wireless either.

ozmo

Originally posted by Mutant_Fruit
my packets see exactly 0 milimetres of copper on their trip. First it goes through about 7 metres of cat5 cable (i assume cat5 isn't made of copper... i may be wrong though),

Well - yes Cat5 is copper. But 7m isnt going to make any difference. Its the plugs on each end that can though if they are loose or dirty. And they are made of stuff less conductive (ie. worse) than copper (copper is too soft for terminals).
But dsl is designed (very well actually) to work over a very long length of copper. (local lan, over similar cable only goes about 200 meters if you are lucky)
ozmo.

LumoColor

Originally posted by logic
Is Netsource still really bad for ping times.....the only reason I want to go with them is the no cap. Cant have wireless either.

Last few nights have been ok till later on, Tuesday bad pings started around 10pm, Wednesday started about 9pm. This could be people's usage pattern's or them playing with the network, you will never get a straight answer from them on whats happening.

It also depends on what you want to do:-

If you want to play games online, then my advise would be to stay away until they can finally resolve the issues. And that dont mean a temporary 1 month fix like we had at the start of July.

When Netsource is good, its very very good. When its bad, might as well use a 56k modem.

Current bout of problems are not effecting downloads tho, so If you want to download tons of stuff on kazza ect, then Netsource is for you untill you get Throttled for d/loading too much circa 20gb/month from what people have been posting. Hope your not on my exchange tho

nxbyveromdwjpg

Leap Broadband, 1mb (bus3)

C:\>ping www.boards.ie

Pinging www.boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=52ms TTL=55
Reply from 217.114.166.147: bytes=32 time=70ms TTL=55
Reply from 217.114.166.147: bytes=32 time=50ms TTL=55
Reply from 217.114.166.147: bytes=32 time=50ms TTL=55

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 70ms, Average = 55ms

C:\>ping www.jolt.co.uk

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=127ms TTL=55
Reply from 195.149.21.11: bytes=32 time=125ms TTL=55
Reply from 195.149.21.11: bytes=32 time=125ms TTL=55
Reply from 195.149.21.11: bytes=32 time=130ms TTL=55

Ping statistics for 195.149.21.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 130ms, Average = 126ms

Coolermaster

Eircom i-stream starter with Draytek Vigor 2600we

C:\>ping boards.ie

Pinging boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=31ms TTL=53
Reply from 217.114.166.147: bytes=32 time=32ms TTL=53
Reply from 217.114.166.147: bytes=32 time=32ms TTL=53

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 47ms, Average = 35ms

C:\>ping www.jolt.co.uk

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=47ms TTL=57
Reply from 195.149.21.11: bytes=32 time=31ms TTL=57
Reply from 195.149.21.11: bytes=32 time=31ms TTL=57
Reply from 195.149.21.11: bytes=32 time=32ms TTL=57

Ping statistics for 195.149.21.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 47ms, Average = 35ms

Kevok

IBB 1meg Res - 3-rock Tower

Jolt:

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=25ms TTL=55
Reply from 195.149.21.11: bytes=32 time=21ms TTL=55
Reply from 195.149.21.11: bytes=32 time=28ms TTL=55
Reply from 195.149.21.11: bytes=32 time=31ms TTL=55
Reply from 195.149.21.11: bytes=32 time=23ms TTL=55
Reply from 195.149.21.11: bytes=32 time=34ms TTL=55
Reply from 195.149.21.11: bytes=32 time=26ms TTL=55
Reply from 195.149.21.11: bytes=32 time=36ms TTL=55
Reply from 195.149.21.11: bytes=32 time=23ms TTL=55
Reply from 195.149.21.11: bytes=32 time=33ms TTL=55
Reply from 195.149.21.11: bytes=32 time=33ms TTL=55
Reply from 195.149.21.11: bytes=32 time=23ms TTL=55
Reply from 195.149.21.11: bytes=32 time=22ms TTL=55
Reply from 195.149.21.11: bytes=32 time=26ms TTL=55
Reply from 195.149.21.11: bytes=32 time=28ms TTL=55
Reply from 195.149.21.11: bytes=32 time=24ms TTL=55
Reply from 195.149.21.11: bytes=32 time=28ms TTL=55
Reply from 195.149.21.11: bytes=32 time=24ms TTL=55
Reply from 195.149.21.11: bytes=32 time=25ms TTL=55
Reply from 195.149.21.11: bytes=32 time=43ms TTL=55
Reply from 195.149.21.11: bytes=32 time=24ms TTL=55
Reply from 195.149.21.11: bytes=32 time=31ms TTL=55
Reply from 195.149.21.11: bytes=32 time=21ms TTL=55
Reply from 195.149.21.11: bytes=32 time=26ms TTL=55
Reply from 195.149.21.11: bytes=32 time=23ms TTL=55

Ping statistics for 195.149.21.11:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 43ms, Average = 27ms

Boards:


Pinging www.boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=41ms TTL=51
Reply from 217.114.166.147: bytes=32 time=46ms TTL=51
Reply from 217.114.166.147: bytes=32 time=83ms TTL=51
Reply from 217.114.166.147: bytes=32 time=49ms TTL=51
Reply from 217.114.166.147: bytes=32 time=42ms TTL=51
Reply from 217.114.166.147: bytes=32 time=38ms TTL=51
Reply from 217.114.166.147: bytes=32 time=39ms TTL=51
Reply from 217.114.166.147: bytes=32 time=41ms TTL=51
Reply from 217.114.166.147: bytes=32 time=39ms TTL=51
Reply from 217.114.166.147: bytes=32 time=41ms TTL=51
Reply from 217.114.166.147: bytes=32 time=38ms TTL=51
Reply from 217.114.166.147: bytes=32 time=47ms TTL=51
Reply from 217.114.166.147: bytes=32 time=38ms TTL=51

Ping statistics for 217.114.166.147:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 83ms, Average = 44ms




I'm not 100% on this, but from traceroutes it looks like IBB have dropped Colt and gone with C&W (are they the same?). It's 10 hops to jolt, 12ms on the IBB network, about 10 then to jolt. It goes IBB - tiscali - nildram (the network jolt is on).

Whereas to Boards it's IBB - C&W - boards across 14 hops. The biggest latency it between:

bcr2-so-2-0-0.Thamesside.cw.net [166.63.209.197]
bcr1.Thamesside.cw.net [166.63.210.61]
cable-and-wireless-internal-isp.Thamesside.cw.net

with 30ms added between the 3.

MickFarr

Name: NTL 600 Always-On cable
Speed: 600/128

I seem to have great pings but the downloads pong


Pinging www.boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=41ms TTL=51
Reply from 217.114.166.147: bytes=32 time=36ms TTL=51
Reply from 217.114.166.147: bytes=32 time=37ms TTL=51
Reply from 217.114.166.147: bytes=32 time=38ms TTL=51

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 41ms, Average = 38ms



Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=31ms TTL=53
Reply from 195.149.21.11: bytes=32 time=26ms TTL=53
Reply from 195.149.21.11: bytes=32 time=27ms TTL=53
Reply from 195.149.21.11: bytes=32 time=27ms TTL=53

Ping statistics for 195.149.21.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 31ms, Average = 27ms

colincarnate

HOLD ON A SEC!
D'y'know the way 56k dial-up ****e lines really give 4k, is that the same with DSL? As in: i'm promised 512k with DSL Eircom-style, will that mean i'll only get 104k

MrPinK

Originally posted by colincarnate
HOLD ON A SEC!
D'y'know the way 56k dial-up ****e lines really give 4k, is that the same with DSL? As in: i'm promised 512k with DSL Eircom-style, will that mean i'll only get 104k

If you pass the line test for RADSL that means your line is capable of at least 256k. If you're line is any worse than this they won't let you get DSL.

MickFarr

modem = 56kbps (kilo bits per second) not 56KB (kilo bytes per second)

BKtje

There are 8 bits in a Byte so 56kb/8 = 7kB/s (note capital B for Byte) . However people rarely connect at 56k and then there are some overheads.

Same way 64k isdn gives dlaod of 8kB/s and 128k gives 16kB/s (-overhead)

256k gives 32kB/s and 512k gives 64kB/s (-overheads)

Of course thats in theory. Speeds will always bea little slower.

ando

Eircom 512/128 starter pack radsl



C:\>ping clarity.jolt.co.uk

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=31ms TTL=57
Reply from 195.149.21.11: bytes=32 time=16ms TTL=57
Reply from 195.149.21.11: bytes=32 time=16ms TTL=57
Reply from 195.149.21.11: bytes=32 time=16ms TTL=57

Ping statistics for 195.149.21.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 31ms, Average = 19ms


excellent

LumoColor

Nice.

/me gotta get one of those. netfarce can go spin.

Chaz

C:\Documents and Settings\Chaz>ping www.google.com

Pinging www.google.akadns.net [216.239.59.99] with 32 bytes of data:

Reply from 216.239.59.99: bytes=32 time=3ms TTL=55
Reply from 216.239.59.99: bytes=32 time=3ms TTL=55
Reply from 216.239.59.99: bytes=32 time=3ms TTL=55
Reply from 216.239.59.99: bytes=32 time=4ms TTL=55

Ping statistics for 216.239.59.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 4ms, Average = 3ms

Irish Broadband Business Connection :-)

LumoColor

Originally posted by Chaz
Reply from 216.239.59.99: bytes=32 time=4ms TTL=55

I thought we'd done the editing dos output to make your pings look better posts......

Mutant_Fruit

I don;t believe this, how come a business line can get pings about 5 times better than mine, at the very least. I thought contention ratio was only supposed to effect download speeds, not pings.

Chaz

Who said that contention will only affect download speeds and pings? They go hand in hand to a large extent.

The system that this is running on is a new product offering with higher bandwidth etc. It is given out for business clients that want 1Meg and upwards.

Mutant_Fruit

This is what i always thought happened in a gateway server.....

These are only basic figures....

A gateway server can handle a max of 50 people, so therefore it has enough bandwidth for 50 people at 10-1 (assuming they are all on 10-1 contention to make sums easier). That means, if 5 people connect to the server, everyone gets full speeds and great pings, as the server isn;t under a lot of stress.

4 times that, 20 people are connecting to the server, this means that everyone gets half bandwidth, BUT pings should still be great, as the server isn;t even over 50% load. But, when you get to 45 people connected and downloading, speeds will be terrible, and so will pings, as the server is under 90% load.

So basically, download speed is an indication of what pings you should be getting. If you are getting speeds of over 50% of the connection speed, you should be getting good/great pings to go with it. Unless of course the server is capible of holding 25 people, and 50 people are been connected to it.

I know from past experience, that i've been able to achieve download speeds <300k, and yet i have gotten pings to the Gateway averaging 100ms+.

Maybe my idea is wrong, but from reading up on these things, thats what i've gathered. Following from this, you would expect to get better pings on a Business line, but pings that much better?

You're pinging external sites with 1/3 of the time it takes me to ping my gateway, on the very best of days.

EDIT: and this is not the best of days....

Ping statistics for 216.239.59.99:
Packets: Sent = 28, Received = 28, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 295ms, Maximum = 555ms, Average = 395ms

Chaz

I agree with the basic of contention and pings. In most situations - if bandwidth is low - pings are high. If a person however ran some form of bandwidth management software - and dedicated 64K of their contended 512K connection for gaming (normally UDP) then pings would be more stable.

The issue here is that there are differences in technology from providers to providers and also a difference in technology based on the clients needs.

Mutant_Fruit

and i presume you don't know if IBB use the "dedicate 64k" method, do you?

Chaz

Of course I do - I work for them afterall.

By default a 512K 1:8 connection has a commited rate of 64K.

Kevok

Chaz is that the 'IP link' mentioned on the site? If so how much does that normally cost?

You don't happen to know if the 3-rock mast is seeing some unusually high interference do you? My pings have been awful recently and download speeds just as bad. I had my gateway and IP changed today but it has made no difference. Or is it heavily contended? (i'm on the 1meg 8:1 option)

I can't see myself staying with IBB if it's not sorted to be honest.