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

BT Ping Tonight

Options
  • 13-12-2006 10:49pm
    #1
    Auvers
    Closed Accounts Posts: 2,987 ✭✭✭


    How are your pings on BT tonight? Mine are awful :(
    oh and I am on the swords exchange.

    Pinging ftp.heanet.ie [193.1.193.64] with 32 bytes of data:

    Reply from 193.1.193.64: bytes=32 time=134ms TTL=56
    Reply from 193.1.193.64: bytes=32 time=146ms TTL=56
    Reply from 193.1.193.64: bytes=32 time=131ms TTL=56
    Reply from 193.1.193.64: bytes=32 time=156ms TTL=56

    Ping statistics for 193.1.193.64:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 131ms, Maximum = 156ms, Average = 141ms


Comments

  • Options
    #2
    challengemaster
    Registered Users Posts: 16,930 ✭✭✭✭challengemaster


    mine couldnt be better, best i've had all year. getting 32 ping to dublin UT servers. im in westmeath btw.


  • Options
    #3
    quarryman
    Registered Users Posts: 7,496 ✭✭✭quarryman


    Pinging ftp.heanet.ie [193.1.193.64] with 32 bytes of data:



    Reply from 193.1.193.64: bytes=32 time=18ms TTL=57

    Reply from 193.1.193.64: bytes=32 time=16ms TTL=57

    Reply from 193.1.193.64: bytes=32 time=17ms TTL=57

    Reply from 193.1.193.64: bytes=32 time=16ms TTL=57



    Ping statistics for 193.1.193.64:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 16ms, Maximum = 18ms, Average = 16ms



    I'm in Limerick


  • Options
    #4
    Auvers
    Closed Accounts Posts: 2,987 ✭✭✭Auvers


    Its typical girlfriend is gone out for the night and I was ready for a uninterrupted battlefield 2 session and my ping is gone to sh1te.


  • Options
    #5
    Lockup
    Closed Accounts Posts: 113 ✭✭Lockup


    Auvers, I was seeing bad pings and poor download speeds last night as well. I'm on BT as well but in the Dennehy's Cross in Cork..


  • Options
    #6
    kmick
    Registered Users Posts: 3,375 ✭✭✭kmick


    Mine were awful in Rathgar and I was getting dropped connections as well.


  • Advertisement
  • Options
    #7
    Furp
    Registered Users Posts: 933 ✭✭✭Furp


    Mine where also bad last night, connected on the Navan exchange with BT, and getting pings in the 170-200 range to Jolt.co.uk


  • Options
    #8
    scargill
    Registered Users Posts: 1,679 ✭✭✭scargill


    mine is dire, losing lots of packets I'm in Newbridge - anyone else having similar grief? Is it the weather?

    Pinging 193.1.193.64 with 32 bytes of data:

    Reply from 193.1.193.64: bytes=32 time=25ms TTL=56
    Request timed out.
    Reply from 193.1.193.64: bytes=32 time=26ms TTL=56
    Reply from 193.1.193.64: bytes=32 time=25ms TTL=56

    Ping statistics for 193.1.193.64:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 26ms, Average = 25ms

    Pinging 193.1.193.64 with 32 bytes of data:

    Reply from 193.1.193.64: bytes=32 time=27ms TTL=56
    Reply from 193.1.193.64: bytes=32 time=29ms TTL=56
    Reply from 193.1.193.64: bytes=32 time=24ms TTL=56
    Reply from 193.1.193.64: bytes=32 time=2398ms TTL=56

    Ping statistics for 193.1.193.64:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 24ms, Maximum = 2398ms, Average = 619ms


  • Options
    #9
    Pokes
    Registered Users Posts: 345 ✭✭Pokes


    Mines brutal too.On Bt and in Portlaoise.Keeps lagging for 5 secs at a time on any CSS server i try :(


  • Options
    #10
    BoobeR
    Registered Users Posts: 760 ✭✭✭BoobeR


    Having same problems, 5 second pauses playing CSS every 15seconds avg. I'm on eircom 3mb in midlands, my brother having the same problems on esat 3mb also in midlands.. its not a problem with game either, happening in nexuiz.


  • Options
    #11
    flamegrill
    Registered Users Posts: 1,862 ✭✭✭flamegrill


    In carlow on netsource having the same issue. Been happening since around midday today.

    :/

    http://monster.blacknight.ie/~paul/****sake.png


  • Advertisement
  • Options
    #12
    kleefarr
    Registered Users Posts: 5,743 ✭✭✭kleefarr


    Just done mine.

    Kilkenny exchange.


    Pinging 193.1.193.64 with 32 bytes of data:

    Reply from 193.1.193.64: bytes=32 time=24ms TTL=56
    Reply from 193.1.193.64: bytes=32 time=24ms TTL=56
    Reply from 193.1.193.64: bytes=32 time=39ms TTL=56
    Reply from 193.1.193.64: bytes=32 time=287ms TTL=56

    Ping statistics for 193.1.193.64:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 24ms, Maximum = 287ms, Average = 93ms


  • Options
    #13
    Dundhoone
    Closed Accounts Posts: 710 ✭✭✭Dundhoone


    Having the exact same problem in limerick just now.

    25% loss on ping.
    connection drop every five seconds or so.
    BT must be trying out broadband rationing or summat.


  • Options
    #14
    Auvers
    Closed Accounts Posts: 2,987 ✭✭✭Auvers


    Back to normal tonight :)


    Pinging ftp.heanet.ie [193.1.193.64] with 32 bytes of data:

    Reply from 193.1.193.64: bytes=32 time=25ms TTL=55
    Reply from 193.1.193.64: bytes=32 time=25ms TTL=55
    Reply from 193.1.193.64: bytes=32 time=24ms TTL=55
    Reply from 193.1.193.64: bytes=32 time=25ms TTL=55

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


  • Options
    #15
    Dundhoone
    Closed Accounts Posts: 710 ✭✭✭Dundhoone


    Im Jealous.

    Its still losing one packet in four on ping. :(

    Doubt I'll be getting a refund from BT for poor service................


  • Options
    #16
    flamegrill
    Registered Users Posts: 1,862 ✭✭✭flamegrill


    4825 packets transmitted, 3318 received, +4 errors, 31% packet loss, time 4827425ms

    Eircom dsl line in Carlow. I know Carlow is on the Limerick BAS as when you're looking for the PPPOE concentrator you can see the name come up in the pppoe header.

    So major problem it would seem :/

    Paul


  • Options
    #17
    Pacifico
    Closed Accounts Posts: 5,115 ✭✭✭Pacifico


    Just off the phone with Eircom. Apparently, there is 128dB's attenuation on my line......!

    Told me an engineer will take a look at it.

    Major problem indeed :(


  • Options
    #18
    nd
    Registered Users Posts: 1,855 ✭✭✭nd


    Dundhoone wrote:
    Having the exact same problem in limerick just now.

    25% loss on ping.
    connection drop every five seconds or so.
    BT must be trying out broadband rationing or summat.


    same here but with digiweb....also in limerick



    Pinging dsl.digiweb.ie [217.114.163.194] with 32 bytes of data:

    Request timed out.
    Reply from 217.114.163.194: bytes=32 time=18ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=17ms TTL=124
    Reply from 217.114.163.194: bytes=32 time=18ms TTL=124

    Ping statistics for 217.114.163.194:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 18ms, Average = 17ms


    almost everytime I try it


  • Options
    #19
    Pacifico
    Closed Accounts Posts: 5,115 ✭✭✭Pacifico


    Be sure to let your ISPs know, the more complains the quicker it should be rectified!


  • Options
    #20
    jonski
    Registered Users Posts: 6,393 ✭✭✭jonski


    On Eircom , in Limerick , having problems tonight aswell


  • Options
    #21
    Lucutus
    Registered Users Posts: 2,831 ✭✭✭Lucutus


    BT Ping problems myself tonight... 
    C:\>ping ireland.com -t

Pinging ireland.com [195.7.33.36] with 32 bytes of data:

Request timed out.
Reply from 195.7.33.36: bytes=32 time=19ms TTL=247
Reply from 195.7.33.36: bytes=32 time=19ms TTL=247
Reply from 195.7.33.36: bytes=32 time=19ms TTL=247
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Request timed out.
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Reply from 195.7.33.36: bytes=32 time=18ms TTL=247
Reply from 195.7.33.36: bytes=32 time=19ms TTL=247
Reply from 195.7.33.36: bytes=32 time=19ms TTL=247
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Request timed out.
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Reply from 195.7.33.36: bytes=32 time=18ms TTL=247
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Reply from 195.7.33.36: bytes=32 time=19ms TTL=247
Reply from 195.7.33.36: bytes=32 time=19ms TTL=247
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Request timed out.
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Reply from 195.7.33.36: bytes=32 time=18ms TTL=247
Reply from 195.7.33.36: bytes=32 time=18ms TTL=247
Reply from 195.7.33.36: bytes=32 time=19ms TTL=247
Reply from 195.7.33.36: bytes=32 time=3143ms TTL=247
Reply from 195.7.33.36: bytes=32 time=29ms TTL=247
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Reply from 195.7.33.36: bytes=32 time=18ms TTL=247
Reply from 195.7.33.36: bytes=32 time=18ms TTL=247
Reply from 195.7.33.36: bytes=32 time=18ms TTL=247
Reply from 195.7.33.36: bytes=32 time=19ms TTL=247
Reply from 195.7.33.36: bytes=32 time=19ms TTL=247
Reply from 195.7.33.36: bytes=32 time=20ms TTL=247
Reply from 195.7.33.36: bytes=32 time=3129ms TTL=247


C:\>ping microsoft.com -t

Pinging microsoft.com [207.46.197.32] with 32 bytes of data:

Reply from 207.46.197.32: bytes=32 time=191ms TTL=110
Reply from 207.46.197.32: bytes=32 time=192ms TTL=110
Reply from 207.46.197.32: bytes=32 time=3272ms TTL=110
Reply from 207.46.197.32: bytes=32 time=192ms TTL=110
Reply from 207.46.197.32: bytes=32 time=191ms TTL=110
Reply from 207.46.197.32: bytes=32 time=192ms TTL=110
Reply from 207.46.197.32: bytes=32 time=195ms TTL=110
Reply from 207.46.197.32: bytes=32 time=192ms TTL=110
Reply from 207.46.197.32: bytes=32 time=196ms TTL=110
Reply from 207.46.197.32: bytes=32 time=191ms TTL=110
Reply from 207.46.197.32: bytes=32 time=191ms TTL=110
Reply from 207.46.197.32: bytes=32 time=199ms TTL=110
Request timed out.
Reply from 207.46.197.32: bytes=32 time=191ms TTL=110
Reply from 207.46.197.32: bytes=32 time=191ms TTL=110
Reply from 207.46.197.32: bytes=32 time=194ms TTL=110
Reply from 207.46.197.32: bytes=32 time=192ms TTL=110
Reply from 207.46.197.32: bytes=32 time=193ms TTL=110
Reply from 207.46.197.32: bytes=32 time=3252ms TTL=110

    :(


  • Advertisement
  • Options
    #22
    Champ
    Registered Users Posts: 677 ✭✭✭Champ


    Joining the club. Eircom 3Meg Limerick.
    Last night loosing 25% of packets. Never had this problem before. Though the packets that were making it through were fast at 15 - 17 ms.

    Interestingly i did a ping on Eircom Primary DNS and had no problems what so ever.
    Tried the secondary and boom crash burn, loosing packets and one round trip even took 3000ms!


  • Options
    #23
    Ludo
    Registered Users Posts: 5,015 ✭✭✭Ludo


    Have BT in Bray and was very happy with it for the last 6 months. However, I too have noticed in the last two weeks that the ping during game play is gone to hell. Very erratic with lost connection regularly. BB connection drops altogether now a couple of times every evening also.

    I guess it is a general problem they are having.


  • Options
    #24
    flamegrill
    Registered Users Posts: 1,862 ✭✭✭flamegrill


    fixed itself for us around midnight last night ... no problems since.

    Paul


  • Options
    #25
    Pacifico
    Closed Accounts Posts: 5,115 ✭✭✭Pacifico


    Yep fine again :)


  • Options
    #26
    Furp
    Registered Users Posts: 933 ✭✭✭Furp


    Yep the ping times are looking good again in Navan.
    Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=37ms TTL=55
Reply from 82.133.85.65: bytes=32 time=40ms TTL=55
Reply from 82.133.85.65: bytes=32 time=40ms TTL=55
Reply from 82.133.85.65: bytes=32 time=42ms TTL=55


Advertisement