High Pings

[Florence]

OK who at NTL has messed with my coinnection!!!!!!


Its been good for a few weeks and now its screwed again in the words of a friend between me and the UBR.

Tracing route to www.bbc.net.uk [212.58.224.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms
2 * 83 ms * 10.252.24.1
3 238 ms * * oldh-t2cam1-a-ge-wan51-129.inet.ntl.com [80.5.16
5.69]
4 308 ms * 63 ms manc-t3core-1a-ge-112-0.inet.ntl.com [213.104.24
2.53]
5 * * * Request timed out.
6 * 291 ms 116 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
7 * * 149 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

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

9 * * * Request timed out.
10 * * 17 ms 212.58.238.189
11 44 ms 162 ms * 212.58.238.149
12 27 ms 16 ms 15 ms www30.thdo.bbc.co.uk [212.58.224.81]

Trace complete.

C:\Documents and Settings\Florence>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.224.115] with 32 bytes of data:

Reply from 212.58.224.115: bytes=32 time=49ms TTL=245
Reply from 212.58.224.115: bytes=32 time=31ms TTL=245
Reply from 212.58.224.115: bytes=32 time=285ms TTL=245
Reply from 212.58.224.115: bytes=32 time=18ms TTL=245

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



Can I have a stable 2mb connection forget the 4mb just give me a steady stable 2mb :mad:

[James Henry]

Reboot el cable modem just incase, highly unlikely to fix though. Try direct without router (just so that you have done it).

Saves time when logging the fault :)

Can you do a ping -n 100 www.bbc.co.uk (http://www.bbc.co.uk) please and give the end result :)

How's the power levels?

[Florence]

Ok I will do the tests this problem keeps returning I have Mirc open and when I get this message in the room
[18:42] <Awy> Status Still Away Reason Autoaway [4hrs]Time 046:42 PM Away For 10hrs
Ping Your ping time has exceeded 4secs
Ping Your ping time has exceeded 4secs
Ping Your ping time has exceeded 4secs
[18:57] <Kits> pete
[18:57] <profpete> kits
[18:58] <Kits> pm
Ping Your ping time has exceeded 4secs

If I do my tracert or ping tests then its bad other times the connection is good.. All I want is it to be stable again like it was before all the upgrades.

When its peak times my connection just goes down hill fast.

[cyrus the great]

Hi, My pings are a nightmare tonight . I have donr the above and here are the results.
Pinging www.bbc.net.uk (http://www.bbc.net.uk) [212.58.224.88] with 32 bytes of data:
Reply from 212.58.224.88: bytes=32 time=154ms TTL=246
Reply from 212.58.224.88: bytes=32 time=95ms TTL=246
Reply from 212.58.224.88: bytes=32 time=104ms TTL=246
Reply from 212.58.224.88: bytes=32 time=47ms TTL=246
Reply from 212.58.224.88: bytes=32 time=55ms TTL=246
Reply from 212.58.224.88: bytes=32 time=156ms TTL=246
Reply from 212.58.224.88: bytes=32 time=28ms TTL=246
Reply from 212.58.224.88: bytes=32 time=23ms TTL=246
Reply from 212.58.224.88: bytes=32 time=139ms TTL=246
Reply from 212.58.224.88: bytes=32 time=75ms TTL=246
Reply from 212.58.224.88: bytes=32 time=70ms TTL=246
Reply from 212.58.224.88: bytes=32 time=160ms TTL=246
Reply from 212.58.224.88: bytes=32 time=16ms TTL=246
Reply from 212.58.224.88: bytes=32 time=143ms TTL=246
Reply from 212.58.224.88: bytes=32 time=22ms TTL=246
Request timed out.
Reply from 212.58.224.88: bytes=32 time=16ms TTL=246
Reply from 212.58.224.88: bytes=32 time=66ms TTL=246
Reply from 212.58.224.88: bytes=32 time=20ms TTL=246
Reply from 212.58.224.88: bytes=32 time=71ms TTL=246
Reply from 212.58.224.88: bytes=32 time=167ms TTL=246
Reply from 212.58.224.88: bytes=32 time=90ms TTL=246
Reply from 212.58.224.88: bytes=32 time=205ms TTL=246
Reply from 212.58.224.88: bytes=32 time=210ms TTL=246
Reply from 212.58.224.88: bytes=32 time=281ms TTL=246
Reply from 212.58.224.88: bytes=32 time=82ms TTL=246
Reply from 212.58.224.88: bytes=32 time=180ms TTL=246
Reply from 212.58.224.88: bytes=32 time=23ms TTL=246
Reply from 212.58.224.88: bytes=32 time=215ms TTL=246
Reply from 212.58.224.88: bytes=32 time=171ms TTL=246
Reply from 212.58.224.88: bytes=32 time=169ms TTL=246
Reply from 212.58.224.88: bytes=32 time=78ms TTL=246
Reply from 212.58.224.88: bytes=32 time=95ms TTL=246
Reply from 212.58.224.88: bytes=32 time=67ms TTL=246
Reply from 212.58.224.88: bytes=32 time=87ms TTL=246
Reply from 212.58.224.88: bytes=32 time=105ms TTL=246
Reply from 212.58.224.88: bytes=32 time=92ms TTL=246
Reply from 212.58.224.88: bytes=32 time=59ms TTL=246
Reply from 212.58.224.88: bytes=32 time=19ms TTL=246
Reply from 212.58.224.88: bytes=32 time=23ms TTL=246
Reply from 212.58.224.88: bytes=32 time=41ms TTL=246
Reply from 212.58.224.88: bytes=32 time=59ms TTL=246
Reply from 212.58.224.88: bytes=32 time=181ms TTL=246
Reply from 212.58.224.88: bytes=32 time=49ms TTL=246
Reply from 212.58.224.88: bytes=32 time=41ms TTL=246
Request timed out.
Reply from 212.58.224.88: bytes=32 time=18ms TTL=246
Reply from 212.58.224.88: bytes=32 time=18ms TTL=246
Reply from 212.58.224.88: bytes=32 time=21ms TTL=246
Request timed out.
Reply from 212.58.224.88: bytes=32 time=59ms TTL=246
Reply from 212.58.224.88: bytes=32 time=239ms TTL=246
Reply from 212.58.224.88: bytes=32 time=75ms TTL=246
Reply from 212.58.224.88: bytes=32 time=118ms TTL=246
Reply from 212.58.224.88: bytes=32 time=38ms TTL=246
Reply from 212.58.224.88: bytes=32 time=57ms TTL=246
Request timed out.
Reply from 212.58.224.88: bytes=32 time=79ms TTL=246
Reply from 212.58.224.88: bytes=32 time=102ms TTL=246
Reply from 212.58.224.88: bytes=32 time=120ms TTL=246
Reply from 212.58.224.88: bytes=32 time=19ms TTL=246
Reply from 212.58.224.88: bytes=32 time=46ms TTL=246
Reply from 212.58.224.88: bytes=32 time=136ms TTL=246
Reply from 212.58.224.88: bytes=32 time=32ms TTL=246
Reply from 212.58.224.88: bytes=32 time=145ms TTL=246
Reply from 212.58.224.88: bytes=32 time=57ms TTL=246
Reply from 212.58.224.88: bytes=32 time=114ms TTL=246
Reply from 212.58.224.88: bytes=32 time=149ms TTL=246
Reply from 212.58.224.88: bytes=32 time=68ms TTL=246
Reply from 212.58.224.88: bytes=32 time=185ms TTL=246
Reply from 212.58.224.88: bytes=32 time=88ms TTL=246
Reply from 212.58.224.88: bytes=32 time=145ms TTL=246
Reply from 212.58.224.88: bytes=32 time=39ms TTL=246
Reply from 212.58.224.88: bytes=32 time=73ms TTL=246
Request timed out.
Reply from 212.58.224.88: bytes=32 time=61ms TTL=246
Reply from 212.58.224.88: bytes=32 time=39ms TTL=246
Reply from 212.58.224.88: bytes=32 time=127ms TTL=246
Reply from 212.58.224.88: bytes=32 time=18ms TTL=246
Reply from 212.58.224.88: bytes=32 time=21ms TTL=246
Reply from 212.58.224.88: bytes=32 time=261ms TTL=246
Reply from 212.58.224.88: bytes=32 time=28ms TTL=246
Reply from 212.58.224.88: bytes=32 time=163ms TTL=246
Reply from 212.58.224.88: bytes=32 time=178ms TTL=246
Reply from 212.58.224.88: bytes=32 time=192ms TTL=246
Reply from 212.58.224.88: bytes=32 time=19ms TTL=246
Reply from 212.58.224.88: bytes=32 time=161ms TTL=246
Reply from 212.58.224.88: bytes=32 time=62ms TTL=246
Reply from 212.58.224.88: bytes=32 time=167ms TTL=246
Reply from 212.58.224.88: bytes=32 time=119ms TTL=246
Reply from 212.58.224.88: bytes=32 time=255ms TTL=246
Reply from 212.58.224.88: bytes=32 time=42ms TTL=246
Reply from 212.58.224.88: bytes=32 time=16ms TTL=246
Reply from 212.58.224.88: bytes=32 time=30ms TTL=246
Reply from 212.58.224.88: bytes=32 time=227ms TTL=246
Reply from 212.58.224.88: bytes=32 time=54ms TTL=246
Reply from 212.58.224.88: bytes=32 time=56ms TTL=246
Reply from 212.58.224.88: bytes=32 time=75ms TTL=246
Reply from 212.58.224.88: bytes=32 time=50ms TTL=246
Reply from 212.58.224.88: bytes=32 time=36ms TTL=246
Ping statistics for 212.58.224.88:
Packets: Sent = 100, Received = 95, Lost = 5 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 281ms, Average = 94ms

[Druchii]

Cyrus i'm getting worse loss than you, and really good pings when it works, looks like you may need to do a few more tracerts. Firstly to the modem and secondly to a website, see where its dropping.

[Florence]

It has been good since my last post until a few days ago when it started having high pingss again.

Reply from 212.58.224.113: bytes=32 time=171ms TTL=244
Reply from 212.58.224.113: bytes=32 time=166ms TTL=244
Reply from 212.58.224.113: bytes=32 time=16ms TTL=244
Reply from 212.58.224.113: bytes=32 time=76ms TTL=244
Reply from 212.58.224.113: bytes=32 time=15ms TTL=244
Reply from 212.58.224.113: bytes=32 time=168ms TTL=244
Reply from 212.58.224.113: bytes=32 time=137ms TTL=244
Reply from 212.58.224.113: bytes=32 time=120ms TTL=244
Reply from 212.58.224.113: bytes=32 time=18ms TTL=244
Reply from 212.58.224.113: bytes=32 time=31ms TTL=244
Reply from 212.58.224.113: bytes=32 time=16ms TTL=244
Reply from 212.58.224.113: bytes=32 time=94ms TTL=244
Reply from 212.58.224.113: bytes=32 time=389ms TTL=244
Reply from 212.58.224.113: bytes=32 time=16ms TTL=244
Reply from 212.58.224.113: bytes=32 time=17ms TTL=244
Reply from 212.58.224.113: bytes=32 time=16ms TTL=244
Reply from 212.58.224.113: bytes=32 time=21ms TTL=244
Reply from 212.58.224.113: bytes=32 time=16ms TTL=244
Reply from 212.58.224.113: bytes=32 time=15ms TTL=244
Reply from 212.58.224.113: bytes=32 time=239ms TTL=244
Reply from 212.58.224.113: bytes=32 time=17ms TTL=244
Reply from 212.58.224.113: bytes=32 time=16ms TTL=244
Reply from 212.58.224.113: bytes=32 time=19ms TTL=244
Reply from 212.58.224.113: bytes=32 time=253ms TTL=244
Reply from 212.58.224.113: bytes=32 time=45ms TTL=244
Reply from 212.58.224.113: bytes=32 time=147ms TTL=244
Reply from 212.58.224.113: bytes=32 time=80ms TTL=244
Reply from 212.58.224.113: bytes=32 time=60ms TTL=244
Reply from 212.58.224.113: bytes=32 time=21ms TTL=244
Reply from 212.58.224.113: bytes=32 time=73ms TTL=244
Reply from 212.58.224.113: bytes=32 time=19ms TTL=244
Reply from 212.58.224.113: bytes=32 time=310ms TTL=244
Reply from 212.58.224.113: bytes=32 time=168ms TTL=244
Reply from 212.58.224.113: bytes=32 time=15ms TTL=244
Reply from 212.58.224.113: bytes=32 time=16ms TTL=244
Reply from 212.58.224.113: bytes=32 time=16ms TTL=244
Reply from 212.58.224.113: bytes=32 time=16ms TTL=244
Reply from 212.58.224.113: bytes=32 time=19ms TTL=244
Reply from 212.58.224.113: bytes=32 time=156ms TTL=244

Ping statistics for 212.58.224.113:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 444ms, Average = 102ms

That was part of a ping to bbc.co.uk and tracert

Tracing route to www.bbc.net.uk [212.58.224.113]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms WRT54GS [192.168.1.1]
2 188 ms 8 ms 8 ms 10.252.24.1
3 8 ms 7 ms 7 ms oldh-t2cam1-a-ge-wan51-129.inet.ntl.com [80.5.16
5.69]
4 9 ms 10 ms 8 ms manc-t3core-1a-ge-112-0.inet.ntl.com [213.104.24
2.53]
5 62 ms 8 ms 9 ms man-bb-a-so-400-0.inet.ntl.com [213.105.175.1]
6 26 ms 8 ms 24 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
7 44 ms 15 ms 16 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

8 15 ms 17 ms 235 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

9 54 ms 17 ms 17 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
10 122 ms 333 ms 61 ms 212.58.238.189
11 33 ms 19 ms 18 ms 212.58.238.149
12 16 ms 17 ms 15 ms www13.thdo.bbc.co.uk [212.58.224.113]

Trace complete.