IOL Broadband 150ms pings

Diabolus

More the merrier.

TimTim

I only get an occasional spike, nothing too major, but I've noticed they are getting slightly more visable. My brother is complaining now that his CS and FL games are getting laggy. between 5pm after 9pm-ish it clears up. So I'm assuming its a bandwith problem

Here is some tracert results only taken a few seconds ago.

C:\Documents and Settings\Conor>tracert jolt.co.uk

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    23 ms    23 ms    22 ms  bas503.cwt.esat.net [193.95.136.239]
  3    23 ms    24 ms    24 ms  vlan501.rt502.cwt.esat.net [193.95.137.125]
  4    22 ms    24 ms    21 ms  vlan52.rt001.cwt.esat.net [193.95.130.145]
  5    22 ms    23 ms    25 ms  ge0-0.core001.cwt.esat.net [193.95.129.1]
  6    33 ms    36 ms    36 ms  pos2-0.br001.ldn.esat.net [193.95.131.14]
  7    34 ms    36 ms    36 ms  lon1-9.nildram.net [195.66.224.59]
  8    36 ms    35 ms    36 ms  jolt-gw.nildram.net [195.149.20.126]
  9    36 ms    49 ms    35 ms  clarity.jolt.co.uk [195.149.21.11]

Trace complete.

C:\Documents and Settings\Conor>tracert pie.boards.ie

Tracing route to pie.boards.ie [82.195.131.129]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    22 ms    21 ms    23 ms  bas503.cwt.esat.net [193.95.136.239]
  3    30 ms   101 ms   133 ms  vlan501.rt501.cwt.esat.net [193.95.137.124]
  4   390 ms    22 ms    22 ms  vlan53.rt002.cwt.esat-x.com [193.95.130.153]
  5    21 ms    22 ms    24 ms  ge0-0.core002.cwt.esat.net [193.95.129.18]
  6    90 ms   244 ms    72 ms  pos2-0.br001.inex.esat.net [193.95.131.6]
  7    29 ms    67 ms    27 ms  panama-inex.hosting365.ie [193.1.208.234]
  8    27 ms    24 ms    27 ms  sneezy.hosting365.ie [82.195.128.8]
  9    32 ms    43 ms    47 ms  boards.ie [82.195.131.129]

Trace complete.

C:\Documents and Settings\Conor>tracert burstfire.net

Tracing route to burstfire.net [195.22.128.20]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms  192.168.0.1
2    24 ms    22 ms    22 ms  bas503.cwt.esat.net [193.95.136.239]
3    21 ms    23 ms    24 ms  vlan501.rt502.cwt.esat.net [193.95.137.125]
4    22 ms    22 ms    23 ms  vlan54.rt002.cwt.esat-x.com [193.95.130.161]
5    23 ms    23 ms    23 ms  ge1-0.core001.cwt.esat.net [193.95.129.17]
6    34 ms    37 ms    34 ms  pos2-0.br001.ldn.esat.net [193.95.131.14]
7    34 ms    35 ms    33 ms  linx-gw0.enta.net [195.66.224.151]
8    35 ms    38 ms    33 ms  fe-3-1-cr2.sov.as25492.net [193.109.219.138]
9   242 ms    35 ms    35 ms fe-0-1-700-vanadium.as25492.net
[82.136.0.203]
10    38 ms    33 ms    37 ms  platinum.burstfire.net [195.22.128.20]

Trace complete.

Is1ldur

Thanks Diabolus, You presence on the Boards is appreciated. I emailed last night (without my details) and received a response. Details on the way now.
Thanks again.
By the way, pinging fine now, but as others have said, when I actually get down to some playing later on, it will shoot up.

cuppa

Id say we all got the same reply,,,I wonder is it all the new free trails.Im sure they will fix it quick,cos its not good buisness for getting new users who are on the 3 month trail.

reply from iol
"This problem may due to a contention ratio of 48:1 on the service (24:1 on Broadband Plus). What this means is that you are sharing the same DSL line with 47 other users in your area or 23 in the case of Broadband Plus. If any or all of these users are online at the same time as you, your connection speeds will drop. How much depends on the number of users online at that time. This is stated in the Terms & Conditions of the service. However, we are concerned with the experience you are having with our broadband service and are investigating this matter further in an effort improve your broadband experience."

Saruman

Iol here.. fine or me in d20
Pinging boards.ie [82.195.131.130] with 32 bytes of data:

Reply from 82.195.131.130: bytes=32 time=16ms TTL=58
Reply from 82.195.131.130: bytes=32 time=31ms TTL=58
Reply from 82.195.131.130: bytes=32 time=16ms TTL=58
Reply from 82.195.131.130: bytes=32 time=31ms TTL=58

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

C:\Documents and Settings\saruman>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=31ms TTL=57
Reply from 195.149.21.11: bytes=32 time=31ms TTL=57
Reply from 195.149.21.11: bytes=32 time=47ms 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

vishal

hi, i can't get my pings to work. it used to work and i think it stopped working when i reset my router. any help? i have a 623R-T1 router.

conor-mr2

vishal wrote:

hi, i can't get my pings to work. it used to work and i think it stopped working when i reset my router. any help? i have a 623R-T1 router.

Log into your the web administration interface screen on the router.
Goto Security
Untick the box for allowing pings from the wan to the lan
apply settings and it should work.

vishal

thanks, works now

Diabolus

Issue was resolved last night.
Can you all do the tracerts again tonight?

Thanks.

Collina

Seemed pretty good to me last night - got the occasional timeout doing a tracert, but by and large back to normal.

Thanks for info and time you put in on this, Diabolus.

Any word on what was the cause ? Contention Issues ? Faulty Hubs ?

[DF]Lenny

Hope its sorted out know .WP Diabolus (although the last time I had a problem with Esat they gave me 2 months free ...which was nice)

conor-mr2

Got a call today from a chap called Paul at Esat saying the issue was resolved. I wasnt home at the time and my father took the call. Said I could ring him back if I wished.
Good service Im happy with that. Ill retry ping and traceroutes tonight.

Diabolus

Seems to be resolved.
Try the tracerts. ??

animaal

Credit where credit's due. Thanks Diabolus, your efforts are appreciated!

Diabolus

No problem.

Yay now im on a Distinguished road