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

NTL High Pings - Anyone Else?

2»

Comments

  • #32
    LumoColor
    Closed Accounts Posts: 103 ✭✭LumoColor


    Spoke to NTL this morning and they are investigating as there have been a few reports of problems.

    Aparently there are a lot of network changes going off at the moment as NTL.ie is breaking away from NTL UK as part of the UPC takeover.


  • #33
    Drapper
    Registered Users, Registered Users 2 Posts: 3,812 ✭✭✭Drapper


    anyone from NTL reading! It would be great to have a network status bar on your website to keep punters uptodate on servicing etc like NLT UK. Even IBB send out emails of network upgrades! it would save loads of calls and clogging of the CS line ............ and keep people in the know!


  • #34
    LumoColor
    Closed Accounts Posts: 103 ✭✭LumoColor


    Drapper wrote:
    anyone from NTL reading! It would be great to have a network status bar on your website to keep punters uptodate on servicing etc like NLT UK. Even IBB send out emails of network upgrades! it would save loads of calls and clogging of the CS line ............ and keep people in the know!
    I mentioned this to them when I was onto support, not going to happen until UPC takeover stuff is completed.

    They admitted there was a problem affecting the whole network they detected at 9pm (2 hours after I reported it to Tech Supp - nice to see they on the ball :eek:) and that it was resolved 9am this morning.

    Pings back to normal here:-

    Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

    Reply from 82.133.85.65: bytes=32 time=25ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=23ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=33ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=22ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=20ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=31ms TTL=50

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


  • #35
    Drapper
    Registered Users, Registered Users 2 Posts: 3,812 ✭✭✭Drapper


    LumoColor wrote:
    I mentioned this to them when I was onto support, not going to happen until UPC takeover stuff is completed.

    guess we will have to give the network updates here !! :p


  • #36
    thund3rbird_
    Registered Users, Registered Users 2 Posts: 866 ✭✭✭thund3rbird_


    Drapper wrote:
    anyone from NTL reading! It would be great to have a network status bar on your website to keep punters uptodate on servicing etc like NLT UK. Even IBB send out emails of network upgrades! it would save loads of calls and clogging of the CS line ............ and keep people in the know!

    there is one.... only, as the ntl Ireland network is still connected to the UK one you need to check the ntlworld UK page :rolleyes:

    http://www.ntl-isp.ntl.com/ServiceStatus/

    this page refers to a fault that was detected aroung 9:45pm on the 25th


  • Advertisement
  • #37
    d4r3n
    Registered Users Posts: 707 ✭✭✭d4r3n


    I recently got NTL Broadband installed (D4) and playing games can be a nightmare sometimes, it seems to be fine but then it spikes and I get like 60 loss for a few seconds and then its back.

    Pinging www.ntl.ie [62.253.165.47] with 32 bytes of data:
    Reply from 62.253.165.47: bytes=32 time=36ms TTL=111
    Reply from 62.253.165.47: bytes=32 time=27ms TTL=111
    Reply from 62.253.165.47: bytes=32 time=1485ms TTL=111
    Reply from 62.253.165.47: bytes=32 time=50ms TTL=111

    Pinging www.ntl.ie [62.253.165.47] with 32 bytes of data:
    Reply from 62.253.165.47: bytes=32 time=20ms TTL=111
    Reply from 62.253.165.47: bytes=32 time=28ms TTL=111
    Reply from 62.253.165.47: bytes=32 time=725ms TTL=111
    Reply from 62.253.165.47: bytes=32 time=32ms TTL=111

    Pinging www.ntl.ie [62.253.165.47] with 32 bytes of data:
    Reply from 62.253.165.47: bytes=32 time=34ms TTL=111
    Reply from 62.253.165.47: bytes=32 time=122ms TTL=111
    Reply from 62.253.165.47: bytes=32 time=1334ms TTL=111
    Reply from 62.253.165.47: bytes=32 time=49ms TTL=111


    Pinging www.ntl.ie [62.253.165.47] with 32 bytes of data:
    Reply from 62.253.165.47: bytes=32 time=20ms TTL=111
    Reply from 62.253.165.47: bytes=32 time=28ms TTL=111
    Request timed out.
    Reply from 62.253.165.47: bytes=32 time=30ms TTL=111


  • #38
    Cuddlesworth
    Registered Users, Registered Users 2 Posts: 13,995 ✭✭✭✭Cuddlesworth


    Type in ping ???.etc -n 50

    sends more packets and gives a bigger picture.
    Other than that looks like you need to ring up customer support and complain since cable broadband has no excuse for so many lost packets.


  • #39
    TempestSabre
    Registered Users, Registered Users 2 Posts: 4,142 ✭✭✭TempestSabre


    Mine has been bad on and off over the past couple of weeks, but I didn't check the pings. I just know it was playing havok with VOIP. I must check it the next time the VOIP act up. However checked it now and its the best I've ever seen it. Used to be chronic.

    Pinging www.ntl.ie [62.253.165.47] with 32 bytes of data:

    Reply from 62.253.165.47: bytes=32 time=30ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=55ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=26ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=51ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=28ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=29ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=30ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=25ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=26ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=33ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=28ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=29ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=54ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=31ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=26ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=27ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=28ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=35ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=29ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=30ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=31ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=26ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=33ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=70ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=29ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=26ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=29ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=48ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=26ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=27ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=34ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=29ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=30ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=48ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=25ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=32ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=57ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=28ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=29ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=30ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=37ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=32ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=33ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=28ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=77ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=30ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=43ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=33ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=28ms TTL=109
    Reply from 62.253.165.47: bytes=32 time=34ms TTL=109

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


  • #40
    Drapper
    Registered Users, Registered Users 2 Posts: 3,812 ✭✭✭Drapper


    thats cause I'm not rapping the luttlrestown bandwidth :-) lol

    ping www.jolt.co.uk -n 50

    Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=25ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=55ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=22ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=19ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=29ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=33ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=23ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=20ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=57ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=29ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=30ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=20ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=35ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=39ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=22ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=23ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=31ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=23ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=20ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=29ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=24ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=22ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=31ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=38ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=51ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=39ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=48ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=23ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=27ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=40ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=34ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=21ms TTL=50
    Reply from 82.133.85.65: bytes=32 time=31ms TTL=50

    Ping statistics for 82.133.85.65:
    Packets: Sent = 45, Received = 45, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 57ms, Average = 28ms


    ping are great for me 90% of the time ! odd spikes at peak times


  • #41
    Star*
    Closed Accounts Posts: 32 ✭Star*


    Kicking some ass as always I see thund3rbird_ :)

    Some things never change chicken ! :)


  • Advertisement
  • #42
    Boomer23
    Closed Accounts Posts: 230 ✭✭Boomer23


    boo yah!


Advertisement