problems with eircom

sunzz

Anyone else getting HORRIBLE pings the last few weeks with eircom. I'm thinking about moving over to bt, I'm in the sligo area.

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

1 <1 ms 1 ms 1 ms 192.168.1.254
2 239 ms 287 ms 296 ms b-ras1.mvw.galway.eircom.net [159.134.155.25]
3 17 ms 21 ms 18 ms ge15-2.coreb.mvw.galway.eircom.net [83.71.114.14
5]
4 210 ms 205 ms 211 ms 83.71.112.253
5 203 ms 199 ms 205 ms te1-3.cr05.tn5.bb.pipex.net [195.66.224.29]
6 * 228 ms 246 ms g1-1-6.ar01.tn5.bb.pipex.net [62.72.140.142]
7 193 ms 199 ms 214 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.24
1.14]
8 189 ms 191 ms 189 ms secure.jolt.co.uk [82.133.85.65]




Tracing route to www.boards.ie [82.195.136.250]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.254
2 28 ms 46 ms 25 ms b-ras1.mvw.galway.eircom.net [159.134.155.25]
3 14 ms 13 ms 13 ms ge15-2.corea.mvw.galway.eircom.net [83.71.114.12
9]
4 39 ms 31 ms 33 ms 83.71.115.214
5 27 ms 21 ms 19 ms border1.hosting365.ie [193.242.111.87]
6 24 ms 21 ms 18 ms 82.195.143.3
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.


Any suggestions on what to do email/ring or just change isp ?

Sponge Bob

looks like congestion in your exchange and/or contention between Sligo and Mervue (MRV Galway) , it can take months to add capacity as dcully found out in Monasterevin. I don't think its Galway - Dublin or the whole of the wesht would notice.

be prepared to complain bitterly to all and sundry starting with the Sligo Champion . Also walk into the Sligo main exchange where the local engineers are and ask for one, they have answers unlike 1901 muppets

Its not your line anyway .

OfflerCrocGod

Well at least we have solid proof BB is becoming very popular in areas that can avail of it if exchanges need upgrading for capacity.




Or maybe it's just a few leeches destroying the service for all........

dub45

What sort of speeds are you getting?

Dcully

Or maybe it's just a few leeches destroying the service for all

I think that is a very very valid comment.
I download nothing but game patches and maybe game trailers,no torrents whatsoever.

IMO the sooner the better eircom etc charge for going over the limits.
I expect an earfull for saying it but if you went through the 6 months i have you may agree with me.

I hope the OP gets this sorted sooner than i did.

gordonnet

this is cork tonight at 10pm, it been like this for the last two weeks

Tracing route to www.l.google.com [72.14.221.103]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 761 ms 263 ms 429 ms b-ras1.chf.cork.eircom.net [159.134.155.21]
3 19 ms 19 ms 20 ms ge15-2.corea.chf.cork.eircom.net [83.71.114.65]
4 34 ms 32 ms 33 ms 83.71.112.198
5 34 ms 33 ms 34 ms 195.66.224.125
6 42 ms 41 ms 42 ms 209.85.248.80
7 42 ms 43 ms 41 ms 209.85.248.85
8 49 ms 49 ms 47 ms 72.14.232.209
9 48 ms 48 ms 47 ms 72.14.232.201
10 52 ms 53 ms 58 ms 209.85.250.46
11 48 ms 47 ms 47 ms fg-in-f103.google.com [72.14.221.103]

Trace complete.

bloke

gordonnet wrote:

this is cork tonight at 10pm, it been like this for the last two

gordonnet wrote:

10 52 ms 53 ms 58 ms 209.85.250.46
11 48 ms 47 ms 47 ms fg-in-f103.google.com [72.14.221.103]

Trace complete.

Maybe I'm missing something - but what's wrong with 48ms latency to google over a DSL line?

gordonnet

the problem is here: 1 <1 ms <1 ms <1 ms 192.168.1.254
2 761 ms 263 ms 429 ms b-ras1.chf.cork.eircom.net [159.134.155.21]

connection to the gateway has high latentcy, consistent over a number of days

Sponge Bob

Its contention or congestion or _maybe_ a dodgy line , post your line stats off that Netopia Gordonnet (it is a Netopia is it not ??)

are you in cork city outside ???

bloke

gordonnet wrote:

the problem is here: 1 <1 ms <1 ms <1 ms 192.168.1.254
2 761 ms 263 ms 429 ms b-ras1.chf.cork.eircom.net [159.134.155.21]

connection to the gateway has high latentcy, consistent over a number of days

That hop would be the access concentrator... designed to pass your traffic and that of thousands of other users *through* it, but not particularly designed to handle traffic *to* it. Replying to your ping is not one of its priorities.

The fact that latency at all subsequent hops is fine shows that it's passing through the device absolutely fine. Unless you have a pressing need for low latency access to the access concentrator cpu itself, this traceroute does not indicate anything unusual.

BTW not saying you don't have some sort of issue - just that this traceroute doesn't show one!

Sponge Bob

true

if he pinged example

ping - t 123.123.123.123

any of these lads below and got a time of c 30ms on a 2mb line then there is nothing wrong as bloke said

2 761 ms 263 ms 429 ms b-ras1.chf.cork.eircom.net [159.134.155.21]
3 19 ms 19 ms 20 ms ge15-2.corea.chf.cork.eircom.net [83.71.114.65]
4 34 ms 32 ms 33 ms 83.71.112.198
5 34 ms 33 ms 34 ms 195.66.224.125

especially pinging the lower ones on the list.

lynchie

I was having this issue with 3 dsl lines in different exchanges around Dublin yesterday. The offending router 83.71.113.102 looks congested adding on at least 200ms to all routes going through it. Seems to have calmed down at the minute, but i get the odd spike from 50-250 ms from it.