cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
rcolbyuk
Beginner
907 Views
Message 71 of 82

Re: PACKETLOSS BT ISSUE!!

I did speak to soon, SkyGo was buffering all over the place when I tried later on about 12am, strange how NetFlix was fine (something to do with the latest TV adverts!).

 

Below link says it all really and don't see any improvement in the customer service since Jan.

http://www.thisismoney.co.uk/money/news/article-2539447/Wooden-Spoon-2014-BT-wins-worst-customer-ser...

 

It's good to talk, remember that! Communication is all that is required, most people are fine with issues if they are kept informed, maybe it not a quick fix so dont want to lose customer (well they will anyway if it doesnt work correctly!). I'll be happy if someone said, look we have a capacity issue here is the plan over the next few weeks to improve the service.

 

Thanks

Rich

 

 

 

 

0 Ratings
dfenceman
Expert
879 Views
Message 72 of 82

Re: PACKETLOSS BT ISSUE!!

What I don't understand is how everything works fine from my neighbour's who is with TalkTalk.  Not LLU though !

Best regards,
dfenceman
0 Ratings
john46
Distinguished Sage
861 Views
Message 73 of 82

Re: PACKETLOSS BT ISSUE!!

@dfenceman simple answer different network routing to BT
0 Ratings
DavidM
Moderator
Moderator
848 Views
Message 74 of 82

Re: PACKETLOSS BT ISSUE!!

Hi all,

 

Thanks for posting. We’ve had an update form wholesale and the Manchester exchange issue should now be sorted. Can you run the usual checks (speed test and tracerts)and post the results so we can confirm that with wholesale for you.

 

Cheers

 

David

 

0 Ratings
Fellblade
Aspiring Contributor
818 Views
Message 75 of 82

Re: PACKETLOSS BT ISSUE!!

A helpful chap on this thread I made in a great deal of frustration pointed me here - I'm getting exactly the same issues connecting with Infinity 2 to both EVE Online and a lot of US sites... and the BT community site itself! The post with my tracert etc can be found here

0 Ratings
wush786
Contributor
812 Views
Message 76 of 82

Re: PACKETLOSS BT ISSUE!!

just done a fresh new 1 . this is a trace route to blizzard servers on the time it was giving me packetloss

 
 Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\wush>tracert 195.12.232.102
 
Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:
 
  1    <1 ms     1 ms    <1 ms  BThomehub.home [192.168.1.254]
  2    29 ms    28 ms    30 ms  213.1.177.186
  3    28 ms    29 ms    28 ms  213.1.177.161
  4    30 ms    29 ms    30 ms  213.1.69.194
  5    32 ms    32 ms    33 ms  31.55.165.103
  6    29 ms    29 ms    30 ms  31.55.165.195
  7    29 ms    29 ms    29 ms  31.55.165.109
  8    28 ms    28 ms    30 ms  acc2-10GigE-0-2-0.mr.21cn-ipp.bt.net [109.159.25
0.194]
  9    39 ms    39 ms    40 ms  109.159.252.223
 10    37 ms    38 ms    35 ms  peer2-xe0-0-1.telehouse.ukcore.bt.net [109.159.2
54.138]
 11    35 ms    34 ms    34 ms  166-49-211-238.eu.bt.net [166.49.211.238]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 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.
 
And now for a pathping 
 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\wush>pathping 213.155.152.66
 
Tracing route to 213-155-152-66.customer.teliacarrier.com [213.155.152.66]
over a maximum of 30 hops:
  0  wush-PC.home [192.168.1.65]
  1  BThomehub.home [192.168.1.254]
  2  213.1.177.186
  3  213.1.177.161
  4  213.1.69.194
  5  31.55.165.103
  6  31.55.165.195
  7  31.55.165.109
  8  acc2-xe-4-2-2.mr.21cn-ipp.bt.net [109.159.250.244]
  9  core2-te0-0-0-17.ealing.ukcore.bt.net [109.159.250.158]
 10     *        *     peer6-te0-9-0-9.telehouse.ukcore.bt.net [109.159.254.163]
 
 11  166-49-211-242.eu.bt.net [166.49.211.242]
 12  213.248.82.249
 13     *     ldn-bb2-link.telia.net [62.115.137.192]
 14  prs-bb2-link.telia.net [80.91.247.240]
 15  prs-b7-link.telia.net [213.155.134.227]
 16     *        *        *
Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           wush-PC.home [192.168.1.65]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  BThomehub.home [192.168.1.254]
                               28/ 100 = 28%   |
  2   29ms    34/ 100 = 34%     6/ 100 =  6%  213.1.177.186
                                0/ 100 =  0%   |
  3   38ms    34/ 100 = 34%     6/ 100 =  6%  213.1.177.161
                                0/ 100 =  0%   |
  4   29ms    28/ 100 = 28%     0/ 100 =  0%  213.1.69.194
                                2/ 100 =  2%   |
  5   29ms    32/ 100 = 32%     2/ 100 =  2%  31.55.165.103
                                0/ 100 =  0%   |
  6  ---     100/ 100 =100%    70/ 100 = 70%  31.55.165.195
                                0/ 100 =  0%   |
  7   29ms    30/ 100 = 30%     0/ 100 =  0%  31.55.165.109
                                1/ 100 =  1%   |
  8   32ms    33/ 100 = 33%     2/ 100 =  2%  acc2-xe-4-2-2.mr.21cn-ipp.bt.net [
109.159.250.244]
                                0/ 100 =  0%   |
  9   37ms    31/ 100 = 31%     0/ 100 =  0%  core2-te0-0-0-17.ealing.ukcore.bt.
net [109.159.250.158]
                                0/ 100 =  0%   |
 10   37ms    34/ 100 = 34%     3/ 100 =  3%  peer6-te0-9-0-9.telehouse.ukcore.b
t.net [109.159.254.163]
                                0/ 100 =  0%   |
 11   37ms    34/ 100 = 34%     3/ 100 =  3%  166-49-211-242.eu.bt.net [166.49.2
11.242]
                                0/ 100 =  0%   |
 12   42ms    35/ 100 = 35%     4/ 100 =  4%  213.248.82.249
                                0/ 100 =  0%   |
 13   43ms    31/ 100 = 31%     0/ 100 =  0%  ldn-bb2-link.telia.net [62.115.137
.192]
                                1/ 100 =  1%   |
 14   57ms    37/ 100 = 37%     5/ 100 =  5%  prs-bb2-link.telia.net [80.91.247.
240]
                                0/ 100 =  0%   |
 15   45ms    32/ 100 = 32%     0/ 100 =  0%  prs-b7-link.telia.net [213.155.134
.227]
 
Trace complete.
 
This all started around 6 o clock. an it will now stay like this till 11- 1 in the morning ...

 

 

0 Ratings
het_uk
Aspiring Expert
703 Views
Message 77 of 82

Re: PACKETLOSS BT ISSUE!!

David,

 

Was this at a particular Manchester exchange, or at a PoP in Manchester?

0 Ratings
NeilO
Moderator
Moderator
699 Views
Message 78 of 82

Re: PACKETLOSS BT ISSUE!!

Hi het_uk

 

The fault was down to an incorrectly configured FTHL link on the BTR dedicated network.

 

Neil

 

0 Ratings
Gazjon
Beginner
692 Views
Message 79 of 82

Re: PACKETLOSS BT ISSUE!!

"Hi het_uk

 

The fault was down to an incorrectly configured FTHL link on the BTR dedicated network.

 

Neil"

 

Wow Red Dwarf has a lot to answer for. Faster Than Hard Light problems used to bug Rimmer something chronic.

 

My connection has certainly improved since the reconfiguration. Now if only the DDOS attacks on parts of the internet would reduce.

 

Thanks for the notifications Neil and crew.

0 Ratings
het_uk
Aspiring Expert
666 Views
Message 80 of 82

Re: PACKETLOSS BT ISSUE!!


@wush786 wrote:

 

Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           wush-PC.home [192.168.1.65]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  BThomehub.home [192.168.1.254]
                               28/ 100 = 28%   |
  2   29ms    34/ 100 = 34%     6/ 100 =  6%  213.1.177.186
                                0/ 100 =  0%   |
  3   38ms    34/ 100 = 34%     6/ 100 =  6%  213.1.177.161
                                0/ 100 =  0%   |
  4   29ms    28/ 100 = 28%     0/ 100 =  0%  213.1.69.194
                                2/ 100 =  2%   |
  5   29ms    32/ 100 = 32%     2/ 100 =  2%  31.55.165.103
                                0/ 100 =  0%   |
  6  ---     100/ 100 =100%    70/ 100 = 70%  31.55.165.195
                                0/ 100 =  0%   |
  7   29ms    30/ 100 = 30%     0/ 100 =  0%  31.55.165.109
                                1/ 100 =  1%   |
  8   32ms    33/ 100 = 33%     2/ 100 =  2%  acc2-xe-4-2-2.mr.21cn-ipp.bt.net [
109.159.250.244]
                                0/ 100 =  0%   |
  9   37ms    31/ 100 = 31%     0/ 100 =  0%  core2-te0-0-0-17.ealing.ukcore.bt.
net [109.159.250.158]
                                0/ 100 =  0%   |
 10   37ms    34/ 100 = 34%     3/ 100 =  3%  peer6-te0-9-0-9.telehouse.ukcore.b
t.net [109.159.254.163]
                                0/ 100 =  0%   |
 11   37ms    34/ 100 = 34%     3/ 100 =  3%  166-49-211-242.eu.bt.net [166.49.2
11.242]
                                0/ 100 =  0%   |
 12   42ms    35/ 100 = 35%     4/ 100 =  4%  213.248.82.249
                                0/ 100 =  0%   |
 13   43ms    31/ 100 = 31%     0/ 100 =  0%  ldn-bb2-link.telia.net [62.115.137
.192]
                                1/ 100 =  1%   |
 14   57ms    37/ 100 = 37%     5/ 100 =  5%  prs-bb2-link.telia.net [80.91.247.
240]
                                0/ 100 =  0%   |
 15   45ms    32/ 100 = 32%     0/ 100 =  0%  prs-b7-link.telia.net [213.155.134
.227]
 
Trace complete.
 
This all started around 6 o clock. an it will now stay like this till 11- 1 in the morning ...

 

 


With respect. wush768 - you are seeing packet loss at hop 1.  That's YOUR router.  If you're losing packets between your PC and your router that's NOTHING to do with BT's network.  It has EVERYTHING to do with why you're seeing packet loss further down the line though.

0 Ratings