Terrible latency to the UK and Europe

chriss745

Since a few days I experience high ping times for online gaming, I am on eFibre near Cork. I ran a traceroute to the UK and it looks bad:

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    42 ms    17 ms    16 ms  95.44.68.1
  3    17 ms    17 ms    18 ms  86.43.59.205
  4    22 ms    21 ms    22 ms  tenge-2-1-1.core2.dbn.core.eircom.net [86.43.253
.45]
  5     *       45 ms    22 ms  tenge-2-2-1.core2.bdt.core.eircom.net [86.43.252
.17]
  6    22 ms    22 ms    21 ms  ge0-0-0.peering1.csg.dublin.eircom.net [86.43.24
5.78]
  7     *        *        *     Request timed out.
  8   117 ms   120 ms   120 ms  ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
  9   130 ms   130 ms   131 ms  4.69.153.229
 10   130 ms   130 ms   130 ms  ae-58-113.csw1.London1.Level3.net [4.69.153.122]

 11   126 ms   129 ms   131 ms  ae-119-3505.edge4.London1.Level3.net [4.69.166.1
]
 12    37 ms    35 ms    38 ms  195.50.122.158
 13   123 ms   119 ms   119 ms  173.199.79.197.choopa.net [173.199.79.197]

Trace complete.

I found the following pings to the same destimation from a week ago on this forum:

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.254
2 23 ms 23 ms 35 ms 95.45.46.1
3 24 ms 23 ms 23 ms 86.43.10.177
4 30 ms 26 ms 26 ms tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252.97]
5 24 ms 24 ms 23 ms ge0-0-0.peering1.csg.dublin.eircom.net [86.43.245.78]
6 24 ms 93 ms 40 ms 195.16.170.41
7 26 ms 28 ms 25 ms ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
8 37 ms 39 ms 38 ms 4.69.153.229
9 38 ms 35 ms 36 ms ae-59-114.csw1.London1.Level3.net [4.69.153.126]

10 36 ms 35 ms 35 ms ae-121-3507.edge4.London1.Level3.net [4.69.166.9]
11 40 ms 36 ms 36 ms 195.50.122.158
12 36 ms 36 ms 35 ms 173.199.79.197.choopa.net [173.199.79.197]

Trace complete.


Between 86.43.245.78 and 4.69.153.237 there was 2 ms latency a week ago, today it is almost a 100 ms.

thret

Same issue for past 6-7 months with ADSL2+ 24MB

They don't want to solve my issue no matter how hard I try.

They keep telling me that 100ms to UK is normal.. well no it's not for an FPS gamer.

I'm currently looking for low ms provider to get away from them ASAP..

I'll follow this thread to see how it goes for you.

Good Luck!

eircom: Alan

Hi thret & chriss745

I'm afraid I do not have any information regarding these issues however for more information please visit our websit and check out the technical support live chat option : http://bit.ly/19rUr5k

Thanks

Al

Hank Scorpio

thret wrote: »

Same issue for past 6-7 months with ADSL2+ 24MB

They don't want to solve my issue no matter how hard I try.

They keep telling me that 100ms to UK is normal.. well no it's not for an FPS gamer.

I'm currently looking for low ms provider to get away from them ASAP..

I'll follow this thread to see how it goes for you.

Good Luck!

I'm on the same package and the exact same thing has been happening to me

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\PC>ping www.multiplay.co.uk Random English server

Pinging sites01.multiplay.co.uk [85.236.96.26] with 32 bytes of data:
Reply from 85.236.96.26: bytes=32 time=100ms TTL=53
Reply from 85.236.96.26: bytes=32 time=99ms TTL=53
Reply from 85.236.96.26: bytes=32 time=106ms TTL=53
Reply from 85.236.96.26: bytes=32 time=104ms TTL=53

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

C:\Users\PC>ping de2.ut99.pro Random Server in Germany

Pinging de2.ut99.pro [82.96.119.12] with 32 bytes of data:
Reply from 82.96.119.12: bytes=32 time=178ms TTL=119
Reply from 82.96.119.12: bytes=32 time=182ms TTL=119
Reply from 82.96.119.12: bytes=32 time=170ms TTL=119
Reply from 82.96.119.12: bytes=32 time=167ms TTL=119

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

C:\Users\PC>

C:\Users\PC>ping bbc.co.uk

Pinging bbc.co.uk [212.58.246.104] with 32 bytes of data:
Reply from 212.58.246.104: bytes=32 time=178ms TTL=53
Reply from 212.58.246.104: bytes=32 time=178ms TTL=53
Reply from 212.58.246.104: bytes=32 time=175ms TTL=53
Reply from 212.58.246.104: bytes=32 time=173ms TTL=53

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

C:\Users\PC>

I'm on fathpath too, these pings make any online gaming impossible.

Are eircom cheaping out on they're routing policy? The pings are low locally so it isn't a direct congestion problem

Conallmacker

Yep also been having this problem, its been getting worse as they roll out their efiber across the country.getting over 200 ping to Germany

Hank Scorpio

Yeah, I own servers in Germany and it's been like this for at least 6 months. Sort it out eircom please

eircom: Alan

Hi All
 
I have been informed that there has been confirmation of a break in a major cable under the Irish Sea.
 
This has created a lot of issues on the network and explains a lot of the issues you have raised. I would like to assure you that divers and engineers are being dispatched tomorrow morning to begin repairs.
 
At present we do not have a specific timeframe of how long repairs are expected to take however there are indications that this could indeed take up to a couple of days. I will do my best to keep you updated on any further information I may get.
 
Thanks
 
Al

chriss745

eircom: Alan wrote: »

Hi All
 
I have been informed that there has been confirmation of a break in a major cable under the Irish Sea.
 
This has created a lot of issues on the network and explains a lot of the issues you have raised. I would like to assure you that divers and engineers are being dispatched tomorrow morning to begin repairs.
 
At present we do not have a specific timeframe of how long repairs are expected to take however there are indications that this could indeed take up to a couple of days. I will do my best to keep you updated on any further information I may get.
 
Thanks
 
Al

Thanks Al, it is good to know, please keep us updated.

thret

Gotten even worse by yesterday and tonight.. really need this fixed ASAP
Can't do anything.

Hank Scorpio

thret wrote: »

Gotten even worse by yesterday and tonight.. really need this fixed ASAP
Can't do anything.

My routes keep changing, so I have to change from server to server in germany. It's really unpredictable and annoying since I'm paying for servers.

Anyway I`ll give it a couple of days and see if the issue is resolved

You on fastpath too? 24mb ngb

thret

nuxxx wrote: »

thret wrote: »

Gotten even worse by yesterday and tonight.. really need this fixed ASAP
Can't do anything.

My routes keep changing, so I have to change from server to server in germany. It's really unpredictable and annoying since I'm paying for servers.

Anyway I`ll give it a couple of days and see if the issue is resolved

You on fastpath too? 24mb ngb

I am now, but 8mb because they wouldn't let me on it on 24mb.. but it didn't solve my issue so I'm going to tell them to change it back to 24 tomorrow.
I hope all the routing changes are due to them investigating this issue..
I have 250,000$ tournament qualifier on Friday.. I don't really want to lag, but don't think this will be resolved any time soon so might need to go to a friends house with UPC lol...


edit; I checked eircom forums and can see that Alan has raised this higher up and has gotten some response. Check this thread out

http://community.eircom.net/t5/Broadband/High-Ping-in-the-evenings/td-p/55110/page/11

Hi All

I have been informed that there has been confirmation of a break in a major cable under the Irish Sea.

Hank Scorpio

What game you playing? GL in the qualifier

ElNino

eircom: Alan wrote: »

Hi All
 
I have been informed that there has been confirmation of a break in a major cable under the Irish Sea.
 
This has created a lot of issues on the network and explains a lot of the issues you have raised. I would like to assure you that divers and engineers are being dispatched tomorrow morning to begin repairs.
 
At present we do not have a specific timeframe of how long repairs are expected to take however there are indications that this could indeed take up to a couple of days. I will do my best to keep you updated on any further information I may get.
 
Thanks
 
Al

Alan can you confirm that the break wasn't in eircom's cable but in another cable used by other telcos? And that the congestion on the eircom network is being caused because eircom allowed those other telcos to piggy back on to the eircom cable even though there isn't enough capacity?

Hank Scorpio

Just gonna post my pings in this thread this evening, hopefully by Saturday this will be resolved. The following are 4 servers from Germany, all different IP's/Server providers.

I'm on 24Mb NGB with fastpath

German server 1

Pinging de1.ut99.pro [80.82.215.118] with 32 bytes of data:
Reply from 80.82.215.118: bytes=32 time=182ms TTL=56
Reply from 80.82.215.118: bytes=32 time=193ms TTL=56
Reply from 80.82.215.118: bytes=32 time=187ms TTL=56
Reply from 80.82.215.118: bytes=32 time=189ms TTL=56

German server 2

Pinging de2.ut99.pro [82.96.119.12] with 32 bytes of data:
Reply from 82.96.119.12: bytes=32 time=181ms TTL=119
Reply from 82.96.119.12: bytes=32 time=187ms TTL=119
Reply from 82.96.119.12: bytes=32 time=187ms TTL=119
Reply from 82.96.119.12: bytes=32 time=187ms TTL=119

German server 3

Pinging de3.ut99.pro [5.62.105.37] with 32 bytes of data:
Reply from 5.62.105.37: bytes=32 time=233ms TTL=56
Reply from 5.62.105.37: bytes=32 time=232ms TTL=56
Reply from 5.62.105.37: bytes=32 time=237ms TTL=56
Reply from 5.62.105.37: bytes=32 time=235ms TTL=56

German server 4

Pinging 176.57.142.9 with 32 bytes of data:
Reply from 176.57.142.9: bytes=32 time=235ms TTL=55
Reply from 176.57.142.9: bytes=32 time=226ms TTL=55
Reply from 176.57.142.9: bytes=32 time=226ms TTL=55
Reply from 176.57.142.9: bytes=32 time=231ms TTL=55

And here's a trace to a uk server, getting routed through Paris

Tracing route to multiplay.co.uk [85.236.96.26]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.254
  2    11 ms    13 ms    11 ms  b-ras2.dbn.dublin.eircom.net [159.134.155.5]
  3    12 ms    12 ms    11 ms  ge-2-1-7.pe1.dbn.cld-dbn.eircom.net [86.43.246.1
57]
  4    15 ms    14 ms    14 ms  tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252
.97]
  5    11 ms    13 ms    11 ms  ge0-0-0.peering1.csg.dublin.eircom.net [86.43.24
5.78]
  6    35 ms    36 ms    37 ms  195.16.170.41
  7    90 ms    90 ms    87 ms  ae-12-12.ebr2.Paris1.Level3.net [4.69.153.242]
  8    88 ms    93 ms    89 ms  ae-82-82.csw3.Paris1.Level3.net [4.69.161.102]
  9    87 ms    89 ms    93 ms  ae-81-81.ebr1.Paris1.Level3.net [4.69.161.85]
 10    91 ms    89 ms    87 ms  ae-1-3.edge3.London2.Level3.net [4.69.141.85]
 11    36 ms    34 ms    34 ms  MULTIPLAY-L.edge3.London2.Level3.net [195.50.125
.6]
 12    96 ms    95 ms    95 ms  ha01.multiplay.co.uk [85.236.96.26]

chriss745

I can see serious improvement to UK:

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    21 ms    16 ms    17 ms  95.44.68.1
  3    17 ms    16 ms    16 ms  86.43.59.205
  4    23 ms    42 ms    22 ms  tenge-2-1-1.core2.dbn.core.eircom.net [86.43.253
.45]
  5    24 ms    22 ms    22 ms  tenge-2-2-1.core2.bdt.core.eircom.net [86.43.252
.17]
  6    23 ms    22 ms    22 ms  ge0-0-0.peering1.csg.dublin.eircom.net [86.43.24
5.78]
  7     *       47 ms    46 ms  195.16.170.41
  8    33 ms    32 ms    32 ms  ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
  9    70 ms    52 ms    54 ms  4.69.153.229
 10    49 ms    49 ms    48 ms  ae-58-113.csw1.London1.Level3.net [4.69.153.122]

 11    97 ms    48 ms    48 ms  ae-119-3505.edge4.London1.Level3.net [4.69.166.1
]
 12    34 ms    34 ms    34 ms  195.50.122.158
 13    48 ms    47 ms    47 ms  173.199.79.197.choopa.net [173.199.79.197]

razor75x

eircom: Alan wrote: »

Hi All
 
I have been informed that there has been confirmation of a break in a major cable under the Irish Sea.
 
This has created a lot of issues on the network and explains a lot of the issues you have raised. I would like to assure you that divers and engineers are being dispatched tomorrow morning to begin repairs.
 
At present we do not have a specific timeframe of how long repairs are expected to take however there are indications that this could indeed take up to a couple of days. I will do my best to keep you updated on any further information I may get.
 
Thanks
 
Al

hi mark I'm on the eircom 70mb pacakage and in the last while experiencing problems with my speeds in evenings dropping as low as 1mb ! phoned tech support who told me today just what you say above. i see you wrote this in october ? surely the problem is not still on going ? or can u please give me some information as to whats going on ?

thanks very much  

razor75x

eircom: Alan wrote: »

Hi All
 
I have been informed that there has been confirmation of a break in a major cable under the Irish Sea.
 
This has created a lot of issues on the network and explains a lot of the issues you have raised. I would like to assure you that divers and engineers are being dispatched tomorrow morning to begin repairs.
 
At present we do not have a specific timeframe of how long repairs are expected to take however there are indications that this could indeed take up to a couple of days. I will do my best to keep you updated on any further information I may get.
 
Thanks
 
Al

apologies i see you wrote this information on the 14th of this month , can u give a insight as to when it could be resolved ? thanks alan 

Hank Scorpio

problem still presists, 200ms+ ping to central europe

chriss745

nuxxx wrote: »

problem still presists, 200ms+ ping to central europe

It looks like for me the problem between Ireland an UK is gone right now:

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    36 ms    79 ms    25 ms  95.44.68.1
  3    17 ms    18 ms    16 ms  86.43.59.205
  4    27 ms    23 ms    22 ms  tenge-2-1-1.core2.dbn.core.eircom.net [86.43.253
.45]
  5     *        *       26 ms  tenge-2-2-1.core2.bdt.core.eircom.net [86.43.252
.17]
  6    34 ms    25 ms    35 ms  ge0-0-0.peering1.csg.dublin.eircom.net [86.43.24
5.78]
  7    22 ms    27 ms    23 ms  195.16.170.41
  8    30 ms    31 ms    23 ms  ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
  9    36 ms    38 ms    44 ms  4.69.153.229
 10    38 ms    39 ms    33 ms  ae-58-113.csw1.London1.Level3.net [4.69.153.122]

 11    49 ms    41 ms    39 ms  ae-119-3505.edge4.London1.Level3.net [4.69.166.1
]
 12    34 ms    34 ms    35 ms  195.50.122.158
 13    36 ms    38 ms    38 ms  173.199.79.197.choopa.net [173.199.79.197]


38 ms ping to the UK is good from Cork. 

I ran a few traceroutes to central Europe, and it looks like the routing can go through two different ways.

Way 1 (trunk, currently slow):

Tracing route to ftp.freepark.org [195.228.252.133]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    30 ms    66 ms    18 ms  95.44.68.1
  3    44 ms    35 ms    29 ms  86.43.59.201
  4    24 ms    34 ms    23 ms  tenge-2-1-1.core1.dbn.core.eircom.net [86.43.253
.17]
  5     *       48 ms    37 ms  86.43.11.182
  6    37 ms    42 ms    37 ms  ge0-0-0.corea.thn.london.eircom.net [86.43.245.1
62]
  7   162 ms   167 ms     *     decix.net.telekom.hu [80.81.194.86]
  8   179 ms   184 ms   178 ms  xe-8-3-0.ic0-ip2.net.telekom.hu [81.183.0.108]
  9   180 ms   161 ms   155 ms  xe-0-0-0.ic1-dplex.net.telekom.hu [81.183.0.203]

 10   187 ms   183 ms   180 ms  81.183.2.210
 11   179 ms   188 ms   178 ms  ftp.freepark.org [195.228.252.133]

In that case from London the next hop was Hungary. There is no direct link between UK and Hungary, so that must be a trunk (or I don't know how they call it in that case), where the problem looks to be.

Way 2 (normal hop-to-hop):

Tracing route to jedlik.hu [88.87.240.24]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    17 ms    16 ms    21 ms  95.44.68.1
  3    18 ms    23 ms    22 ms  86.43.59.201
  4    32 ms    24 ms    28 ms  tenge-2-1-1.core1.dbn.core.eircom.net [86.43.253
.17]
  5    38 ms    41 ms    38 ms  86.43.11.182
  6    38 ms    61 ms    48 ms  ge0-0-0.corea.thn.london.eircom.net [86.43.245.1
62]
  7    41 ms    37 ms    68 ms  gi3-0.lonth-inter-1.interoute.net [195.66.224.53
]
  8    73 ms    68 ms    84 ms  ae2-0.lon-001-score-2-re1.interoute.net [84.233.
218.185]
  9    65 ms    66 ms    68 ms  ae0-0.lon-001-score-1-re0.interoute.net [84.233.
218.189]
 10    75 ms    91 ms    93 ms  ae1-0.ams-koo-score-1-re0.interoute.net [84.233.
190.57]
 11    91 ms    82 ms    92 ms  ae0-0.ams-koo-score-2-re0.interoute.net [84.233.
190.2]
 12    67 ms    70 ms    71 ms  ae1-0.fra-006-score-1-re0.interoute.net [84.233.
190.50]
 13    71 ms    66 ms    65 ms  ae1-0.vie-per-score-1-re0.interoute.net [212.23.
43.25]
 14    82 ms    67 ms    70 ms  ae0-0.vie-per-score-2-re0.interoute.net [212.23.
43.50]
 15    81 ms    65 ms    74 ms  ae1-0.bts-001-score-1-re0.interoute.net [84.233.
147.13]
 16    87 ms    78 ms    68 ms  ae0-0.bts-001-score-2-re1.interoute.net [84.233.
147.2]
 17    85 ms    76 ms    91 ms  ae1-0.bud-001-score-2-re0.interoute.net [84.233.
147.113]

We get 70-80 ms ping from Cork to Budapest, which is decent I believe.

I would say right now the problem with that trunking from the UK. 

Hank Scorpio

that decix node is the one causing all the problems for me

chriss745

chriss745 wrote: »

nuxxx wrote: »

problem still presists, 200ms+ ping to central europe

It looks like for me the problem between Ireland an UK is gone right now:

Tracing route to 173.199.79.197.choopa.net [173.199.79.197]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    36 ms    79 ms    25 ms  95.44.68.1
  3    17 ms    18 ms    16 ms  86.43.59.205
  4    27 ms    23 ms    22 ms  tenge-2-1-1.core2.dbn.core.eircom.net [86.43.253
.45]
  5     *        *       26 ms  tenge-2-2-1.core2.bdt.core.eircom.net [86.43.252
.17]
  6    34 ms    25 ms    35 ms  ge0-0-0.peering1.csg.dublin.eircom.net [86.43.24
5.78]
  7    22 ms    27 ms    23 ms  195.16.170.41
  8    30 ms    31 ms    23 ms  ae-0-4.bar1.Dublin1.Level3.net [4.69.153.237]
  9    36 ms    38 ms    44 ms  4.69.153.229
 10    38 ms    39 ms    33 ms  ae-58-113.csw1.London1.Level3.net [4.69.153.122]

 11    49 ms    41 ms    39 ms  ae-119-3505.edge4.London1.Level3.net [4.69.166.1
]
 12    34 ms    34 ms    35 ms  195.50.122.158
 13    36 ms    38 ms    38 ms  173.199.79.197.choopa.net [173.199.79.197]


38 ms ping to the UK is good from Cork. 

I ran a few traceroutes to central Europe, and it looks like the routing can go through two different ways.

Way 1 (trunk, currently slow):

Tracing route to ftp.freepark.org [195.228.252.133]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    30 ms    66 ms    18 ms  95.44.68.1
  3    44 ms    35 ms    29 ms  86.43.59.201
  4    24 ms    34 ms    23 ms  tenge-2-1-1.core1.dbn.core.eircom.net [86.43.253
.17]
  5     *       48 ms    37 ms  86.43.11.182
  6    37 ms    42 ms    37 ms  ge0-0-0.corea.thn.london.eircom.net [86.43.245.1
62]
  7   162 ms   167 ms     *     decix.net.telekom.hu [80.81.194.86]
  8   179 ms   184 ms   178 ms  xe-8-3-0.ic0-ip2.net.telekom.hu [81.183.0.108]
  9   180 ms   161 ms   155 ms  xe-0-0-0.ic1-dplex.net.telekom.hu [81.183.0.203]

 10   187 ms   183 ms   180 ms  81.183.2.210
 11   179 ms   188 ms   178 ms  ftp.freepark.org [195.228.252.133]

In that case from London the next hop was Hungary. There is no direct link between UK and Hungary, so that must be a trunk (or I don't know how they call it in that case), where the problem looks to be.

Way 2 (normal hop-to-hop):

Tracing route to jedlik.hu [88.87.240.24]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    17 ms    16 ms    21 ms  95.44.68.1
  3    18 ms    23 ms    22 ms  86.43.59.201
  4    32 ms    24 ms    28 ms  tenge-2-1-1.core1.dbn.core.eircom.net [86.43.253
.17]
  5    38 ms    41 ms    38 ms  86.43.11.182
  6    38 ms    61 ms    48 ms  ge0-0-0.corea.thn.london.eircom.net [86.43.245.1
62]
  7    41 ms    37 ms    68 ms  gi3-0.lonth-inter-1.interoute.net [195.66.224.53
]
  8    73 ms    68 ms    84 ms  ae2-0.lon-001-score-2-re1.interoute.net [84.233.
218.185]
  9    65 ms    66 ms    68 ms  ae0-0.lon-001-score-1-re0.interoute.net [84.233.
218.189]
 10    75 ms    91 ms    93 ms  ae1-0.ams-koo-score-1-re0.interoute.net [84.233.
190.57]
 11    91 ms    82 ms    92 ms  ae0-0.ams-koo-score-2-re0.interoute.net [84.233.
190.2]
 12    67 ms    70 ms    71 ms  ae1-0.fra-006-score-1-re0.interoute.net [84.233.
190.50]
 13    71 ms    66 ms    65 ms  ae1-0.vie-per-score-1-re0.interoute.net [212.23.
43.25]
 14    82 ms    67 ms    70 ms  ae0-0.vie-per-score-2-re0.interoute.net [212.23.
43.50]
 15    81 ms    65 ms    74 ms  ae1-0.bts-001-score-1-re0.interoute.net [84.233.
147.13]
 16    87 ms    78 ms    68 ms  ae0-0.bts-001-score-2-re1.interoute.net [84.233.
147.2]
 17    85 ms    76 ms    91 ms  ae1-0.bud-001-score-2-re0.interoute.net [84.233.
147.113]

We get 70-80 ms ping from Cork to Budapest, which is decent I believe.

I would say right now the problem with that trunking from the UK. 

Much better today

Tracing route to ftp.freepark.org [195.228.252.133]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    41 ms    17 ms    17 ms  95.44.68.1
  3    18 ms    17 ms    17 ms  86.43.59.201
  4    23 ms    22 ms    22 ms  tenge-2-1-1.core1.dbn.core.eircom.net [86.43.253
.17]
  5     *        *        *     Request timed out.
  6    37 ms    37 ms    37 ms  ge0-0-0.corea.thn.london.eircom.net [86.43.245.1
62]
  7     *       70 ms     *     decix.net.telekom.hu [80.81.194.86]
  8    68 ms    68 ms    68 ms  xe-8-3-0.ic0-ip2.net.telekom.hu [81.183.0.108]
  9    68 ms    68 ms    68 ms  xe-0-0-0.ic1-dplex.net.telekom.hu [81.183.0.203]

 10    69 ms    69 ms    68 ms  81.183.2.210
 11    69 ms    68 ms    68 ms  ftp.freepark.org [195.228.252.133]

Hank Scorpio

try now? its over 100ms. In another hour it will be 200ms



Still the same for me to every server

This is what my brother on UPC gets no matter the time of the day

Pinging de2.ut99.pro [82.96.119.12] with 32 bytes of data:
Reply from 82.96.119.12: bytes=32 time=33ms TTL=117
Reply from 82.96.119.12: bytes=32 time=32ms TTL=117
Reply from 82.96.119.12: bytes=32 time=33ms TTL=117
Reply from 82.96.119.12: bytes=32 time=34ms TTL=117

This is what I get with 24MB NGB with fastpath enabled

Pinging de2.ut99.pro [82.96.119.12] with 32 bytes of data:
Reply from 82.96.119.12: bytes=32 time=185ms TTL=119
Reply from 82.96.119.12: bytes=32 time=188ms TTL=119
Reply from 82.96.119.12: bytes=32 time=188ms TTL=119
Reply from 82.96.119.12: bytes=32 time=188ms TTL=119

I used to get 12ms to eircom.net



Rang eircom to make sure fastpath was enabled and the guy I was speaking too didn't even know what it was. Been on hold for the last 15 minutes

He said there's been another cable break in Wexford, won't hold my breath in suspence

chriss745

Yes, unfortunately the problem still exists depending on the route of the destination network.

Indirect routing is OK:

Tracing route to zeus.jaisz.hu [193.225.219.34]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    56 ms    17 ms    18 ms  95.44.68.1
  3    17 ms    16 ms    16 ms  86.43.59.205
  4    22 ms    21 ms    21 ms  tenge-2-1-1.core2.prp.core.eircom.net [86.43.253.89]
  5     *       37 ms    37 ms  tenge-2-2-1.pe1.the.the-thn.eircom.net [86.43.253.110]
  6    37 ms    37 ms    37 ms  ge7-1-0.corea.the.london.eircom.net [86.43.244.190]
  7    37 ms    37 ms    37 ms  ldn-b1-link.telia.net [213.248.95.1]
  8    37 ms    37 ms    38 ms  ldn-bb2-link.telia.net [80.91.248.94]
  9    49 ms    60 ms    49 ms  hbg-bb2-link.telia.net [80.91.247.200]
 10    68 ms    65 ms    68 ms  win-bb2-link.telia.net [62.115.136.31]
 11    71 ms    97 ms    71 ms  bpt-b4-link.telia.net [213.155.137.41]
 12    73 ms    72 ms    76 ms  dante-ic-130278-bpt-b4.c.telia.net [213.248.79.186]
 13    78 ms    78 ms    78 ms  be2.rtr.sopron.hbone.hu [195.111.111.203]

But if the destination network is directly routed (trunked), it is terrible:

Tracing route to ftp.freepark.org [195.228.252.133]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Router [192.168.0.1]
  2    21 ms    19 ms    80 ms  95.44.68.1
  3    17 ms    17 ms    17 ms  86.43.59.201
  4    22 ms    24 ms    22 ms  86.43.13.177
  5    37 ms    37 ms    37 ms  86.43.11.182
  6    37 ms    36 ms    36 ms  ge0-0-0.corea.thn.london.eircom.net [86.43.245.162]
  7   184 ms     *      174 ms  decix.net.telekom.hu [80.81.194.86]
  8   172 ms   176 ms   177 ms  xe-2-1-0.ic0-ip2.net.telekom.hu [81.183.0.76]
  9   167 ms   169 ms   175 ms  xe-11-3-0.ic1-dplex.net.telekom.hu [81.183.0.251
]

I believe the 86.43.245.162 is on Eircom's network, that router has a very congested connection back to Europe. It is insane that there is no one at Eircom who could know how to solve this trivial problem, it is a shame, it is a simple routing issue...

Hank Scorpio

Been going on for months and still nothing only false promises

eircom: Alan

nuxxx wrote: »

Just gonna post my pings in this thread this evening, hopefully by Saturday this will be resolved. The following are 4 servers from Germany, all different IP's/Server providers.

I'm on 24Mb NGB with fastpath

German server 1

Pinging de1.ut99.pro [80.82.215.118] with 32 bytes of data:
Reply from 80.82.215.118: bytes=32 time=182ms TTL=56
Reply from 80.82.215.118: bytes=32 time=193ms TTL=56
Reply from 80.82.215.118: bytes=32 time=187ms TTL=56
Reply from 80.82.215.118: bytes=32 time=189ms TTL=56

German server 2

Pinging de2.ut99.pro [82.96.119.12] with 32 bytes of data:
Reply from 82.96.119.12: bytes=32 time=181ms TTL=119
Reply from 82.96.119.12: bytes=32 time=187ms TTL=119
Reply from 82.96.119.12: bytes=32 time=187ms TTL=119
Reply from 82.96.119.12: bytes=32 time=187ms TTL=119

German server 3

Pinging de3.ut99.pro [5.62.105.37] with 32 bytes of data:
Reply from 5.62.105.37: bytes=32 time=233ms TTL=56
Reply from 5.62.105.37: bytes=32 time=232ms TTL=56
Reply from 5.62.105.37: bytes=32 time=237ms TTL=56
Reply from 5.62.105.37: bytes=32 time=235ms TTL=56

German server 4

Pinging 176.57.142.9 with 32 bytes of data:
Reply from 176.57.142.9: bytes=32 time=235ms TTL=55
Reply from 176.57.142.9: bytes=32 time=226ms TTL=55
Reply from 176.57.142.9: bytes=32 time=226ms TTL=55
Reply from 176.57.142.9: bytes=32 time=231ms TTL=55

And here's a trace to a uk server, getting routed through Paris

Tracing route to multiplay.co.uk [85.236.96.26]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.254
  2    11 ms    13 ms    11 ms  b-ras2.dbn.dublin.eircom.net [159.134.155.5]
  3    12 ms    12 ms    11 ms  ge-2-1-7.pe1.dbn.cld-dbn.eircom.net [86.43.246.1
57]
  4    15 ms    14 ms    14 ms  tenge-4-1-1.core2.bdt.core.eircom.net [86.43.252
.97]
  5    11 ms    13 ms    11 ms  ge0-0-0.peering1.csg.dublin.eircom.net [86.43.24
5.78]
  6    35 ms    36 ms    37 ms  195.16.170.41
  7    90 ms    90 ms    87 ms  ae-12-12.ebr2.Paris1.Level3.net [4.69.153.242]
  8    88 ms    93 ms    89 ms  ae-82-82.csw3.Paris1.Level3.net [4.69.161.102]
  9    87 ms    89 ms    93 ms  ae-81-81.ebr1.Paris1.Level3.net [4.69.161.85]
 10    91 ms    89 ms    87 ms  ae-1-3.edge3.London2.Level3.net [4.69.141.85]
 11    36 ms    34 ms    34 ms  MULTIPLAY-L.edge3.London2.Level3.net [195.50.125
.6]
 12    96 ms    95 ms    95 ms  ha01.multiplay.co.uk [85.236.96.26]

Hi Nuxx



[font=Times New Roman","serif]I understand you are experiencing congestion like issues and you want to share your ping results to prove this to me to responde to however information as advised on outher threads and websites the best advice I can possibly offer on this is to contact eircom broadband technical support for technical assistance on this when you notice the speeds are slowing down. [/font]


[font=Times New Roman","serif] [/font]
[font=Times New Roman","serif]Technical support can be contacted 7 days a week from 8am to 10pm on free phone 1901 (enter number then chose option 3 then 2) or on 1890260260. We also have a technical support web chat service - follow here for details http://bit.ly/1d4wjku [/font]
[font=Times New Roman","serif] [/font]
[font=Times New Roman","serif] [/font]
[font=Times New Roman","serif]Thanks[/font]
[font=Times New Roman","serif] [/font]
[font=Times New Roman","serif]Al[/font]