Via Latency Problems

ando · 20-05-2003 6:23pm #1

Ok, Now I'm getting extremely bad pings of to game servers in the UK:

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=431ms TTL=248
Reply from 195.149.21.11: bytes=32 time=241ms TTL=248
Reply from 195.149.21.11: bytes=32 time=250ms TTL=248
Reply from 195.149.21.11: bytes=32 time=271ms TTL=248

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

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

Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.0.1
2 261 ms 230 ms 250 ms rt004dub.netsource.ie [213.79.63.254]
3 221 ms 260 ms 291 ms rt001dub.netsource.ie [212.17.32.97]
4 260 ms 280 ms 281 ms rt001kil.netsource.ie [212.17.32.101]
5 180 ms 130 ms 120 ms t3-4-2-0.ar1.dub1.gblx.net [64.213.22.253]
6 260 ms 331 ms 280 ms so6-0-0-2488M.cr2.LON3.gblx.net [64.212.107.241]

7 260 ms 221 ms 230 ms pos2-0-622M.ar2.LON2.gblx.net [208.49.136.58]
8 311 ms 350 ms 321 ms lon1-9.nildram.net [195.66.224.59]
9 150 ms 170 ms 130 ms jolt-gw.nildram.net [195.149.20.126]
10 301 ms 220 ms 180 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

Now compare this to yesturday or every early morning:

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=50ms TTL=248
Reply from 195.149.21.11: bytes=32 time=41ms TTL=248
Reply from 195.149.21.11: bytes=32 time=40ms TTL=248
Reply from 195.149.21.11: bytes=32 time=40ms TTL=248

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

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

Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.0.1
2 20 ms 20 ms 20 ms rt004dub.netsource.ie [213.79.63.254]
3 20 ms 20 ms 20 ms rt001dub.netsource.ie [212.17.32.97]
4 30 ms 30 ms 30 ms rt001kil.netsource.ie [212.17.32.101]
5 60 ms 40 ms 110 ms t3-4-2-0.ar1.dub1.gblx.net [64.213.22.25
6 50 ms 60 ms 71 ms so6-0-0-2488M.cr2.LON3.gblx.net [64.212.
7 40 ms 40 ms 50 ms pos2-0-622M.ar2.LON2.gblx.net [208.49.13
8 61 ms 80 ms 60 ms lon1-9.nildram.net [195.66.224.59]
9 60 ms 60 ms 60 ms jolt-gw.nildram.net [195.149.20.126]
10 60 ms 60 ms 70 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

I've complained to netsource about the intermediate problem of unstable pings, and they got back to me today

We're experiencing some contention on the RADSL link from Eircom -
basically it appears that at peak times the amount of data being
shifted is causing traffic to experience some latency.

We've asked Eircom for additional capacity to handle the traffic and
hopefully reduce the latency to you, but I'm afraid the variations you
are seeing is the nature of the contented product

So basically they cannot do anything about the problem. Its times like this I'd prefare a cap

Sloth · 20-05-2003 6:55pm

I had some mild latency (150 pings) at about 4:30 but after about ten minutes it cleared up and was back to it's usual interleaved self (60-90ish). Downloads seemed a bit slower too but it was only for ten minutes and then I was back to full speed again (53k or so) and have been ever since.

ando · 20-05-2003 7:00pm

hmm, if your ok, then the problem could be at the exchange level. Since I posted this thread I left the computer downloading a Linux file from Esat's FTP. I got an average 14KB's

Sloth · 20-05-2003 7:02pm

Send me the file link and I'll test it out.
I'd agree that it could be an exchange issue, thats where my problem lay so ask them to check it out when you ring them tomorrow.

ando · 20-05-2003 7:31pm

ftp://ftp.esat.net/pub/linux/mandrake/iso/Mandrake91-cd1-inst.i586.iso

thats the file I was getting 14kB with

Sloth · 20-05-2003 7:37pm

Hmm, 54.3k here. To be honest it sounds like you have exactly the same problems I had, just ring up Via and ask them about checking if the exchange is ok.

flav0rflav · 20-05-2003 7:47pm

I experiencing similar 'service'. Oh well, the world of broadband is losing(?) it's shine.

pings are pants, and dls are down.

20-05-2003 8:53pm

Originally posted by ando
ftp://ftp.esat.net/pub/linux/mandrake/iso/Mandrake91-cd1-inst.i586.iso

thats the file I was getting 14kB with

54.1 or so on that here

Mountjoy Mugger · 20-05-2003 9:01pm

49KB/Sec ish Summerhill exchange, for the same file.

EDIT - Oops, that's on eircom's self install, soz lads. But it'll be the same for any Netsource/Via users on the exchange, I reckon.

Ste- · 20-05-2003 9:19pm

Getting speed of 20KB/sec for that file.
Same thing on Saturday night.

Obo · 20-05-2003 9:35pm

I was getting about 17KB/sec on that iso, although it was very slowly rising. (Netsource RADSL)

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

Reply from 195.149.21.11: bytes=32 time=297ms TTL=249
Request timed out.
Reply from 195.149.21.11: bytes=32 time=266ms TTL=249
Reply from 195.149.21.11: bytes=32 time=297ms TTL=249
Reply from 195.149.21.11: bytes=32 time=282ms TTL=249
Reply from 195.149.21.11: bytes=32 time=266ms TTL=249
Reply from 195.149.21.11: bytes=32 time=282ms TTL=249
Reply from 195.149.21.11: bytes=32 time=312ms TTL=249
Reply from 195.149.21.11: bytes=32 time=312ms TTL=249
Reply from 195.149.21.11: bytes=32 time=313ms TTL=249
Reply from 195.149.21.11: bytes=32 time=313ms TTL=249
Reply from 195.149.21.11: bytes=32 time=219ms TTL=249
Request timed out.
Reply from 195.149.21.11: bytes=32 time=281ms TTL=249
Reply from 195.149.21.11: bytes=32 time=234ms TTL=249
Reply from 195.149.21.11: bytes=32 time=172ms TTL=249
Reply from 195.149.21.11: bytes=32 time=313ms TTL=249
Reply from 195.149.21.11: bytes=32 time=344ms TTL=249
Reply from 195.149.21.11: bytes=32 time=188ms TTL=249
Reply from 195.149.21.11: bytes=32 time=297ms TTL=249
Reply from 195.149.21.11: bytes=32 time=375ms TTL=249
Reply from 195.149.21.11: bytes=32 time=235ms TTL=249
Reply from 195.149.21.11: bytes=32 time=328ms TTL=249

Ping statistics for 195.149.21.11:
Packets: Sent = 23, Received = 21, Lost = 2 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 172ms, Maximum = 375ms, Average = 257ms

ando · 20-05-2003 10:13pm

sloth, are you definatly on Radsl SOHO netsource package? R your pings to clarity.jolt.co.uk stable during peak times?

BlackFlag · 21-05-2003 10:18am

Originally posted by flav0rflav
I experiencing similar 'service'. Oh well, the world of broadband is losing(?) it's shine.

pings are pants, and dls are down.

Esat Business line is expensive but you pay for what you get m8s.............tis class...not one problem in almost 2 weeks now
pinging on game servers in uk betweem 18-35 and d/l fine

carbsy · 21-05-2003 10:23am

Originally posted by BlackFlag
Esat Business line is expensive but you pay for what you get m8s.............tis class...not one problem in almost 2 weeks now
pinging on game servers in uk betweem 18-35 and d/l fine

I shouldn't have to fork out €108.90 per month for a usable xDSL service! :mad:

carb.

P.S. €66 per month is still expensive (Netsource) and what do we get? .... atrocious pings and below par downloads. (I don't want to hear any contention bull****e as there are more €ircon users than Netsource and they aren't experiencing any problems) An absolute disgrace for the money. :mad:

BlackFlag · 21-05-2003 10:29am

I do agree.....but 3 years ago I was running up bills of £200 punts a MONTH just to play off peak with an ISDN connection I would have bitten off the hand if anyone had of offered the package I am on now back then......

We are 3 steps behind UK alright but they in turn are 10 steps behind the Dutch who have 2mb lines which d/l at over 300kb/s in some cases and is cheaper than what I pay for 512(608)/256(320)

ando · 21-05-2003 1:05pm

i never taught it would be this bad so soon after launch. i mean, utv isdn has a reputation for really bad pings, but I end up dialling into utv to play games, dsl for surfing

Sloth · 21-05-2003 1:58pm

I'm on the ADSL service. It's basically the same as Esat's business one only theres no cap but you get higher pings (75ish is the norm).

21-05-2003 2:33pm

Originally posted by ando
i never taught it would be this bad so soon after launch. i mean, utv isdn has a reputation for really bad pings, but I end up dialling into utv to play games, dsl for surfing

ando,
Is your contract covered under the sale of goods act, ie can you reject the service within a cooling off period?
It's possible that, thats ten days or so.
If you are finding that the main reason you got VIA was for gaming and you cannot use it, surely theres an arguable case there.
After all you are paying through the nose for the ISDN and the move to dsl is supposed to be saving you money.

mm

Obo · 23-05-2003 2:34pm

At the moment it looks to be back as it should be (except that there is still interleaving

).
Maybe I have the connection all to myself.

C:\>ping -t boards.ie

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

Reply from 217.114.166.147: bytes=32 time=63ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=32ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
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=31ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=47ms TTL=53
Reply from 217.114.166.147: bytes=32 time=31ms TTL=53

Ping statistics for 217.114.166.147:
Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 63ms, Average = 44ms
Control-C
^C
C:\>ping -t 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=47ms TTL=248
Reply from 195.149.21.11: bytes=32 time=31ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Request timed out.
Reply from 195.149.21.11: bytes=32 time=250ms TTL=248
Reply from 195.149.21.11: bytes=32 time=31ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248
Reply from 195.149.21.11: bytes=32 time=32ms TTL=248

Ping statistics for 195.149.21.11:
Packets: Sent = 21, Received = 20, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 250ms, Average = 41ms
Control-C
^C

fatguy · 23-05-2003 9:59pm

I literally just got connected right now. Pinging 350 to www.ireland.com, lost 5/45 packets, maximum dl I got was 11k/s.

Not impressed. The exchange (Whitehall) apparently had a problem, so we'll see if that's what's happening. Also 11pm on a Friday night is likely to have plenty of users on. I'll post again with how it's like at 3am.

Damian · 24-05-2003 1:35am

I'm also on the Whitehall exchange and just got connected this evening.

And I'm also getting terrible pings.
both www.ireland.com and clarity.jolt.co.uk vary between 200 to 300.

And more towards the 300 mark!

I am getting faster downloads than fatguy, although not great at about 30 k/s.

For some reason I don't have traceroute installed. I'll sort it out and post some traces later tonight.

ando · 24-05-2003 10:01am

We've asked Eircom for additional capacity to handle the traffic and
hopefully reduce the latency to you

anybody know how long this takes? getting pings of 300 to Jolt on a saturday morning is pis$ing me off :mad:

disco_rob_funk · 24-05-2003 1:31pm

Is there actually something wrong (& fixable) with Netsource/Eircom, or is this the way it's gonna be when it gets busy?

My pings are shot to shít and I'm at about 60% previous bandwidth at best.

Terminator · 24-05-2003 4:19pm

What is up with Netsource? Connection speed is down to about 40% of what it was a week ago.

thomasb · 24-05-2003 6:55pm

Hey folks,

The Link the RADSL users are on is still quite heavy (don't you lot have any thing better to do at weekends?

).

This will lead to slow pings / latency and dodgy through put. I'm hoping the upgraded link will be in place next week - and I'll be chasing Eircom to get it done as I know you will all be wanting to put it through its paces over the bank holiday weekend.

Regards,

Thomas

Mr. Fancypants · 24-05-2003 7:12pm

Hey Thomas, what will the link be upgraded too? I hope you guys arent just going to be continuosly chasing this problem. Its only a couple of weeks after launch and are having serious issues with bandwidth, i hope you will be putting in the infrastructure to deal with this permanently. Thanks again for replying to customers problems in open way.

carbsy · 24-05-2003 7:44pm

Originally posted by mbroaders
Hey Thomas, what will the link be upgraded too? I hope you guys arent just going to be continuosly chasing this problem. Its only a couple of weeks after launch and are having serious issues with bandwidth, i hope you will be putting in the infrastructure to deal with this permanently. Thanks again for replying to customers problems in open way.

I second that!

carb.

disco_rob_funk · 24-05-2003 8:08pm

Originally posted by carbsy
I second that!

carb.

Most definitely, any pals in the area who want to get conected to Netsource aren't even connected yet, and they'll be on ALL night every night!

Please don't go easy on the upgrade, plan for as high demand as possible.

Cheers

RC

thomasb · 24-05-2003 8:29pm

We'll triple the current size of the current connection from Eircom and see how that goes. I think that will cover us - most of the customers due to be installed in the next couple of weeks are exchanges already installed.

I would point out that the contention on the current connection isn't even remotely approaching 48:1. Its also hard to come up with a definitive plan, as the 48:1 contention is on a per exchange basis (ie if disco_rob_funk's mates all share the same exchange, then the contention will be imposed between their exchange and the BAS which handles L2TP tunnels) and no matter how much more bandwidth I put in, I can't do anything about that.

disco_rob_funk · 24-05-2003 8:56pm

Can't say fairer than that; keep bugging eircom like a good fella!

RC

ando · 24-05-2003 10:23pm

Originally posted by thomasb
We'll triple the current size of the current connection from Eircom and see how that goes

I hope it works :eek: , download speeds are really down + pings are unbearable

The Brigadier · 25-05-2003 7:49am

It's not a Via issue, it an Eircom issue. I'm on a 1meg line and I got this :

Pinging www.eircom.net [159.134.237.56] with 32 bytes of data:

Reply from 159.134.237.56: bytes=32 time=89ms TTL=60
Reply from 159.134.237.56: bytes=32 time=250ms TTL=60
Reply from 159.134.237.56: bytes=32 time=335ms TTL=60
Reply from 159.134.237.56: bytes=32 time=228ms TTL=60

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

Hrumph...

flav0rflav · 25-05-2003 4:54pm

Huh? You want to expand on that, Melody?

fatguy · 25-05-2003 8:40pm

That's good news, thomasb. I had only just sent an email to Nicola Ryan with some information on how poor my connection is when I saw this.

I'll post here and email Nicola as soon as things pick up.

Damian: the dos command is tracert, it should just work in a command prompt window, no need to install.

Via Latency Problems

Comments