Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Latency issues especially late at night
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: Latency issues especially late at night
Latency issues especially late at night
22-06-2014 11:26 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hi
I routinely (almost every day) have latency issues late at night. This is usually when playing warcraft although it seems to affect webpages too. I have just had some issues and undertook a trace route and pathping as suggested on the warcraft forums. Can anyone advise me on what I can do to resolve these issues?
Thanks
Traceroute
Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:
1 74 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 41 ms 45 ms 39 ms lo0-central10.pcl-ag01.plus.net [195.166.128.182]
3 236 ms 176 ms 222 ms link-b-central10.pcl-gw02.plus.net [212.159.2.162]
4 49 ms 49 ms 48 ms xe-10-0-0.pcl-cr02.plus.net [212.159.0.194]
5 50 ms 39 ms 52 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 50 ms 50 ms 49 ms xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
7 147 ms 293 ms 380 ms vl-3101-ve-127.ebr1.London2.Level3.net [4.69.202.169]
8 46 ms 50 ms 49 ms ae-48-48.ebr1.London15.Level3.net [4.69.159.78]
9 49 ms 50 ms 48 ms ae-43-43.ebr1.London1.Level3.net [4.69.167.26]
10 46 ms 49 ms 50 ms ae-58-113.csw1.London1.Level3.net [4.69.153.122]
11 52 ms 53 ms 52 ms ae-124-3510.edge5.london1.Level3.net [4.69.166.37]
12 45 ms 52 ms 54 ms ldn-b5-link.telia.net [213.248.92.81]
13 46 ms 54 ms 53 ms ldn-bb1-link.telia.net [80.91.246.144]
14 51 ms 60 ms 58 ms prs-bb1-link.telia.net [80.91.247.6]
15 68 ms 66 ms 63 ms ffm-bb1-link.telia.net [80.91.245.102]
16 69 ms 69 ms 67 ms ffm-b10-link.telia.net [62.115.137.131]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Pathping
Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:
0 HomePC.lan []
1 dsldevice.lan [192.168.1.254]
2 lo0-central10.pcl-ag01.plus.net [195.166.128.182]
3 link-b-central10.pcl-gw02.plus.net [212.159.2.162]
4 xe-10-0-0.pcl-cr02.plus.net [212.159.0.194]
5 ae2.pcl-cr01.plus.net [195.166.129.6]
6 xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
7 vl-3101-ve-127.ebr1.London2.Level3.net [4.69.202.169]
8 ae-48-48.ebr1.London15.Level3.net [4.69.159.78]
9 ae-43-43.ebr1.London1.Level3.net [4.69.167.26]
10 ae-58-113.csw1.London1.Level3.net [4.69.153.122]
11 ae-124-3510.edge5.london1.Level3.net [4.69.166.37]
12 ldn-b5-link.telia.net [213.248.92.81]
13 ldn-bb1-link.telia.net [80.91.246.144]
14 prs-bb1-link.telia.net [80.91.247.6]
15 ffm-bb1-link.telia.net [213.155.132.157]
16 ffm-b10-link.telia.net [62.115.137.215]
17 * * *
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 HomePC.lan [192.168.1.69]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% dsldevice.lan [192.168.1.254]
4/ 100 = 4% |
2 143ms 4/ 100 = 4% 0/ 100 = 0% lo0-central10.pcl-ag01.plus.net [195.166.128.182]
0/ 100 = 0% |
3 135ms 7/ 100 = 7% 3/ 100 = 3% link-b-central10.pcl-gw02.plus.net [212.159.2.162]
0/ 100 = 0% |
4 135ms 8/ 100 = 8% 4/ 100 = 4% xe-10-0-0.pcl-cr02.plus.net [212.159.0.194]
0/ 100 = 0% |
5 136ms 9/ 100 = 9% 5/ 100 = 5% ae2.pcl-cr01.plus.net [195.166.129.6]
0/ 100 = 0% |
6 149ms 4/ 100 = 4% 0/ 100 = 0% xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
0/ 100 = 0% |
7 140ms 7/ 100 = 7% 3/ 100 = 3% vl-3101-ve-127.ebr1.London2.Level3.net [4.69.202.169]
0/ 100 = 0% |
8 134ms 4/ 100 = 4% 0/ 100 = 0% ae-48-48.ebr1.London15.Level3.net [4.69.159.78]
2/ 100 = 2% |
9 138ms 7/ 100 = 7% 1/ 100 = 1% ae-43-43.ebr1.London1.Level3.net [4.69.167.26]
0/ 100 = 0% |
10 142ms 7/ 100 = 7% 1/ 100 = 1% ae-58-113.csw1.London1.Level3.net [4.69.153.122]
0/ 100 = 0% |
11 145ms 6/ 100 = 6% 0/ 100 = 0% ae-124-3510.edge5.london1.Level3.net [4.69.166.37]
0/ 100 = 0% |
12 139ms 7/ 100 = 7% 1/ 100 = 1% ldn-b5-link.telia.net [213.248.92.81]
0/ 100 = 0% |
13 133ms 7/ 100 = 7% 1/ 100 = 1% ldn-bb1-link.telia.net [80.91.246.144]
0/ 100 = 0% |
14 146ms 7/ 100 = 7% 1/ 100 = 1% prs-bb1-link.telia.net [80.91.247.6]
0/ 100 = 0% |
15 165ms 6/ 100 = 6% 0/ 100 = 0% ffm-bb1-link.telia.net [213.155.132.157]
1/ 100 = 1% |
16 167ms 7/ 100 = 7% 0/ 100 = 0% ffm-b10-link.telia.net [62.115.137.215]
Trace complete.
I routinely (almost every day) have latency issues late at night. This is usually when playing warcraft although it seems to affect webpages too. I have just had some issues and undertook a trace route and pathping as suggested on the warcraft forums. Can anyone advise me on what I can do to resolve these issues?
Thanks
Traceroute
Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:
1 74 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 41 ms 45 ms 39 ms lo0-central10.pcl-ag01.plus.net [195.166.128.182]
3 236 ms 176 ms 222 ms link-b-central10.pcl-gw02.plus.net [212.159.2.162]
4 49 ms 49 ms 48 ms xe-10-0-0.pcl-cr02.plus.net [212.159.0.194]
5 50 ms 39 ms 52 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 50 ms 50 ms 49 ms xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
7 147 ms 293 ms 380 ms vl-3101-ve-127.ebr1.London2.Level3.net [4.69.202.169]
8 46 ms 50 ms 49 ms ae-48-48.ebr1.London15.Level3.net [4.69.159.78]
9 49 ms 50 ms 48 ms ae-43-43.ebr1.London1.Level3.net [4.69.167.26]
10 46 ms 49 ms 50 ms ae-58-113.csw1.London1.Level3.net [4.69.153.122]
11 52 ms 53 ms 52 ms ae-124-3510.edge5.london1.Level3.net [4.69.166.37]
12 45 ms 52 ms 54 ms ldn-b5-link.telia.net [213.248.92.81]
13 46 ms 54 ms 53 ms ldn-bb1-link.telia.net [80.91.246.144]
14 51 ms 60 ms 58 ms prs-bb1-link.telia.net [80.91.247.6]
15 68 ms 66 ms 63 ms ffm-bb1-link.telia.net [80.91.245.102]
16 69 ms 69 ms 67 ms ffm-b10-link.telia.net [62.115.137.131]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Pathping
Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:
0 HomePC.lan []
1 dsldevice.lan [192.168.1.254]
2 lo0-central10.pcl-ag01.plus.net [195.166.128.182]
3 link-b-central10.pcl-gw02.plus.net [212.159.2.162]
4 xe-10-0-0.pcl-cr02.plus.net [212.159.0.194]
5 ae2.pcl-cr01.plus.net [195.166.129.6]
6 xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
7 vl-3101-ve-127.ebr1.London2.Level3.net [4.69.202.169]
8 ae-48-48.ebr1.London15.Level3.net [4.69.159.78]
9 ae-43-43.ebr1.London1.Level3.net [4.69.167.26]
10 ae-58-113.csw1.London1.Level3.net [4.69.153.122]
11 ae-124-3510.edge5.london1.Level3.net [4.69.166.37]
12 ldn-b5-link.telia.net [213.248.92.81]
13 ldn-bb1-link.telia.net [80.91.246.144]
14 prs-bb1-link.telia.net [80.91.247.6]
15 ffm-bb1-link.telia.net [213.155.132.157]
16 ffm-b10-link.telia.net [62.115.137.215]
17 * * *
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 HomePC.lan [192.168.1.69]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% dsldevice.lan [192.168.1.254]
4/ 100 = 4% |
2 143ms 4/ 100 = 4% 0/ 100 = 0% lo0-central10.pcl-ag01.plus.net [195.166.128.182]
0/ 100 = 0% |
3 135ms 7/ 100 = 7% 3/ 100 = 3% link-b-central10.pcl-gw02.plus.net [212.159.2.162]
0/ 100 = 0% |
4 135ms 8/ 100 = 8% 4/ 100 = 4% xe-10-0-0.pcl-cr02.plus.net [212.159.0.194]
0/ 100 = 0% |
5 136ms 9/ 100 = 9% 5/ 100 = 5% ae2.pcl-cr01.plus.net [195.166.129.6]
0/ 100 = 0% |
6 149ms 4/ 100 = 4% 0/ 100 = 0% xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
0/ 100 = 0% |
7 140ms 7/ 100 = 7% 3/ 100 = 3% vl-3101-ve-127.ebr1.London2.Level3.net [4.69.202.169]
0/ 100 = 0% |
8 134ms 4/ 100 = 4% 0/ 100 = 0% ae-48-48.ebr1.London15.Level3.net [4.69.159.78]
2/ 100 = 2% |
9 138ms 7/ 100 = 7% 1/ 100 = 1% ae-43-43.ebr1.London1.Level3.net [4.69.167.26]
0/ 100 = 0% |
10 142ms 7/ 100 = 7% 1/ 100 = 1% ae-58-113.csw1.London1.Level3.net [4.69.153.122]
0/ 100 = 0% |
11 145ms 6/ 100 = 6% 0/ 100 = 0% ae-124-3510.edge5.london1.Level3.net [4.69.166.37]
0/ 100 = 0% |
12 139ms 7/ 100 = 7% 1/ 100 = 1% ldn-b5-link.telia.net [213.248.92.81]
0/ 100 = 0% |
13 133ms 7/ 100 = 7% 1/ 100 = 1% ldn-bb1-link.telia.net [80.91.246.144]
0/ 100 = 0% |
14 146ms 7/ 100 = 7% 1/ 100 = 1% prs-bb1-link.telia.net [80.91.247.6]
0/ 100 = 0% |
15 165ms 6/ 100 = 6% 0/ 100 = 0% ffm-bb1-link.telia.net [213.155.132.157]
1/ 100 = 1% |
16 167ms 7/ 100 = 7% 0/ 100 = 0% ffm-b10-link.telia.net [62.115.137.215]
Trace complete.
Message 1 of 4
(838 Views)
3 REPLIES 3
Re: Latency issues especially late at night
23-06-2014 12:22 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
When you do the trace is anything on your lan actively online? As the last trace should have roughly the same ping. Ran a trace myself and it shows nothing out of the ordinary. So I would check you haven't picked something.
When it happens from dos, type netstat -bn that lists what exe is connected to what IP address on your pc
When it happens from dos, type netstat -bn that lists what exe is connected to what IP address on your pc
FTTP 500 regrade from Tues 28th November
Message 2 of 4
(512 Views)
Re: Latency issues especially late at night
23-06-2014 1:34 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I haven't been able to run a reliable latency test (why don't plusnet provide a utility like TalkTalk do for this?), but I too have noticed latency issues.
A speedtest on my line at bt wholesale shows good line speed - 6mbs down and 780kbs up with latency stated at 45ms.
However, the last few nights, it's been taking ages for web pages to come up / turn and sometimes the request has had to be resent. I can only put this down to high latency spikes and or packet loss.
BTW, pingtest isn't very good for this purpose :
1. The latency test isn't working following the latest Java update (it tells you, you don't have Java)
2. In any event, past experience has shown that if you have a latency issue, the utility just hangs until the latency spike is over so it doesn't show in the results unless of course it reoccurs mid test. If it hangs for too long then the test ends without recording anything. Hence why Pluisnet could really do with a small desktop utility such as that on TalkTalk (their utility pings the route to a predetermined talktalk server or several popular websites (you choose before starting the test), and pings every hop 3 times recording the latency each time. It does this incrementally so rather than pinging the whole route 3 times, it does hop 1 x 3 times, then hop 2 x 3 times, then hop 3 x 3 times etc. I found this quite useful in the past for proving latency / packet loss issues as it records every hop in a table and the result can then be copied to a forum or support.
EDIT: just discovered I still have a copy of their utility but it looks as if the plusnet server ignores ping requests as all timed out.
A speedtest on my line at bt wholesale shows good line speed - 6mbs down and 780kbs up with latency stated at 45ms.
However, the last few nights, it's been taking ages for web pages to come up / turn and sometimes the request has had to be resent. I can only put this down to high latency spikes and or packet loss.
BTW, pingtest isn't very good for this purpose :
1. The latency test isn't working following the latest Java update (it tells you, you don't have Java)
2. In any event, past experience has shown that if you have a latency issue, the utility just hangs until the latency spike is over so it doesn't show in the results unless of course it reoccurs mid test. If it hangs for too long then the test ends without recording anything. Hence why Pluisnet could really do with a small desktop utility such as that on TalkTalk (their utility pings the route to a predetermined talktalk server or several popular websites (you choose before starting the test), and pings every hop 3 times recording the latency each time. It does this incrementally so rather than pinging the whole route 3 times, it does hop 1 x 3 times, then hop 2 x 3 times, then hop 3 x 3 times etc. I found this quite useful in the past for proving latency / packet loss issues as it records every hop in a table and the result can then be copied to a forum or support.
EDIT: just discovered I still have a copy of their utility but it looks as if the plusnet server ignores ping requests as all timed out.
Message 3 of 4
(512 Views)
Re: Latency issues especially late at night
23-06-2014 9:46 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Do you have a TBB Graph that we can look at?
http://community.plus.net/forum/index.php/topic,106312.0.html
http://community.plus.net/forum/index.php/topic,106312.0.html
Message 4 of 4
(512 Views)
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: Latency issues especially late at night