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
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Esat poor pings - tuesday 21:15 ?

  • 14-03-2006 9:13pm
    #1
    Gavin
    Registered Users, Registered Users 2 Posts: 4,676 ✭✭✭


    Anyone having troubles with EsatBT pingwise at the moment? I'm getting bad pings from the first hop on.

    Tracing route to www.esat.com [193.95.153.20]
    over a maximum of 30 hops:

    1 2 ms 2 ms 2 ms 192.168.1.1
    2 131 ms 123 ms 124 ms bas502.cwt.esat.net [193.95.136.238]
    3 82 ms 84 ms 90 ms vlan500.rt501.cwt.esat.net [193.95.136.124]
    4 90 ms 84 ms 76 ms vlan53.rt002.cwt.esat-x.com [193.95.130.153]
    5 19 ms 23 ms 23 ms vlan73.rt701.cwt.esat.net [193.95.130.218]
    6 41 ms 38 ms 36 ms 193.95.153.20
    7 63 ms 53 ms 55 ms 193.95.153.20

    Trace complete.

    Pinging lo1.bas502.cwt.esat.net [193.95.136.238] with 32 bytes of data:

    Reply from 193.95.136.238: bytes=32 time=117ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=127ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=146ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=168ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=173ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=138ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=171ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=178ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=187ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=161ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=169ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=156ms TTL=254
    Reply from 193.95.136.238: bytes=32 time=193ms TTL=254

    Ping statistics for 193.95.136.238:
    Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 117ms, Maximum = 193ms, Average = 160ms

    I've noticed this happening a bit in the evenings lately.


Comments

  • #2
    anthonymcg
    Registered Users, Registered Users 2 Posts: 660 ✭✭✭anthonymcg


    Mine are fine and as expected. From Lucan though.


  • #3
    DemonOfTheFall
    Closed Accounts Posts: 2,279 ✭✭✭DemonOfTheFall


    I'm not on BT any more but I got the same thing after the 2meg upgrades last spring.

    Try ringing BT and whining, they'll tell you its the quality of the phone line between you and the exchange tho, irrespective of the fact that it only happens in the evening. Muppets.


  • #4
    DonkeyStyle \o/
    Closed Accounts Posts: 7,145 ✭✭✭DonkeyStyle \o/


    Was getting rubbish pings on monday evening alright... wasn't on yesterday, so I'm not sure if there was a repeat performance. :rolleyes:


Advertisement