Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Pings to Boards.ie and Irish servers bad again

  • 23-02-2004 4:29pm
    #1
    Gonzo
    Moderators, Science, Health & Environment Moderators Posts: 16,940 Mod ✭✭✭✭


    It seems pings to boards.ie and many irish servers are bad again today however servers in the UK and beyond are unaffected. Im on eircom and this happened for a while last Friday too.

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

    Reply from 82.195.131.128: bytes=32 time=294ms TTL=58
    Reply from 82.195.131.128: bytes=32 time=302ms TTL=58
    Reply from 82.195.131.128: bytes=32 time=285ms TTL=58
    Reply from 82.195.131.128: bytes=32 time=278ms TTL=58

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

    C:\Documents and Settings\Barry>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=36ms TTL=57
    Reply from 195.149.21.11: bytes=32 tim=36ms TTL=57
    Reply from 195.149.21.11: bytes=32 time=35ms TTL=57
    Reply from 195.149.21.11: bytes=32 time=35ms 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 = 35ms, Maximum = 36ms, Average = 35ms


Comments

  • #2
    Xcellor
    Registered Users, Registered Users 2 Posts: 2,806 ✭✭✭Xcellor


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

    Reply from 82.195.131.128: bytes=32 time=173ms TTL=54
    Reply from 82.195.131.128: bytes=32 time=161ms TTL=54
    Reply from 82.195.131.128: bytes=32 time=137ms TTL=54
    Reply from 82.195.131.128: bytes=32 time=162ms TTL=54

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

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

    Reply from 195.149.21.11: bytes=32 time=97ms TTL=55
    Reply from 195.149.21.11: bytes=32 time=117ms TTL=55
    Reply from 195.149.21.11: bytes=32 time=135ms TTL=55
    Reply from 195.149.21.11: bytes=32 time=140ms 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 = 97ms, Maximum = 140ms, Average = 122ms


    I was getting pings as high as 350... Brutal BRUTAL BRUTAL...

    Wish they would ever plug the hole or whatever that is causing this slow down...
    Least I know im not the only one...

    Finally got our line fixed today and I was hoping for the fastest pings ever har har har WISHFUL THINKING....

    Xcellor

    P.S I am on IOL BB :P


  • #3
    Ripwave
    Closed Accounts Posts: 2,188 ✭✭✭Ripwave


    Originally posted by Xcellor
    Wish they would ever plug the hole or whatever that is causing this slow down...
    If you posted a traceroute instead of a useless ping, someone might be able to tell you where the problem is.


  • #4
    Xcellor
    Registered Users, Registered Users 2 Posts: 2,806 ✭✭✭Xcellor


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

    1 2 ms 2 ms 2 ms 192.168.1.1
    2 350 ms 362 ms 346 ms lo3.bas501.cwt.esat.net [193.95.136.175]
    3 313 ms 296 ms 311 ms vlan501.rt501.cwt.esat.net [193.95.137.124]
    4 288 ms 309 ms 290 ms vlan51.rt001.cwt.esat.net [193.95.130.137]
    5 326 ms 314 ms 349 ms ge1-0.core002.cwt.esat.net [193.95.129.2]
    6 316 ms 305 ms 302 ms pos2-0.br001.inex.esat.net [193.95.131.6]
    7 291 ms 308 ms 295 ms rt001inx.netsource.ie [193.1.208.199]
    8 311 ms 305 ms 314 ms suez.hosting365.ie [212.17.63.4]
    9 303 ms 323 ms 322 ms eventhorizon.hosting365.ie [82.195.133.195]
    10 245 ms 242 ms 244 ms boards.ie [82.195.131.128]

    Trace complete.


    Looks terrible all the way....


  • #5
    Gonzo
    Moderators, Science, Health & Environment Moderators Posts: 16,940 Mod ✭✭✭✭Gonzo


    >tracert www.boards.ie

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

    1 1 ms <1 ms <1 ms 192.168.1.254
    2 24 ms 21 ms 24 ms 83-70-64-1.bas2.srl.dublin.eircom.net [83.70.64.
    1]
    3 23 ms 21 ms 24 ms fe0-0.edge1.srl.dublin.eircom.net [159.134.155.6
    5]
    4 354 ms 344 ms 357 ms atm4-0-39.peering1.inex.dublin.eircom.net [159.1
    34.191.126]
    5 336 ms 346 ms 339 ms rt001inx.netsource.ie [193.1.208.199]
    6 298 ms 286 ms 274 ms suez.hosting365.ie [212.17.63.4]
    7 322 ms 314 ms 310 ms eventhorizon.hosting365.ie [82.195.133.195]
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.

    still fine to uk tho

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

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

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

    1 <1 ms <1 ms <1 ms 192.168.1.254
    2 23 ms 21 ms 24 ms 83-70-64-1.bas2.srl.dublin.eircom.net [83.70.64.
    1]
    3 24 ms 24 ms 24 ms fe0-0.edge1.srl.dublin.eircom.net [159.134.155.6
    5]
    4 36 ms 37 ms 34 ms pos0-0.corea.thn.london.eircom.net [159.134.191.
    234]
    5 35 ms 36 ms 34 ms lon1-9.nildram.net [195.66.224.59]
    6 37 ms 34 ms 37 ms jolt-gw.nildram.net [195.149.20.126]


  • #6
    Xcellor
    Registered Users, Registered Users 2 Posts: 2,806 ✭✭✭Xcellor


    Pinging www.365hosting.ie [82.195.128.250] with 32 bytes of data:

    Reply from 82.195.128.250: bytes=32 time=901ms TTL=55
    Reply from 82.195.128.250: bytes=32 time=952ms TTL=55
    Reply from 82.195.128.250: bytes=32 time=979ms TTL=55
    Reply from 82.195.128.250: bytes=32 time=1005ms TTL=55

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

    Wow.... never had that on BB before...


  • Advertisement
  • #7
    Gonzo
    Moderators, Science, Health & Environment Moderators Posts: 16,940 Mod ✭✭✭✭Gonzo


    yeah big problems with irish servers alrite. tryed 365hosting and digiweb. Still getting silky smooth pings from english game servers.

    Pinging www.365hosting.ie [82.195.128.250] with 32 bytes of data:

    Reply from 82.195.128.250: bytes=32 time=438ms TTL=58
    Reply from 82.195.128.250: bytes=32 time=427ms TTL=58
    Reply from 82.195.128.250: bytes=32 time=452ms TTL=58
    Reply from 82.195.128.250: bytes=32 time=475ms TTL=58

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

    Pinging www.digiweb.ie [217.114.163.199] with 32 bytes of data:

    Reply from 217.114.163.199: bytes=32 time=496ms TTL=121
    Reply from 217.114.163.199: bytes=32 time=478ms TTL=121
    Reply from 217.114.163.199: bytes=32 time=492ms TTL=121
    Reply from 217.114.163.199: bytes=32 time=489ms TTL=121

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


  • #8
    Gonzo
    Moderators, Science, Health & Environment Moderators Posts: 16,940 Mod ✭✭✭✭Gonzo


    and heres the isps, couldnt ping esat or iol tho.

    Pinging home.eircom.net [159.134.198.138] with 32 bytes of data:

    Reply from 159.134.198.138: bytes=32 time=24ms TTL=60
    Reply from 159.134.198.138: bytes=32 time=23ms TTL=60
    Reply from 159.134.198.138: bytes=32 time=27ms TTL=60
    Reply from 159.134.198.138: bytes=32 time=27ms TTL=60

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

    Pinging www.utv.ie [194.46.8.120] with 32 bytes of data:

    Reply from 194.46.8.120: bytes=32 time=56ms TTL=52
    Reply from 194.46.8.120: bytes=32 time=62ms TTL=52
    Reply from 194.46.8.120: bytes=32 time=54ms TTL=52
    Reply from 194.46.8.120: bytes=32 time=58ms TTL=52

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

    Pinging www.netsource.ie [212.17.32.48] with 32 bytes of data:

    Reply from 212.17.32.48: bytes=32 time=422ms TTL=123
    Reply from 212.17.32.48: bytes=32 time=387ms TTL=123
    Reply from 212.17.32.48: bytes=32 time=381ms TTL=123
    Reply from 212.17.32.48: bytes=32 time=413ms TTL=123

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

    Pinging 365.ie [82.195.128.250] with 32 bytes of data:

    Reply from 82.195.128.250: bytes=32 time=606ms TTL=58
    Reply from 82.195.128.250: bytes=32 time=614ms TTL=58
    Reply from 82.195.128.250: bytes=32 time=580ms TTL=58
    Reply from 82.195.128.250: bytes=32 time=591ms TTL=58

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

    Pinging www.ntlworld.com [62.253.162.30] with 32 bytes of data:

    Reply from 62.253.162.30: bytes=32 time=44ms TTL=247
    Reply from 62.253.162.30: bytes=32 time=46ms TTL=247
    Reply from 62.253.162.30: bytes=32 time=47ms TTL=247
    Reply from 62.253.162.30: bytes=32 time=42ms TTL=247

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


  • #9
    sixpack's little hat
    Registered Users, Registered Users 2 Posts: 819 ✭✭✭sixpack's little hat


    C:\Documents and Settings\feargal>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=540ms TTL=57
    Reply from 195.149.21.11: bytes=32 time=474ms TTL=57
    Reply from 195.149.21.11: bytes=32 time=468ms TTL=57
    Reply from 195.149.21.11: bytes=32 time=494ms 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 = 468ms, Maximum = 540ms, Average = 494ms


    IOL BB


  • #10
    Tazzle
    Hosted Moderators Posts: 2,563 ✭✭✭Tazzle


    Netsource RADSL - Pings are perfect for me anyway.. Eircom is completely shagged routing inside Ireland..

    365.ie
    Tracing route to 365.ie [82.195.128.250]
    over a maximum of 30 hops:

    1 26 ms 26 ms 25 ms rt004dub.netsource.ie [213.79.63.254]
    2 29 ms 25 ms 25 ms rt001dub.netsource.ie [212.17.32.97]
    3 32 ms 28 ms 29 ms rt001kil.netsource.ie [212.17.32.101]
    4 29 ms 30 ms 32 ms suez.hosting365.ie [212.17.63.4]
    5 29 ms 36 ms 28 ms happy.hosting365.ie [82.195.128.9]
    6 31 ms 32 ms 32 ms hosting365.ie [82.195.128.250]

    IOL
    Tracing route to games1.iol.ie [193.120.123.136]
    over a maximum of 30 hops:

    1 26 ms 29 ms 29 ms rt004dub.netsource.ie [213.79.63.254]
    2 27 ms 28 ms 27 ms rt001dub.netsource.ie [212.17.32.97]
    3 30 ms 27 ms 28 ms rt001kil.netsource.ie [212.17.32.101]
    4 29 ms 27 ms 31 ms fe0-0.br001.inex.esat.net [193.1.208.194]
    5 30 ms 30 ms 31 ms pos2-3.core002.cwt.esat.net [193.95.131.5]
    6 28 ms 31 ms 31 ms vlan2.rt001.cwt.esat-x.com [193.95.129.3]
    7 28 ms 32 ms 31 ms vlan57.rt508.cwt.esat.net [193.95.132.26]
    8 29 ms 32 ms 33 ms games1.iol.ie [193.120.123.136]

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

    1 28 ms 26 ms 28 ms rt004dub.netsource.ie [213.79.63.254]
    2 27 ms 25 ms 26 ms rt001dub.netsource.ie [212.17.32.97]
    3 30 ms 29 ms 29 ms rt001kil.netsource.ie [212.17.32.101]
    4 32 ms 31 ms 30 ms suez.hosting365.ie [212.17.63.4]
    5 33 ms 33 ms 32 ms eventhorizon.hosting365.ie [82.195.133.195]
    6 31 ms 32 ms 33 ms boards.ie [82.195.131.128]

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

    1 28 ms 25 ms 26 ms rt004dub.netsource.ie [213.79.63.254]
    2 28 ms 29 ms 28 ms rt001dub.netsource.ie [212.17.32.97]
    3 28 ms 28 ms 29 ms rt001kil.netsource.ie [212.17.32.101]
    4 31 ms 29 ms 30 ms rt002kil.as9196.net [212.17.63.3]
    5 31 ms 32 ms 30 ms t3-4-2-0.ar1.dub1.gblx.net [64.213.22.253]
    6 42 ms 43 ms 45 ms so6-0-0-2488M.cr2.LON3.gblx.net [67.17.66.25]
    7 40 ms 41 ms 41 ms pos6-1-622M.ar2.LON2.gblx.net [67.17.92.150]
    8 45 ms 40 ms 42 ms lon1-9.nildram.net [195.66.224.59]
    9 44 ms 42 ms 42 ms jolt-gw.nildram.net [195.149.20.126]
    10 42 ms 43 ms 41 ms clarity.jolt.co.uk [195.149.21.11]

    Eircom
    Here's where the problem begins! and a tracert won't work so here's the ping times..

    Pinging home.eircom.net [159.134.198.138] with 32 bytes of data:

    Reply from 159.134.198.138: bytes=32 time=467ms TTL=59
    Reply from 159.134.198.138: bytes=32 time=490ms TTL=59
    Reply from 159.134.198.138: bytes=32 time=446ms TTL=59
    Reply from 159.134.198.138: bytes=32 time=473ms TTL=59

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


  • #11
    ando
    Registered Users, Registered Users 2 Posts: 5,427 ✭✭✭ando


    Oh my, boards.ie is pretty slow for me. My router has disconnected twice in 5 mins

    ping www.boards.ie

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

    Reply from 82.195.131.128: bytes=32 time=764ms TTL=58
    Reply from 82.195.131.128: bytes=32 time=793ms TTL=58
    Reply from 82.195.131.128: bytes=32 time=808ms TTL=58
    Reply from 82.195.131.128: bytes=32 time=797ms TTL=58

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


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

    1 <1 ms <1 ms <1 ms 10.0.0.254
    2 20 ms 19 ms 16 ms 83-70-64-1.bas2.srl.dublin.eircom.net [83.70.64.
    1]
    3 17 ms 19 ms 20 ms ge0-1.edge1.srl.dublin.eircom.net [159.134.155.6
    5]
    4 766 ms 756 ms 758 ms atm4-0-39.peering1.inex.dublin.eircom.net [159.1
    34.191.126]
    5 727 ms 709 ms 687 ms rt001inx.netsource.ie [193.1.208.199]
    6 732 ms 760 ms 762 ms suez.hosting365.ie [212.17.63.4]
    7 764 ms 760 ms 752 ms eventhorizon.hosting365.ie [82.195.128.8]
    8 * * * Request timed out.


    Problem is obviously 3rd to 4th hop, going onto INEX. UK pings are fine for me to, they do not go through INEX:

    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=32ms TTL=57
    Reply from 195.149.21.11: bytes=32 time=30ms TTL=57
    Reply from 195.149.21.11: bytes=32 time=30ms 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 = 30ms, Maximum = 32ms, Average = 31ms


  • Advertisement
  • #12
    ando
    Registered Users, Registered Users 2 Posts: 5,427 ✭✭✭ando


    so whoever goes through INEX are having a bad time with Pings ... ?


  • #13
    Xcellor
    Registered Users, Registered Users 2 Posts: 2,806 ✭✭✭Xcellor


    Phoned Esat.... and gave out about the crap. They tried to blame contention blah blah... and I said unless 1000 people had signed onto my exchange and were downloading constantly there was nothing that could account for the HUGE pings... He was taken back and didn't know how to escape... They say there is nothing wrong with their servers...

    Anyhowz pings are back to normal....

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

    Reply from 82.195.131.128: bytes=32 time=33ms TTL=54
    Reply from 82.195.131.128: bytes=32 time=43ms TTL=54
    Reply from 82.195.131.128: bytes=32 time=33ms TTL=54
    Reply from 82.195.131.128: bytes=32 time=31ms TTL=54

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


  • #14
    crawler
    Registered Users, Registered Users 2 Posts: 1,660 ✭✭✭crawler


    Does anyone know what capacity eircom and EsatBT have to INEX and LINX?

    Some of them there pings are AWFUL


  • #15
    Ripwave
    Closed Accounts Posts: 2,188 ✭✭✭Ripwave


    Originally posted by Gonzo
    > 3 23 ms 21 ms 24 ms fe0-0.edge1.srl.dublin.eircom.net
    4 354 ms 344 ms 357 ms atm4-0-39.peering1.inex.dublin.eircom.net
    Ahh! Now that's interesting. It looks like there's a problem at Inex (the Irish Internet Exchange, where Irish ISPs peer with one another). Or a problem with the link between Inex and eircom at least.

    3 24 ms 24 ms 24 ms fe0-0.edge1.srl.dublin.eircom.net
    4 36 ms 37 ms 34 ms pos0-0.corea.thn.london.eircom.net
    This one doesn't go through Inex, so there's no delay.

    This is why a traceroute is useful in this sort of case. A few traceroutes fom UTV or IOL users through Inex would help tell whether it's an Inex problem, or a problem with eircoms link to Inex.


  • #16
    Ro
    Closed Accounts Posts: 151 ✭✭Ro


    I think the problem was Eircom.net's connection to the INEX. I was getting 35Mb/s through the INEX earlier to Esat, but only 400KB/s to Eircom. I can get 8Mb/s through eircom.net at the moment.

    There was a problem with Eircoms connection to the INEX on Friday too, it went down at about 5pm.


  • #17
    Ripwave
    Closed Accounts Posts: 2,188 ✭✭✭Ripwave


    Originally posted by Xcellor
    They say there is nothing wrong with their servers...
    That's because there isn't anything wrong with their servers.


  • #18
    Ripwave
    Closed Accounts Posts: 2,188 ✭✭✭Ripwave


    Originally posted by crawler
    Does anyone know what capacity eircom and EsatBT have to INEX and LINX?
    That doesn't look like a capacity issue. Pings like that are ususally due to some screwed up router.


  • #19
    Xcellor
    Registered Users, Registered Users 2 Posts: 2,806 ✭✭✭Xcellor


    I dont feel so bad now I know I'm not alone in this ahahah... but at the moment pings are looking good...

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

    Reply from 82.195.131.128: bytes=32 time=32ms TTL=54
    Reply from 82.195.131.128: bytes=32 time=35ms TTL=54
    Reply from 82.195.131.128: bytes=32 time=30ms TTL=54
    Reply from 82.195.131.128: bytes=32 time=33ms TTL=54

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

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

    Reply from 195.149.21.11: bytes=32 time=43ms TTL=55
    Reply from 195.149.21.11: bytes=32 time=41ms TTL=55
    Reply from 195.149.21.11: bytes=32 time=41ms TTL=55
    Reply from 195.149.21.11: bytes=32 time=42ms 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 = 41ms, Maximum = 43ms, Average = 41ms


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

    1 <1 ms <1 ms <1 ms server.mshome.net [192.168.0.1]
    2 2 ms 3 ms 2 ms 192.168.1.1
    3 30 ms 28 ms 29 ms lo3.bas501.cwt.esat.net [193.95.136.175]
    4 29 ms 28 ms 79 ms vlan501.rt502.cwt.esat.net [193.95.137.125]
    5 32 ms 27 ms 28 ms vlan52.rt001.cwt.esat.net [193.95.130.145]
    6 43 ms 46 ms 41 ms ge1-0.core002.cwt.esat.net [193.95.129.2]
    7 45 ms 48 ms 39 ms pos2-0.br001.inex.esat.net [193.95.131.6]
    8 35 ms 34 ms 31 ms rt001inx.netsource.ie [193.1.208.199]
    9 32 ms 32 ms 35 ms suez.hosting365.ie [212.17.63.4]
    10 33 ms 35 ms 31 ms eventhorizon.hosting365.ie [82.195.128.8]
    11 40 ms 34 ms 32 ms boards.ie [82.195.131.128]

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

    1 <1 ms <1 ms <1 ms server.mshome.net [192.168.0.1]
    2 3 ms 2 ms 2 ms 192.168.1.1
    3 51 ms 35 ms 28 ms lo3.bas501.cwt.esat.net [193.95.136.175]
    4 37 ms 29 ms 35 ms vlan501.rt501.cwt.esat.net [193.95.137.124]
    5 68 ms 64 ms 59 ms vlan53.rt002.cwt.esat-x.com [193.95.130.153]
    6 47 ms 56 ms 45 ms ge1-0.core001.cwt.esat.net [193.95.129.17]
    7 82 ms 80 ms 110 ms pos2-0.br001.ldn.esat.net [193.95.131.14]
    8 86 ms 80 ms 72 ms lon1-9.nildram.net [195.66.224.59]
    9 53 ms 49 ms 42 ms jolt-gw.nildram.net [195.149.20.126]
    10 43 ms 45 ms 48 ms clarity.jolt.co.uk [195.149.21.11]

    Trace complete.





    Do you ever worry we might DOS jolt.co.uk and boards.ie with the volume of pings we send their way heh

    Xcellor


  • #20
    Ro
    Closed Accounts Posts: 151 ✭✭Ro


    Originally posted by Ripwave
    That doesn't look like a capacity issue. Pings like that are ususally due to some screwed up router.

    It could be a capacity problem, if a link is saturated then it takes longer to pass through it, so the latency will increase.


  • #21
    Moriarty
    Registered Users, Registered Users 2 Posts: 6,007 ✭✭✭Moriarty


    Originally posted by Ripwave
    That's because there isn't anything wrong with their servers.
    From the trace Xcellor pasted there is - or at least theres a problem somewhere along the line between his house and esats border router for the eircom dsl backhaul network. I find it unlikely that eircom route all dsl traffic for other carriers through the inex..

    It seems as though there are (were) two distinctly seperate problems.


  • Advertisement
  • #22
    Ripwave
    Closed Accounts Posts: 2,188 ✭✭✭Ripwave


    Originally posted by Ro
    It could be a capacity problem, if a link is saturated then it takes longer to pass through it, so the latency will increase.
    They don't increase from 32ms to 400 ms, Ro. Exceeding the capacity of a link can certainly increase latency, but the links to Inex are, almost by definition, pretty big to begin with, so the sort of increase you'd need to cause that kind of degradation can be ruled out. It's far more likely to have been a hardware fault.


  • #23
    Ripwave
    Closed Accounts Posts: 2,188 ✭✭✭Ripwave


    Originally posted by Moriarty
    From the trace Xcellor pasted there is - or at least theres a problem somewhere along the line between his house and esats border router for the eircom dsl backhaul network. I find it unlikely that eircom route all dsl traffic for other carriers through the inex..

    It seems as though there are (were) two distinctly seperate problems.
    We don't know that there was a problem in Inex. We only know that there was a problem getting data from eircom to inex. Links from eircom to Inex - fubar. Links from eircoms DSL network to Esat - fubar.

    Which is more likely, two completely unrelated problems with pretty much the same symptoms, or a screwup somehwere in eircoms network that affected outbound connections from part of eircoms network?

    I know where my money says the problem was, based on the evidence available.


  • #24
    Moriarty
    Registered Users, Registered Users 2 Posts: 6,007 ✭✭✭Moriarty


    I never said there was a problem in inex. How do you explain netsource services being unaffected if youre attributing the same problem to both symptoms?


  • #25
    Ripwave
    Closed Accounts Posts: 2,188 ✭✭✭Ripwave


    Originally posted by Moriarty
    I never said there was a problem in inex. How do you explain netsource services being unaffected if youre attributing the same problem to both symptoms?
    ESAT and Netsource don't necessarily connect to eircom in the same location, so they wouldn't necessarily be affected by the problem.

    As I said, my "diagnosis" for want of a better word, is based on the available information. The information from a netsource poster doesn't really change anything.


Advertisement