NTL Problem!

MickFarr

I have the NTL 1.5MB broadband connection but I've been getting high pings every night lately could anyone who has NTL broadband do a tracert and ping test to www.jolt.co.uk please. Also could you take a note of the time. Thanks here's my results

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

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

1 33 ms 63 ms 28 ms 10.135.31.254
2 10 ms 9 ms 10 ms host82-9-146-5.not-set-yet.ntli.net [82.9.146.5
3 49 ms 41 ms 10 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]
4 30 ms 12 ms 11 ms man-bb-a-atm010-226.inet.ntl.com [62.253.188.82
5 28 ms 16 ms 65 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
6 18 ms 19 ms 20 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
7 167 ms 158 ms 120 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130
8 142 ms 109 ms 120 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
9 129 ms 140 ms 148 ms lon1-10.nildram.net [213.208.106.169]
10 86 ms 95 ms 103 ms lon1-9.nildram.net [195.149.20.130]
11 123 ms 144 ms 195 ms jolt-gw.nildram.net [195.149.20.126]
12 144 ms 145 ms 146 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

C:\Documents and Settings\Michael Farrell>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=100ms TTL=53
Reply from 195.149.21.11: bytes=32 time=99ms TTL=53
Reply from 195.149.21.11: bytes=32 time=117ms TTL=53
Reply from 195.149.21.11: bytes=32 time=125ms TTL=53

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

nava

Hi

I'm on the 750 package, the ping and tracert were done at 23:35 pm Thursday

you can check your speed on http://www.pcpitstop.com/

Just tested with the results:

Download speed: 696 kilobits per second
Upload speed: 126 kilobits per second


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

C:\Documents and Settings\computer>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=109ms TTL=52
Reply from 195.149.21.11: bytes=32 time=107ms TTL=52
Reply from 195.149.21.11: bytes=32 time=118ms TTL=52
Reply from 195.149.21.11: bytes=32 time=132ms TTL=52

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

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

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

1 3 ms 2 ms 3 ms 192.168.2.1
2 15 ms 10 ms 11 ms 10.135.55.254
3 12 ms 13 ms 11 ms host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

4 14 ms 14 ms 11 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]

5 21 ms 16 ms 17 ms man-bb-a-atm010-226.inet.ntl.com [62.253.188.82]

6 20 ms 17 ms 16 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
7 22 ms 29 ms 23 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

8 77 ms 25 ms 28 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

9 39 ms 31 ms 34 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

10 27 ms 33 ms 50 ms lon1-10.nildram.net [213.208.106.169]
11 132 ms 122 ms 106 ms lon1-9.nildram.net [195.149.20.130]
12 30 ms 28 ms 30 ms jolt-gw.nildram.net [195.149.20.126]
13 108 ms 99 ms 105 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

Regards
Nava

seamus

C:\>tracert www.jolt.co.uk

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

1 4 ms 1 ms <1 ms (none) [192.168.1.1]
2 10 ms 7 ms 15 ms 10.135.47.254
3 9 ms 11 ms 12 ms host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

4 10 ms 13 ms 9 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]

5 23 ms 25 ms 22 ms man-bb-a-atm010-230.inet.ntl.com [62.253.188.78]

6 24 ms 40 ms 21 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
7 23 ms 53 ms 23 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

8 30 ms 38 ms 26 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

9 26 ms 26 ms 25 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

10 82 ms 32 ms 36 ms lon1-10.nildram.net [213.208.106.169]
11 109 ms 95 ms 76 ms lon1-9.nildram.net [195.149.20.130]
12 25 ms 65 ms 25 ms jolt-gw.nildram.net [195.149.20.126]
13 38 ms 84 ms 30 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

C:\>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=113ms TTL=52
Reply from 195.149.21.11: bytes=32 time=144ms TTL=52
Reply from 195.149.21.11: bytes=32 time=158ms TTL=52
Reply from 195.149.21.11: bytes=32 time=136ms TTL=52

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

On 750 package

Lenny

On 1.5
Thursday 11:55PM

Looking at my pings are much better than all of yours and tracert is 1 less hop..


Tracing route to clarity.jolt.co.uk [195.149.21.11]

over a maximum of 30 hops:



1 16 ms <10 ms <10 ms 10.135.7.254

2 <10 ms 16 ms <10 ms host82-9-146-5.not-set-yet.ntli.net [82.9.146.5]

3 <10 ms 15 ms <10 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]

4 47 ms 15 ms 31 ms man-bb-a-atm010-224.inet.ntl.com [62.253.187.50]

5 <10 ms 16 ms 15 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]

6 15 ms 31 ms 32 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

7 16 ms 16 ms 31 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

8 15 ms 32 ms 15 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

9 16 ms 16 ms 31 ms lon1-10.nildram.net [213.208.106.169]

10 16 ms 15 ms 31 ms lon1-9.nildram.net [195.149.20.130]

11 16 ms 16 ms 31 ms jolt-gw.nildram.net [195.149.20.126]

12 16 ms 31 ms 47 ms clarity.jolt.co.uk [195.149.21.11]



Trace complete.




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



Reply from 195.149.21.11: bytes=32 time=15ms TTL=53

Reply from 195.149.21.11: bytes=32 time=16ms TTL=53

Reply from 195.149.21.11: bytes=32 time=16ms TTL=53

Reply from 195.149.21.11: bytes=32 time=16ms TTL=53



Ping statistics for 195.149.21.11:

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

Approximate round trip times in milli-seconds:

Minimum = 15ms, Maximum = 16ms, Average = 15ms

Lenny

Also here is the url for the NTL speed test
http://homepage.ntlworld.com/robin.d.h.walker/speedtest.html

MickFarr

Thanks everyone for the replies. Here another test I ran this morning at 9:40

C:\Documents and Settings\Michael Farrell>tracert www.jolt.co.uk
Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

1 7 ms 7 ms 81 ms 10.135.31.254
2 9 ms 7 ms 8 ms host82-9-146-5.not-set-yet.ntli.net [82.9.146.5]
3 7 ms 7 ms 11 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]
4 8 ms 10 ms 10 ms dub-core-b-fa000.inet.ntl.com [62.254.96.2]
5 13 ms 14 ms 14 ms lee-bb-b-atm010-225.inet.ntl.com [62.253.187.54]
6 13 ms 16 ms 17 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
7 17 ms 19 ms 16 ms nth-bb-b-so-000-0.inet.ntl.com [62.253.185.101]
8 18 ms 19 ms 24 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
9 20 ms 19 ms 34 ms tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]
10 17 ms 18 ms 19 ms lon1-10.nildram.net [213.208.106.169]
11 20 ms 19 ms 23 ms lon1-9.nildram.net [195.149.20.130]
12 20 ms 18 ms 18 ms jolt-gw.nildram.net [195.149.20.126]
13 19 ms 22 ms 20 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

C:\Documents and Settings\Michael Farrell>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=20ms TTL=53
Reply from 195.149.21.11: bytes=32 time=20ms TTL=53
Reply from 195.149.21.11: bytes=32 time=21ms TTL=53
Reply from 195.149.21.11: bytes=32 time=19ms TTL=53

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



As you can see there is a big difference running this is the morning. I have never had this problem before. I will run the same test later again to test. Its giving me alot of lag playing online !

seamus

Lenny wrote:

Looking at my pings are much better than all of yours and tracert is 1 less hop..

That's cos myself and nava are using internal routers which gives us one extra hop, which doesn't really make a difference to our overall speed (<1ms pings)

Lenny

Ahh I see now,
I'll run another test later aswell about 6 or so to see if it peaks up..

MickFarr

Lenny wrote:

Ahh I see now,
I'll run another test later aswell about 6 or so to see if it peaks up..

Cheers Lenny,

My pings where fine from about 10:30 onwards. Here's some screen shots showing the ping times to different places around the world the Bad Ping screenshot was taken at 21:37 last night and the Good Pings at 9:15 this morning just before heading to work

sEAMy^

Just thought I'd make others aware of my recent problems so as they don't make the same mistake as me and go with NTL.

I am currently on the 1.5mb Broadband Max connection,been on it now for nearly 4 months I'd say.Everything was fine last 3 months the occasional slow down but thats allowed I suppose,but in the last 2 weeks speeds I have been getting are absolutely terrible to say the least.I have been running lots of different speed tests from uk servers and also purchased one highly recommended one,what I should be getting is 1500kbps 254 upstream as advertised or near enough,what I have been getting last 2 weeks is 350 kbps 111 upstream average,sometimes as low as 250kbps 85 upstream.I finish work at 5 everday probably not on pc till after 6 but this is the speed im getting from thern till late at night when I switch pc off.

I pay 50 euro a month for this service and what has annoyed me more is the reply I got from cable modem support.I won't mention any names beacause I don't want to get anyone in trouble but the atitude I got from him was because he was getting a decent ping from NTL to my pc that the problem was simply "internet traffic" and should clear.I left it for a day and problem was still the same he then ran a few more tests and said he didnt know what else he could do,what he said was no one else from your area has rang and complained about the speeds,which by the way is the Tallaght area.I asked is there anymore we can try beacouse I use the internet for work and gaming etc,he said no he had tried everything and again went on with the whole "no one else has complained so there cant be something wrong with yours" making me more and more feel like he didnt believe me or something.I then explained that I was about to cancel and switch over to Irish Broadband,he gave little to no response to this and said well there was nothing he could do,never once offering to end somebody out to at least attempt to find what problem was,so I was civl and hung up.

I am currently still with NTL 3 weeks on and have been given some one elses name to deal with,but yet when I ring im left on for 30 mins or more and end up hanging up.This thread is solely here to make people aware of my problems with NTL,many people out there may think different,but I STRONGLY recommend going else where as their connection is a joke and there customer support is by far the worst I have ever dealt with.

NTL Broadband Max 1/10

JackKelly

i presume by "kps" you mean kilobits and not kilobytes.

im not with ntl so i cant comment!

There is a government section thought, that you can get onto about issues like this, the name has escaped me at the mo. Have a look around here for it. (my mind has blanked)

We got our lack of broadband sorted by them.Eventually.

CoolNitro

Yea I have the same problem as sEAMy^ right now my ping to uk servers is about 200 normaly its 16 or so but that was before NTL gave everyone 0.5meg upgrade, I ask you why give out .5 of a meg upgrade FREE when the curent servers cant handle it what were NTL thinking.

Lenny

Lads, they aren't entitled to upgrade the connection their site, when you signed up the service was working perfectly, more people may have signed up and started slowing the server down, with cable the more that use it the server degradges for everyone and they aren't entitled to keep it up to top notch..
where bouts in tallaght are yous?
I'm in tallaght too and post some urls to some sites you did the tests on and I'll rung some too, but I think I am grand this way...
theres another topic about the ntl ping times from yesterday, check that out..

illumin

Yeah ive noticed my pings being crap for the past week or so. Did anyone ring up ntl and ask them whats up? Altho i doubt they would give a straight answer.

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

1 53 ms 51 ms 27 ms 10.135.15.254
2 15 ms 14 ms 12 ms host82-9-146-5.not-set-yet.ntli.net [82.9.146.5]

3 11 ms 14 ms 23 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]

4 20 ms 23 ms 27 ms man-bb-a-atm010-228.inet.ntl.com [62.253.187.122
]
5 18 ms 49 ms 24 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
6 25 ms 27 ms 56 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

7 121 ms 144 ms 155 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

8 124 ms 117 ms 174 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

9 107 ms 120 ms 116 ms lon1-10.nildram.net [213.208.106.169]
10 145 ms 129 ms 123 ms lon1-9.nildram.net [195.149.20.130]
11 146 ms 159 ms 219 ms jolt-gw.nildram.net [195.149.20.126]
12 148 ms * 113 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.


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

Reply from 195.149.21.11: bytes=32 time=124ms TTL=53
Reply from 195.149.21.11: bytes=32 time=196ms TTL=53
Reply from 195.149.21.11: bytes=32 time=144ms TTL=53
Reply from 195.149.21.11: bytes=32 time=135ms TTL=53

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

sEAMy^

Yeah I have rang NTL and apparently everything is fine,problems not with NTL but with "general internet traffic" causing the slow down.I have friends on 512k eircom connections and they are getting better speeds than my NTL 1.5mb connection.More and more people need to get on to them,they've told me nobody has been on read my post in this section.

sEAMy^

It gets alot worse than this.


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

1 36 ms 10 ms 9 ms 10.135.23.254
2 13 ms 13 ms 17 ms host82-9-146-5.not-set-yet.ntli.net [82.9.146.5]

3 15 ms 8 ms 11 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]

4 58 ms 39 ms 18 ms man-bb-a-atm010-228.inet.ntl.com [62.253.187.122
]
5 29 ms 16 ms 19 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
6 41 ms 71 ms 25 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

7 180 ms 161 ms 148 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

8 118 ms 164 ms 186 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

9 150 ms 147 ms 159 ms lon1-10.nildram.net [213.208.106.169]
10 132 ms 221 ms 168 ms lon1-9.nildram.net [195.149.20.130]
11 123 ms 129 ms 126 ms jolt-gw.nildram.net [195.149.20.126]
12 153 ms 150 ms 140 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

C:\Documents and Settings\>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=129ms TTL=53
Reply from 195.149.21.11: bytes=32 time=209ms TTL=53
Reply from 195.149.21.11: bytes=32 time=131ms TTL=53
Reply from 195.149.21.11: bytes=32 time=162ms TTL=53

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

iksaw

don't know what it's like at the moment (not on ntl) but spoke to a friend who was on to them earlier this evening
he was onto support & they put him on hold to check on info they had just got in on email
looking at posts in both threads it looks like the problem is not in dublin anyway as the dub / dbln times are fine
pings seem to increase when they hit gfd / lee / man (guilford / leeds / manchester)

apparently some ISP in the UK (must use part of ntl's network?) made some changes to their systems over the last week or so & that had an impact on some of their servers every evening
seemingly this had been rectified today but was going to take a while to settle down again (a few hours?)

he was asked to keep an eye on his connection over the weekend & send in tracerts if any problems

mail them into cablemodemhelp@ntlworld.ie if you have any problems

Gonzo

sEAMy^ wrote:

Yeah I have rang NTL and apparently everything is fine,problems not with NTL but with "general internet traffic" causing the slow down.I have friends on 512k eircom connections and they are getting better speeds than my NTL 1.5mb connection.More and more people need to get on to them,they've told me nobody has been on read my post in this section.

NTL are feeding you lies:) There isnt a problem with "general internet traffic" as my pings are ok on eircom tho they are not quite as good as when I first got the service back in February. My cousin is on NTL and his pings ar normally half mine but in the past week he has been getting 140ms too..time to lean on NTL to fix this

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=40ms TTL=57
Reply from 195.149.21.11: bytes=32 time=37ms TTL=57
Reply from 195.149.21.11: bytes=32 time=39ms TTL=57
Reply from 195.149.21.11: bytes=32 time=41ms 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 = 37ms, Maximum = 41ms, Average = 39ms

C:\Documents and Settings\Barry>

sEAMy^

I hope that is the case and its sorted this weekend.But surely if this is preventing ntl customers from getting the speeds they paid for then it IS an NTL problem,and they shudn't tell the people that ring in otherwise,I was told that no one else had rang in and reported the problem - which is obviously false.And if this UK server was doing upgrades thas fine,im not happy it slows be down what why couldn't they tell me that was the case and not lie by saying they knew of no problems and everything was fine.If me threatning to cancel my account didnt make them tell me anything,just shows how much NTL value their customers.

T-b0n3

Im on 1.5mg ntl too. It seems to go very slow during the evening. 150+ to servers I norm get 40 to. Rang them dis morning , they said it was all fine blah blah.Going to have to ring them and abuse them on monday , because its really bad at the moe and it was fine today before 4pm.

Adam

sEAMy^

So clearly lots of people are having the same slow down problem,and its just NTL its happening with,I urge people who are having the problem to get on to NTL and maybe they might get up off their arses and do something about it.

sEAMy^

Thanks for that Adam,I know NTL tech staff look at these boards cos one them refered to it in one of my conversations with them,so NTL if your reading clearly theres a problem so sort it fast or your going to loose alot of customers.

MagicBusDriver

It looks like congestion. Was poor this evening but is ok now. (00:49)

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

1 <10 ms <10 ms <10 ms 192.168.0.1
2 10 ms 10 ms 10 ms 10.135.23.254
3 10 ms 10 ms 10 ms host82-9-146-5.not-set-yet.ntli.net [82.9.146.5]
4 10 ms 10 ms 10 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]
5 30 ms 20 ms 20 ms man-bb-a-atm010-230.inet.ntl.com [62.253.188.78]
6 10 ms 10 ms 20 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
7 30 ms 20 ms 60 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
8 30 ms 30 ms 30 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
9 40 ms 40 ms 31 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
10 60 ms 60 ms 60 ms lon1-10.nildram.net [213.208.106.169]
11 30 ms 30 ms 20 ms lon1-9.nildram.net [195.149.20.130]
12 60 ms 60 ms 70 ms jolt-gw.nildram.net [195.149.20.126]
13 20 ms 20 ms 30 ms clarity.jolt.co.uk [195.149.21.11]

spongebob

Seamy

This tracert showed that the problem was congestion around Telehouse London where the Clarity servers are served by Nildram .

It has nothing AT ALL to do with Tallaght or Cable Modems or NTL Ireland. Its a peering router in England that is at fault. With peering it can be difficult to tell which 'side' of the peer is the real problem. Suffice to say there are probably 2 culprits and they need to get together.

Contact Nildram and tell them to upgrade their Gateway to NTL in Telehouse.

5 29 ms 16 ms 19 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
6 41 ms 71 ms 25 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

7 180 ms 161 ms 148 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

8 118 ms 164 ms 186 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

9 150 ms 147 ms 159 ms lon1-10.nildram.net [213.208.106.169]
10 132 ms 221 ms 168 ms lon1-9.nildram.net [195.149.20.130]

M

MickFarr

I rang NTL on Thursday to let them know there was a problem with high pings. They told me that it was not an NTL problem and that it was to do with the website I was trying to access and that there is nothing they can do.

I then told her I was having no problems using Leap Broadband only NTL and asked her to try doing a tracert to jolt.co.uk
"I can't do that", she said
"Why", I asked
"Because we are located in Waterford and don't get NTL here", she said
"So then, whom do you use there to access the Internet", I asked her
"Eircom", she said.

At this stage I started to laugh and just ended the conversation. I couldn't believe that they use eircom and she was trying to tell me it was the websites fault and not NTL when she couldn't even test it herself.

Later that night I did the ping and tracert test to www.jolt.co.uk using both NTL and Leap. As you can see below NTL=Crap LEAP=Good very easy to see. It is not just jolt where there’s a problem if you look at the jpg's attached in a previous post you will see that this happens to anywhere around the world!!

I have sent a long email to cablemodemhelp on Friday with the tests I have done showing both NTL and LEAP results. Here's a small example below.

---

BAD TRACERT & PING RESULTS USING NTL

---

The current time is: 21:25

C:\Documents and Settings\Michael Farrell>tracert www.jolt.co.uk
Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

1 33 ms 63 ms 28 ms 10.135.31.254
2 10 ms 9 ms 10 ms host82-9-146-5.not-set-yet.ntli.net [82.9.146.5
3 49 ms 41 ms 10 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]
4 30 ms 12 ms 11 ms man-bb-a-atm010-226.inet.ntl.com [62.253.188.82
5 28 ms 16 ms 65 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
6 18 ms 19 ms 20 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
7 167 ms 158 ms 120 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130
8 142 ms 109 ms 120 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
9 129 ms 140 ms 148 ms lon1-10.nildram.net [213.208.106.169]
10 86 ms 95 ms 103 ms lon1-9.nildram.net [195.149.20.130]
11 123 ms 144 ms 195 ms jolt-gw.nildram.net [195.149.20.126]
12 144 ms 145 ms 146 ms clarity.jolt.co.uk [195.149.21.11]
Trace complete.

C:\Documents and Settings\Michael Farrell>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=100ms TTL=53
Reply from 195.149.21.11: bytes=32 time=99ms TTL=53
Reply from 195.149.21.11: bytes=32 time=117ms TTL=53
Reply from 195.149.21.11: bytes=32 time=125ms TTL=53

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

---- GOOD TRACERT & PING RESULTS USING LEAP BROADBAND----
The current time is: 21:26

C:\Documents and Settings\mfarrell.RIVERVIEW>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 my.firewall [192.168.0.254]
2 33 ms 30 ms 35 ms 217.67.141.221
3 38 ms 40 ms 39 ms 217.67.143.45
4 38 ms 40 ms 39 ms 217.67.131.1
5 98 ms 39 ms 39 ms 217.67.131.6
6 43 ms 40 ms 55 ms 212.147.128.49
7 38 ms 35 ms 39 ms so-4-1-2.ar1.dub1.gblx.net [64.211.206.97]
8 128 ms 50 ms 49 ms pos2-1-622m.ar2.lon2.gblx.net [67.17.92.146]
9 53 ms 55 ms 55 ms lon1-9.nildram.net [195.66.224.59]
10 49 ms 85 ms 85 ms jolt-gw.nildram.net [195.149.20.126]
11 54 ms 55 ms 55 ms clarity.jolt.co.uk [195.149.21.11]
Trace complete.

C:\Documents and Settings\mfarrell.RIVERVIEW>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=54ms TTL=52
Reply from 195.149.21.11: bytes=32 time=53ms TTL=52
Reply from 195.149.21.11: bytes=32 time=52ms TTL=52
Reply from 195.149.21.11: bytes=32 time=47ms TTL=52

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

red_ice

Yer, im getting the same problem since wednesday of last week. I rang in to complain to them and was givin the notion that it was a fault on my computer thats making the internet act slower.. I insisited it wasnt, but just to prove them wrong i shut down my machine, unplugged my second HDD, reinstalled windows and it was still the same. Now, not only do i have a wanky connection, i have lost 3 years of VALUABLE data(disk revoery pro do your stuff..)

After being juggled through 3 different 'techies', i was given the promise of a call back - no dice. I didnt see sight nor sound of one. So during the week ive called them about 6 times trying to get on to someone that knows whats going on.

I was just asleep in my bed 10 minutes ago, and i was woken up by an NTL rep on the phone. Nice girl and did the job right, just got the details she needed and left me for my bed/post on boards.ie. During the conversation i started to think to myself 'jesus, have my 2 weeks of moaning finally woken them up?'... No. She said that boards.ie had woken them up! This is nice to know, but imagion i was the only person with this problem... some how i dont think i would have gotten my call back.

I use the internet for gaming and thats about it... with my traceroots passing the gillford switch averaging 150 there is no real competitive play for me.

8 166 ms 160 ms 165 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
8 143 ms 131 ms 133ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
8 173 ms 172 ms 164ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
8 151ms 146ms 153 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]
8 123 ms 146 ms 145 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

With pings like this i may aswell switch to ISDN..

The lady on the phone seemed pritty confident that the matter would be resolved. I hope it does too.

damien

red_ice wrote:

Now, not only do i have a wanky connection, i have lost 3 years of VALUABLE data

Is Simon Travalagia still working for them ?

sEAMy^

Muck,

If you had bothered to read the rest of the comments and different topics posted regarding NTL you would have seen that it isn't just the jolt servers thats the problem its everywhere outside ireland.If your telling me that if NTL customers are having terrible problems with slow downs accessing any foreign servers that it ISN'T an NTL problem then your having a laugh.With regards to the UK server problem NTL clearly knew that this was the reason people were having the problems on uk servers but instead told customers nothing was wrong "must be a problem their end",this is terrible customer service....if they are aware of a problem its their duty to inform the customer and do something about it.Rather then make the customer feel like its a problem their end.From phone calls to NTL today i know now that NTL have been aware of this problem for nearly 2 weeks and have been in touch with England trying to sort it.Should be fixed by Monday I've been told.....we'll have to wait and see.....how long before we have this problem again?? watch this space.

Moriarty

I've merged the two NTL threads into this one.

MickFarr

It simply is an NTL problem. Check the tracert that have been posted. They will have to fix the problem or how can they expect new customers to sign up or existing customers to stay.

If they have known about this problem for 2 weeks how come there customer support know nothing and try to blame it on the website? As I have show in previous post it is not limited to jolt.co.uk its the whole world.

spongebob

sEAMy^ wrote:

Muck,

If you had bothered to read the rest of the comments and different topics posted regarding NTL you would have seen that it isn't just the jolt servers thats the problem its everywhere outside ireland.If your telling me that if NTL customers are having terrible problems with slow downs accessing any foreign servers that it ISN'T an NTL problem then your having a laugh.

Seamy.

EVERY PING IN THS THREAD is to Jolt . A few servers in Telehouse in London do not constitute " everywhere outside ireland" as you described it and prove fúck all bar what I stated above and will repeat below.

Forget pings, the traceroutes give the correct information. When your pings are crap there is a concurrent slowdown at or around the peering point between NTL and Nildram. Nildram were taken over recently and will be up in the air when it comes to ordering extra capacity if they are maxing out , thats bad news if this is a nightly problem .

I won't bother with a Peering 101 lesson but the problem IS a Joint NTL and Nildram one and need to be sorted out between them . Jolt may not be aware of it .....although they damn well should be. Ask them if they are having problems with Nildram .

Next time you have this problem with clarity/jolt can you tracert to

www.bbc.co.uk
www.colt-telecom.com
www.tele2.co.uk

and paste the tracerts in here along with your usual Jolt one with a time of trace. Maybe ping them too but dont always expect an answer .

Also register with NTLHellWorld or
NTL Hell and ask UK NTL customers to replicate the problem as well and post the results. Dont bother tellling them where Tallaght is

M

ntlbell

At last, ntl users with the same issue.

My story,

I only noticed the problem Monday just gone but it's probably been there longer. Like everyone else I've had the whole "it's not us it's you" "it's not us it's the site your trying"

Eventually after numerous calls I got a fairly clued in guy on the phone who was going to actually do something about it, nothing happened. so I mailed my traces, pings etc from when it's good between 9-6 and when it's bad.

the majority of the traces are to machines I normally avg about 25ms to, located in ireland but connected to a uk provider, plus usuall suspects ftp.heanet.ie, ftp.esat.net.

No response from any of my mails so I lost my top today and eventually got to a supervisor type (non technical) who gave me their name and word I'd get a call on Monday, (We'll see)

Tonight and all day today pings have been fine lo latency high download speeds, like everythings back to normal.

I did notice during the week on the ntl server status for the uk work being carried out in various areas in the uk which effected the UBR's I was having problems with mostly in leeds and Gildford.

It looks like those tickets are resolved and were open the first night I noticed the problem.

So fingers crossed all is well, I'm not hopefull tho.

Is everyone _still_ having problems ?

If so we need to just constantly hammer the support line and straight away ask to go over the random technicians head to someone more technical or senior and has access to the ntl network.

ntlbell

Muck wrote:

Seamy.

EVERY PING IN THS THREAD is to Jolt . A few servers in Telehouse in London do not constitute " everywhere outside ireland" as you described it and prove fúck all bar what I stated above and will repeat below.

Forget pings, the traceroutes give the correct information. When your pings are crap there is a concurrent slowdown at or around the peering point between NTL and Nildram. Nildram were taken over recently and will be up in the air when it comes to ordering extra capacity if they are maxing out , thats bad news if this is a nightly problem .

I won't bother with a Peering 101 lesson but the problem IS a Joint NTL and Nildram one and need to be sorted out between them . Jolt may not be aware of it .....although they damn well should be. Ask them if they are having problems with Nildram .


M

The servers I connet to are on level3 but located in dublin I don't go near any Nildram UBR's on route so I really don't think it's anything to do with them,

Traces on this thread maybe just jolt, but the traces i sent to NTL none of them were jolt none of them went near a Nildram UBR and all had the same problems.

lee-bb-b-so-700-0.inet.ntl.com and gfd-bb-b-so-500-0.inet.ntl.com was the cause of most of my issues.

RicardoSmith

C:\>tracert www.jolt.co.uk

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

1 48 ms 7 ms 7 ms 10.135.103.254
2 35 ms 8 ms 37 ms host82-9-147-25.not-set-yet.ntli.net[82.9.147.25]
3 9 ms 9 ms 8 ms dub-core-b-pos1100.inet.ntl.com [62.254.96.201]
4 14 ms 13 ms 30 ms lee-bb-b-atm010-225.inet.ntl.com [62.253.187.54]
5 18 ms 16 ms 16 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 27 ms 20 ms 16 ms nth-bb-b-so-000-0.inet.ntl.com [62.253.185.101]
7 28 ms 22 ms 32 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
8 54 ms 29 ms 46 ms tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]
9 20 ms 34 ms 52 ms lon1-10.nildram.net [213.208.106.169]
10 24 ms 23 ms 19 ms lon1-9.nildram.net [195.149.20.130]
11 19 ms 20 ms 58 ms jolt-gw.nildram.net [195.149.20.126]
12 47 ms 48 ms 46 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

C:\>

MickFarr

Muck wrote:

Seamy.

EVERY PING IN THS THREAD is to Jolt .
M

Thats what I asked for in the first post but if you check out my posts I give examples of bad pings to www.broadbandspeedtest.co.uk.

https://us.v-cdn.net/6034073/uploads/attachments/21407/7383.JPG

wheres Nildram in that ? but you can see the bad ping are NTLs fault !!!

MickFarr

Here's a tracert using BT broadband
There's no problem for BT Broadband user with Nildram here. Thats because there isn't aproblem with Nildram Muck its with NTL.

Look closer at the tracerts and you can see it starts with NTL not anyone else in any of the posts !!


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

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

1 17 ms 17 ms 17 ms 217.47.207.122
2 17 ms 16 ms 16 ms 217.47.207.82
3 16 ms 17 ms 17 ms core2-pos7-0.edinburgh.ukcore.bt.net [62.6.199.209]
4 27 ms 25 ms 24 ms core2-pos13-0.birmingham.ukcore.bt.net [62.6.196.97]
5 28 ms 27 ms 27 ms core2-pos15-1.reading.ukcore.bt.net [194.74.16.234]
6 29 ms 30 ms 29 ms core2-pos9-0.ilford.ukcore.bt.net [194.74.65.193]
7 31 ms 29 ms 29 ms 194.74.65.198
8 30 ms 29 ms 29 ms lon1-10.nildram.net [195.66.226.59]
9 30 ms 29 ms 31 ms lon1-9.nildram.net [195.149.20.130]
10 30 ms 30 ms 30 ms jolt-gw.nildram.net [195.149.20.126]
11 30 ms 30 ms 30 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

C:\Documents and Settings\Iain>

spongebob

Mick .

Thats a perfect BT trace all right. It seems to hit the same Nildram peering router .

Is there any chance you can get the traces done AT THE SAME TIME which is what you need to prove the point. Then post all the traces, carried out simulateously or near simultaneosuly in the thread.

The rationale is simple, the NTL problems experienced occur in the UK and may be replicated widely across the entire NTL user base . If so the pressure can be put on NTL to fix it .

M

M

spongebob

MickFarr wrote:

wheres Nildram in that ? but you can see the bad ping are NTLs fault !!!

Its very difficult to read that large graphic but it appears to be a congested NTL core router in Leeds / Nottingham .

Entirely NTL's fault that one because the spike occurs before the peering point with someone in Nottingham .

As this is not on the NTL route to Nildram it is a separate issue and should not be lumped in with the Nildram problems as the faults/fixes may be escalated and handled by different teams.

M

MickFarr

Muck

No problem Muck. I can't do that at the moment as I'm up North but will do a tracert test using NTL, LEAP and BT broadband tomorrow.

Mick

ntlbell

Muck do you work for NTL?

Today I decided to bypass the usuall monkeys in NTL and go through the buisness NOC via my job.

They knew about the problem from day 1, the work was announced on the server status page, and as far as they can see the problem is resolved and will be watched closley.

Now why couldn't this communication go through to the monkeys in waterford?

shams.

spongebob

ntlbell wrote:

Muck do you work for NTL?

No

Now why couldn't this communication go through to the monkeys in waterford?

That would require organisation. As there is no second line support in Ireland I told people to make noise in England, where to such as NTLHELL , how and what to report.

The reason I commented on how to interpret Traceroutes in the first place was that I used to have to collect data from the Esat X centre in Dublin over a link from Sprint that suffered large scale packet loss (not even timeouts) on regular occasions.

As it was a Peering Link not a transit problem Sprint blamed ESAT and yadda yadda. I finally found that by telling some large ESAT customers such as Ryanair that their sites were inaccesible from the states that something was done about it. Naturally I included traceroutes .

They listened to Ryanair when they would never have listened to me. Did anyone get the impression that Guildford listens to Waterford ?

M

dub45

ntlbell wrote:

Muck do you work for NTL?

Today I decided to bypass the usuall monkeys in NTL and go through the buisness NOC via my job.

They knew about the problem from day 1, the work was announced on the server status page, and as far as they can see the problem is resolved and will be watched closley.

Now why couldn't this communication go through to the monkeys in waterford?

shams.

Communication within NTL seems to be appalling. One of the reasons I would have doubts about getting bb from NTL when it eventually comes down my street is the poor customer service they provide. I know that up to now from reading posts here that customer service for their bb seems to have been pretty good but as they take on more and more customers for bb I wonder will the bb service end up exactly like the tv service as regards customer service.

Recently I was getting a weak signal on the couple of TV points I have from them and I confirmed with a neighbour their signal was also weak. I rang NTL and explained the problem. The girl I spoke to was absolutely admamant they would have to do a house visit to sort out the problem. I pointed out that I would have to take time off work for this, that it would be a waste of time for both themselves and me as it was clearly nothing to do with my set up.

She refused to progress the matter further unless I agreed to set up an appointment.

Later I was able to find out that there was a general problem in the area and that NTL were aware of it and subsequently fixed it.

This is by no means the first time that I have found examples of a lack of communication with NTL. You would think though that it would be an absolute priority to keep the call centers up to date even if they are not too worried about wasting their customers time - unnecessary call outs are surely costly for NTL?

ntlbell

we're off again,

back to the usuall ****

2 11 ms 8 ms 8 ms 10.135.23.254
3 10 ms 11 ms 7 ms host82-9-146-5.not-set-yet.ntli.net [82.9.146.5]

4 9 ms 9 ms 8 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]

5 11 ms 13 ms 10 ms dub-core-b-fa000.inet.ntl.com [62.254.96.2]
6 125 ms 126 ms 124 ms lee-bb-b-atm010-225.inet.ntl.com [62.253.187.54]

7 88 ms 101 ms 102 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]

ntlbell

I hate using jolt as an example but.

20.11pm (REAL ISP)

traceroute to jolt.co.uk (195.149.21.11), 64 hops max, 40 byte packets
1 fw-dub (83.245.10.33) 0.179 ms 0.165 ms 0.156 ms
2 lvl3gw.thn.packetexchange.net (212.187.197.193) 19.695 ms 13.129 ms 15.243 ms
3 lon1-9.nildram.net (195.66.224.59) 18.028 ms 17.944 ms 13.361 ms
4 jolt-gw.nildram.net (195.149.20.126) 14.462 ms 13.870 ms 13.858 ms
5 clarity.jolt.co.uk (195.149.21.11) 14.045 ms 18.369 ms 18.564 ms


20.12pm (NTL)

traceroute to jolt.co.uk (195.149.21.11), 64 hops max, 40 byte packets
1 10.135.23.254 (10.135.23.254) 8.503 ms 11.195 ms 7.300 ms
2 host82-9-146-5.not-set-yet.ntli.net (82.9.146.5) 12.626 ms 7.855 ms 9.485 ms
3 dub-core-a-pos1100.inet.ntl.com (62.254.96.137) 9.033 ms 8.089 ms 12.915 ms
4 dub-core-b-fa000.inet.ntl.com (62.254.96.2) 10.435 ms 10.126 ms 11.969 ms
5 lee-bb-b-atm010-225.inet.ntl.com (62.253.187.54) 107.333 ms 116.605 ms 130.176 ms
6 lee-bb-a-ae0-0.inet.ntl.com (62.253.187.185) 128.565 ms 143.997 ms 134.687 ms
7 nth-bb-b-so-000-0.inet.ntl.com (62.253.185.101) 135.906 ms 137.954 ms 140.846 ms
8 pop-bb-a-so-100-0.inet.ntl.com (213.105.172.14) 135.564 ms 125.350 ms 135.410 ms
9 tele-ic-2-so-000-0.inet.ntl.com (62.253.185.86) 162.136 ms 148.735 ms 139.306 ms
10 lon1-10.nildram.net (213.208.106.169) 142.899 ms 132.944 ms 123.268 ms
11 lon1-9.nildram.net (195.149.20.130) 108.399 ms 120.508 ms 114.924 ms
12 jolt-gw.nildram.net (195.149.20.126) 127.015 ms 132.747 ms 154.970 ms
13 clarity.jolt.co.uk (195.149.21.11) 146.289 ms 145.253 ms *

bbc for good measure so we're clear on the jolt issue

REAL ISP
traceroute to www.bbc.net.uk (212.58.224.115), 64 hops max, 40 byte packets
1 lvl3gw.thn.packetexchange.net (212.187.197.193) 13.623 ms 15.123 ms 14.008 ms
2 rt-linx-a.thdo.bbc.co.uk (195.66.224.103) 13.793 ms 14.028 ms 13.586 ms
3 212.58.238.153 (212.58.238.153) 13.653 ms 17.612 ms 14.565 ms
4 www15.thdo.bbc.co.uk (212.58.224.115) 14.318 ms 14.793 ms 15.066 ms


POXY NTL

traceroute to www.bbc.net.uk (212.58.224.115), 64 hops max, 40 byte packets
1 10.135.23.254 (10.135.23.254) 9.737 ms 7.863 ms 7.657 ms
2 host82-9-146-5.not-set-yet.ntli.net (82.9.146.5) 10.793 ms 8.658 ms 10.437 ms
3 dub-core-a-pos1100.inet.ntl.com (62.254.96.137) 32.433 ms 10.181 ms 7.583 ms
4 dub-core-b-fa000.inet.ntl.com (62.254.96.2) 10.705 ms 13.153 ms 10.884 ms
5 lee-bb-b-atm010-227.inet.ntl.com (62.253.188.90) 123.445 ms 139.717 ms 134.582 ms
6 lee-bb-a-ae0-0.inet.ntl.com (62.253.187.185) 127.488 ms 150.089 ms 120.486 ms
7 nth-bb-b-so-000-0.inet.ntl.com (62.253.185.101) 116.886 ms 122.291 ms 128.447 ms
8 pop-bb-a-so-100-0.inet.ntl.com (213.105.172.14) 126.752 ms 143.769 ms 130.931 ms
9 tele-ic-2-so-000-0.inet.ntl.com (62.253.185.86) 151.020 ms 145.301 ms 143.463 ms
10 212.58.239.217 (212.58.239.217) 123.926 ms 131.531 ms 137.192 ms
11 212.58.238.153 (212.58.238.153) 138.187 ms 122.986 ms 146.232 ms
12 www15.thdo.bbc.co.uk (212.58.224.115) 130.239 ms 120.691 ms 130.916 ms

Töpher

Aye, it is terrilbe at the moment.
I actually got hold of quite a helpful guy on the helpline yesterday. He said one of the ISP's they go thru in the UK messed something up, and that NTL have resorted whatever they have to do and it should be settled down shortly. And indeed it was, everything was back to being brilliant. He tested everythign while I was on the phone and was yielding the same results as I was here. Went out last night, just home now and it's back to being muck again. Really quite píssed off about this!

[Edit] And for the record, it aint just jolt (obviously ), here's traceroute to 4k-gaming:

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

C:\tracert 4k-gaming.com

Tracing route to 4k-gaming.com [213.230.203.70]
over a maximum of 30 hops:

1 7 ms 7 ms 9 ms 10.135.63.254
2 8 ms 7 ms 10 ms host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

3 12 ms 9 ms 9 ms dub-core-a-pos1100.inet.ntl.com [62.254.96.137]

4 13 ms 8 ms 10 ms dub-core-b-fa000.inet.ntl.com [62.254.96.2]
5 105 ms 104 ms 112 ms lee-bb-b-atm010-225.inet.ntl.com [62.253.187.54]

6 132 ms 134 ms 142 ms ren-bb-a-so-000-0.inet.ntl.com [62.253.185.161]

7 * 153 ms 131 ms bre-bb-b-so-200-0.inet.ntl.com [62.253.185.166]

8 142 ms 138 ms 138 ms bre-bb-a-ae0-0.inet.ntl.com [213.105.172.86]
9 158 ms 148 ms 149 ms redb-ic-1-so-010-0.inet.ntl.com [62.253.188.106]

10 333 ms 947 ms 1087 ms 999.fe0-1.rt0.thdo.woaf.net [217.79.160.51]
11 151 ms 152 ms 149 ms 213.230.194.36
12 133 ms 135 ms 148 ms web6.000025.net [213.230.203.70]

Trace complete.

Ripwave

dub45 wrote:

You would think though that it would be an absolute priority to keep the call centers up to date

Eircom don't do this. UTV don't do this. IBB don't do this. Why would NTL be any different?

ntlbell

Ripwave wrote:

Eircom don't do this. UTV don't do this. IBB don't do this. Why would NTL be any different?

Yeh, because sending an email can be a very complicated task.

dub45

Ripwave wrote:

Eircom don't do this. UTV don't do this. IBB don't do this. Why would NTL be any different?

I cant belive you are serious in asking that question.

Ripwave

dub45 wrote:

I cant belive you are serious in asking that question.

Okay, I didn't insert a sarcasm emoticon, but why would you expect NTL to be any better at customer service and internal communications than eircom, IBB or UTV?

ntlbell

Ripwave wrote:

Okay, I didn't insert a sarcasm emoticon, but why would you expect NTL to be any better at customer service and internal communications than eircom, IBB or UTV?

To be fair and I know they're not mentioned above and apart from the whole capping fiasco, netsource as far as i can see are exceptional when it comes to customer support.

IBB although never dealt with them for myself but on behalf of others, again seem to to go way beyond the call of duty for customer support and most of the phone monkeys seem to be fairly well clued in.

eircom well, they're eircom.

dub45

Ripwave wrote:

Okay, I didn't insert a sarcasm emoticon, but why would you expect NTL to be any better at customer service and internal communications than eircom, IBB or UTV?

And I will repeat exactly what I posted to your last question: I can`t belive you are serious in asking that question.

But anyways some reasons:

It would potentially give them a competitive advantage.

It would save them money (as in the case I instanced a reduction unnecessary call outs)

It would certainly enhance their reputation as in posts to boards might read 'I am with NTL and when I phone them they are are always up to date with what is going on'

It would possibly improve the internal working atmosphere in NTL - good communication has that potential - as in it lessens the 'nobody tell us whats going on around here"

It would certainly lessen customer frustration.