Ping problems

Turin · May 22, 2009, 19:10:26

Hi all,
this is my first post on the forum's and unfortunately it's because of a problem

Everyday,especially on an evening my throughput drops and my ping goes berserk.This has been going on for 2 week's now.
I've been in contact with support and done everything possible my end but I'm just not getting anywhere.This is what I'm getting with interleaving turned off on a 6Mb connection...

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 192.168.0.1
2 telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 www.idnet.net [212.69.36.10]

Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 108ms 0/ 100 = 0% 0/ 100 = 0% telehouse-gw2-lo2.idnet.net [212.69.63.55]
0/ 100 = 0% |
3 108ms 0/ 100 = 0% 0/ 100 = 0% telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
0/ 100 = 0% |
4 105ms 0/ 100 = 0% 0/ 100 = 0% redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
0/ 100 = 0% |
5 95ms 0/ 100 = 0% 0/ 100 = 0% redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
0/ 100 = 0% |
6 98ms 0/ 100 = 0% 0/ 100 = 0% www.idnet.net [212.69.36.10]

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=177ms TTL=59
Reply from 212.69.36.10: bytes=32 time=160ms TTL=59
Reply from 212.69.36.10: bytes=32 time=108ms TTL=59
Reply from 212.69.36.10: bytes=32 time=97ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 177ms, Average = 135ms

As you can see it's not good

Anyone else had this problem??

Rik · May 22, 2009, 19:16:08

Hi Turin and welcome to the forum.

A few people have seen ping issues, including me, but it's small scale and not as severe as the issue affecting you. In most cases, re-booting the router cures the issue, but I'm guessing you've already done that?

If throughput is dropping at the same time, my hunch would be contention at the exchange. Do you get marked differences from, say, morning to evening?

Turin · May 22, 2009, 19:22:43

Hi Rik,

I'm mainly on at night so i tend to notice it more at that time.But having said that i've been on most of the day today and it keep's happening.
I've rebooted the router which sometimes solves it(for half an hour) and sometimes it doesn't.

Rik · May 22, 2009, 19:23:41

That does sound like contention, then. Were support able to identify whether there was an issue. As a long shot, could you borrow another router to try?

Turin · May 22, 2009, 19:29:42

I've changed router's,filter's and cables with no joy.
I've been dealing Brian from support but i don't think he's seen anything specific.

Sebby · May 22, 2009, 19:39:46

Rik · May 23, 2009, 09:53:05

What are your downstream line stats, Turin (you do realise that I've instantly nicknamed you Shroud, don't you

), ie sync speed, noise margin and attenuation?

Turin · May 23, 2009, 10:51:55

Your DSL connection rate: 7456 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 6000 kbps
Actual IP throughput achieved during the test was - 5616 kbps

Connection Speed    7456 kbps    448 kbps
Line Attenuation    37.0 db    18.5 db
Noise Margin    6.3 db    23.0 db

Quote from: Rik on May 23, 2009, 09:53:05
Turin (you do realise that I've instantly nicknamed you Shroud, don't you )

You are not the first and won't be the last

Rik · May 23, 2009, 10:57:42

Your profile is 500k too slow for your sync speed, which suggests that you've had some instability on the line. Throughput for the profile is about right. If that drops later in the day, then contention seems likely, but meanwhile, you might like to try running Routerstats to see what's happening to the line. It can be downloaded here if you don't already have it.

Turin · May 23, 2009, 11:05:34

Thanks Rik,I'll do that now and just so you know I'm now officially out my knowledge area and haven't a clue what I'm looking for

Rik · May 23, 2009, 11:07:04

Routerstats will monitor your noise margin and connection speed. That way, you will see any changes to your connection, plotted as a graph. It will, hopefully, give us a clearer picture of what's going on.

Turin · May 23, 2009, 16:57:18

Right i'm starting to get problems again..

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
0 ian [192.168.0.2]
1 192.168.0.1
2 telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 www.idnet.net [212.69.36.10]

Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 98ms 1/ 100 = 1% 1/ 100 = 1% telehouse-gw2-lo2.idnet.net [212.69.63.55]
0/ 100 = 0% |
3 109ms 1/ 100 = 1% 1/ 100 = 1% telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
0/ 100 = 0% |
4 103ms 0/ 100 = 0% 0/ 100 = 0% redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
0/ 100 = 0% |
5 87ms 0/ 100 = 0% 0/ 100 = 0% redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
1/ 100 = 1% |
6 90ms 1/ 100 = 1% 0/ 100 = 0% www.idnet.net [212.69.36.10]

Trace complete.

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
0 ian [192.168.0.2]
1 192.168.0.1
2 telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 www.idnet.net [212.69.36.10]

Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
|
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 68ms 1/ 100 = 1% 1/ 100 = 1% telehouse-gw2-lo2.idnet.net [212.69.63.55]
0/ 100 = 0% |
3 75ms 1/ 100 = 1% 1/ 100 = 1% telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
0/ 100 = 0% |
4 75ms 0/ 100 = 0% 0/ 100 = 0% redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
0/ 100 = 0% |
5 66ms 0/ 100 = 0% 0/ 100 = 0% redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
1/ 100 = 1% |
6 67ms 1/ 100 = 1% 0/ 100 = 0% www.idnet.net [212.69.36.10]

Trace complete.

Test result as this was going on...

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 7456 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 6000 kbps
Actual IP throughput achieved during the test was - 5481 kbps

I had Routerstats running also but nothing showed up to be a problem.

Rik · May 23, 2009, 17:06:46

My tracert is average atm:

tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms home [192.168.1.254]
2 32 ms 31 ms 29 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 34 ms 37 ms 31 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 83 ms 31 ms 47 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 31 ms 31 ms 31 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 31 ms 33 ms 33 ms www.idnet.net [212.69.36.10]

Trace complete.

Your profile is still 500k below what it should be, but that can take days to recover. Thoughput is possibly a little slow, but nothing to worry about. How far are you from London?

Turin · May 23, 2009, 17:09:23

About 160 miles

Rik · May 23, 2009, 17:11:06

That would add a small amount to my times, but not that much. Do you know what depth of interleaving you have?

Turin · May 23, 2009, 17:11:49

Not a clue Rik

Rik · May 23, 2009, 17:12:25

Have you ever been able to ping with a fast path connection?

Turin · May 23, 2009, 17:13:15

I thought i was on a fast path connection?

Rik · May 23, 2009, 17:16:57

What's your router say? On fast path, I ping about 13ms to idnet.net, on interleaved I ping about 23ms, ie it adds 10ms to my line. It's generally reckoned to add about 20ms, so I seem to get away with quite light interleaving. There's more on the subject at Kitz.

Turin · May 23, 2009, 17:20:11

With interleaved i ping around 45ms.On fast path i ping at 20ms.

Rik · May 23, 2009, 17:20:51

So, is interleaving on now? Have you tried re-booting the router?

Turin · May 23, 2009, 17:24:34

Interleaved was turned off on Friday morning.Ping to idnet has gone down now to 20ms so i haven't rebooted the router this time.

Rik · May 23, 2009, 17:27:45

It sounds like interleaving has been turned back on to me, your router should be able to tell you, either from the error count or it should state fast path/interleaved.

Turin · May 23, 2009, 17:32:04

Nothing on my router states fast path/interleaved.Whereabouts would i find the error count?

Rik · May 23, 2009, 17:33:01

Which router are you using?