NTL High Pings - Anyone Else?

LumoColor

Im getting really high pings to UK gaming servers.

Anyone else having problems?

C:\>ping -t www.jolt.co.uk

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

Reply from 82.133.85.65: bytes=32 time=108ms TTL=50
Reply from 82.133.85.65: bytes=32 time=83ms TTL=50
Reply from 82.133.85.65: bytes=32 time=106ms TTL=50
Reply from 82.133.85.65: bytes=32 time=82ms TTL=50
Reply from 82.133.85.65: bytes=32 time=113ms TTL=50
Reply from 82.133.85.65: bytes=32 time=69ms TTL=50
Reply from 82.133.85.65: bytes=32 time=109ms TTL=50
Reply from 82.133.85.65: bytes=32 time=175ms TTL=50
Reply from 82.133.85.65: bytes=32 time=77ms TTL=50
Reply from 82.133.85.65: bytes=32 time=151ms TTL=50
Reply from 82.133.85.65: bytes=32 time=40ms TTL=50

Ping statistics for 82.133.85.65:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 175ms, Average = 101ms

mang87

Reply from 82.133.85.65: bytes=32 time=66ms TTL=51
Reply from 82.133.85.65: bytes=32 time=64ms TTL=51
Reply from 82.133.85.65: bytes=32 time=103ms TTL=5
Reply from 82.133.85.65: bytes=32 time=86ms TTL=51


Hmm, seems so... I've not been playing anything though in the past 24 hours so I've not noticed.

LumoColor

Tried calling technical support and the line just goes dead.

Drapper

yup very poor for some reason !

location would help Lumo?

Seamy

Getting this problem too,I just started a thread asking the same question then noticed this one.Very poor connection all day.:mad:

mang87

:mad:

Joined the FFM clan server(ut2004://80.69.76.18:8718) and it took .5 seconds for my weapon to fire. God dam. pinging 150.

Reply from 80.69.76.18: bytes=32 time=76ms TTL=49
Reply from 80.69.76.18: bytes=32 time=86ms TTL=49
Reply from 80.69.76.18: bytes=32 time=218ms TTL=49
Reply from 80.69.76.18: bytes=32 time=223ms TTL=49

Ping statistics for 80.69.76.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% lo
Approximate round trip times in milli-seconds:
Minimum = 76ms, Maximum = 223ms, Average = 150ms

Drapper

sh1t even ~Wow is laggy !! this is worse than we thought jim !

mickger

Drapper wrote:

sh1t even ~Wow is laggy !! this is worse than we thought jim !

Speeds are crap here in Waterford too:mad:

LumoColor

Drapper wrote:

location would help Lumo?

Lucan, Dublin.

Not just UK, pinging NTL.ie gets:-

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

Reply from 62.253.165.47: bytes=32 time=232ms TTL=101
Reply from 62.253.165.47: bytes=32 time=203ms TTL=101
Reply from 62.253.165.47: bytes=32 time=77ms TTL=101
Reply from 62.253.165.47: bytes=32 time=246ms TTL=101
Reply from 62.253.165.47: bytes=32 time=134ms TTL=101
Reply from 62.253.165.47: bytes=32 time=62ms TTL=101
Reply from 62.253.165.47: bytes=32 time=86ms TTL=101
Reply from 62.253.165.47: bytes=32 time=142ms TTL=101

Normally I get around 20ms.

I did get through to someone in Normal Tech support and they logged the call, though broadband support is not working today

No gaming for me tonight

mang87

LumoColor wrote:

Lucan, Dublin.

Same

LumoColor wrote:

No gaming for me tonight

Same

Seamy

Sure their tech support is useless anyway,they spend their time trying to convince you it's a problem on your end.

wideband

same here in D24 im afraid....:mad:

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

Reply from 82.133.85.65: bytes=32 time=232ms TTL=50
Reply from 82.133.85.65: bytes=32 time=89ms TTL=50
Reply from 82.133.85.65: bytes=32 time=232ms TTL=50
Reply from 82.133.85.65: bytes=32 time=228ms TTL=50

Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 232ms, Average = 195ms
///////////////////////////////////////////////////////////////////
Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms xxx.xxx.x.x
2 9 ms 6 ms 10 ms 10.189.88.1
3 8 ms 8 ms 9 ms 89.101.162.5
4 7 ms 19 ms 9 ms dbln-t2core-a-ge-210-0.inet.ntl.com [82.9.145.5]
5 8 ms 19 ms 8 ms dbln-bb-a-ae1-0.inet.ntl.com [213.105.174.53]
6 14 ms 11 ms 12 ms ren-bb-b-so-100-0.inet.ntl.com [213.105.174.41]
7 48 ms 19 ms 18 ms man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]
8 28 ms 14 ms 17 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
9 17 ms 22 ms 17 ms bir-bb-a-so-000-0.inet.ntl.com [62.253.185.133]
10 35 ms 25 ms 17 ms bir-bb-b-ae0-0.inet.ntl.com [62.253.185.154]
11 258 ms 258 ms 229 ms nth-bb-a-so-300-0.inet.ntl.com [62.253.185.105]
12 215 ms 234 ms 226 ms nth-bb-b-ae0-0.inet.ntl.com [62.253.185.118]
13 84 ms 210 ms 210 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
14 94 ms 285 ms 212 ms pop-bb-b-ge-000-0.inet.ntl.com [213.105.174.230]
15 122 ms 261 ms 209 ms tele-ic-2-so-700-0.inet.ntl.com [62.253.184.6]
16 26 ms 25 ms 24 ms 212.250.14.42
17 207 ms 139 ms 266 ms ge-0-2-0.lon1-9.nildram.net [62.72.141.38]
18 319 ms 147 ms 155 ms jolt-gw.nildram.net [195.149.20.214]
19 126 ms 201 ms 267 ms secure.jolt.co.uk [82.133.85.65]
Trace complete.

christophicus

mickger wrote:

Speeds are crap here in Waterford too:mad:

Yeah its still bad here in waterford,Its really pissing me off,Now i cant play any cames online.

fatherdougalmag

Phew. Thought I was a lone

Seamy wrote:

Sure their tech support is useless anyway,they spend their time trying to convince you it's a problem on your end.

Well if/when we ring in at least we can point to this thread and re-assure them that it's on their side.

Pinging sip.blueface.ie:
Reply from 213.168.225.133: bytes=32 time=186ms TTL=47
Reply from 213.168.225.133: bytes=32 time=91ms TTL=47
Reply from 213.168.225.133: bytes=32 time=89ms TTL=47
Reply from 213.168.225.133: bytes=32 time=209ms TTL=47
Reply from 213.168.225.133: bytes=32 time=179ms TTL=47
Reply from 213.168.225.133: bytes=32 time=210ms TTL=47
Reply from 213.168.225.133: bytes=32 time=236ms TTL=47
Reply from 213.168.225.133: bytes=32 time=61ms TTL=47
Reply from 213.168.225.133: bytes=32 time=217ms TTL=47

etc.

Pinging www.ntl.ie is consistently 200ms+.
It's bad enough their high but they're wild too.

VOIP is suffering. The wife can't make her usual Sunday night natter calls and she's taking it out on me.

Please NTL sort it soooooon

christophicus

LOl hate that

Drapper

christophicus wrote:

Y i cant play any cames online.

whats a came ?

mang87

Sweet _JESUS_ this is ridiculous

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

Reply from 62.253.165.47: bytes=32 time=621ms TTL=103
Reply from 62.253.165.47: bytes=32 time=210ms TTL=103
Reply from 62.253.165.47: bytes=32 time=444ms TTL=103
Reply from 62.253.165.47: bytes=32 time=284ms TTL=103

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

WTF is happening to NTL. I've been talking to a few other people, and they're having similar problems.

Seamy

I know from experience with them in the past NTL staff do actually keep an eye on boards.ie so anybody out there that is experiecing the same problem please post it here,the more people that complain the sooner NTL will get off their backsides.

Seamy

Reply from 62.253.165.47: bytes=32 time=103ms TTL=105
Reply from 62.253.165.47: bytes=32 time=24ms TTL=105
Reply from 62.253.165.47: bytes=32 time=111ms TTL=105
Reply from 62.253.165.47: bytes=32 time=197ms TTL=105
Reply from 62.253.165.47: bytes=32 time=204ms TTL=105
Reply from 62.253.165.47: bytes=32 time=197ms TTL=105
Reply from 62.253.165.47: bytes=32 time=205ms TTL=105
Reply from 62.253.165.47: bytes=32 time=24ms TTL=105
Reply from 62.253.165.47: bytes=32 time=212ms TTL=105

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

Oh yeah would be usefull to post the proof also.

Am based in Tallaght area.

illumin

same here (templeogue)
Pinging www.ntl.ie [62.253.165.47] with 32 bytes of data

Reply from 62.253.165.47: bytes=32 time=228ms TTL=101
Reply from 62.253.165.47: bytes=32 time=239ms TTL=101
Reply from 62.253.165.47: bytes=32 time=237ms TTL=101
Reply from 62.253.165.47: bytes=32 time=224ms TTL=101

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

christophicus

Drapper wrote:

whats a came ?

sorry ,game

hugoline

same here (D8), although some pakets at least dropped below 200ms (was 200-750ms earlier in the evening)

Reply from 62.253.165.47: bytes=32 time=265ms TTL=103
Reply from 62.253.165.47: bytes=32 time=71ms TTL=103
Reply from 62.253.165.47: bytes=32 time=273ms TTL=103
Reply from 62.253.165.47: bytes=32 time=62ms TTL=103

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

Diabolus

Same here Knocklyon - D16

cmd prompt wrote:

C:\Documents and Settings\Administrator>ping www.ntl.ie

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

Reply from 62.253.165.47: bytes=32 time=288ms TTL=103
Reply from 62.253.165.47: bytes=32 time=283ms TTL=103
Request timed out.
Reply from 62.253.165.47: bytes=32 time=285ms TTL=103

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

Also the problem seems to be in Birmingham as the traceroute suggests

cmd prompt wrote:

7 13 ms 12 ms 15 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 15 ms 15 ms 14 ms bir-bb-a-so-000-0.inet.ntl.com [62.253.185.133]

9 277 ms 286 ms 275 ms bir-bb-b-ae0-0.inet.ntl.com [62.253.185.154]

Hop 9 seems to be it and its Birmingham too
So its the ****ign UK

CyberGhost

D22, 400ms pings absolutely terrible >:/

Cuddlesworth

For once Im sitting here with Ibb's high pings and erractic spikes and still having somebody to laugh at.

oceanclub

Same problem here in D8 (Christchurch)

Pinging 62.253.165.47 with 32 bytes of data:

Reply from 62.253.165.47: bytes=32 time=298ms TTL=101
Reply from 62.253.165.47: bytes=32 time=291ms TTL=101
Reply from 62.253.165.47: bytes=32 time=345ms TTL=101
Reply from 62.253.165.47: bytes=32 time=306ms TTL=101

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

P.

mang87

Things seem to be settling down again.

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

Reply from 62.253.165.47: bytes=32 time=23ms TTL=111
Reply from 62.253.165.47: bytes=32 time=20ms TTL=111
Reply from 62.253.165.47: bytes=32 time=21ms TTL=111
Reply from 62.253.165.47: bytes=32 time=21ms TTL=111

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

Nehpets

Mine were slow for awhile, they've gone back to normal now!

Drapper

just read on NTLworld Uk there was lots of upgrades in the uk and NI over the weekend ! might have had backhaul impacts!

fatherdougalmag

krazy_8s wrote:

For once Im sitting here with Ibb's high pings and erractic spikes and still having somebody to laugh at.

Well we hope you enjoyed it while it lasted.

Now we have the conch!

Diabolus

Drapper wrote:

just read on NTLworld Uk there was lots of upgrades in the uk

Yeah i spoke to NTL who confirmed the same thing.
Issue was with Birmingham as expected.