cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Moderator
Moderator
625 Views
Message 51 of 260

Re: Major Packet Loss

Hi Randal24

 

We will keep this thread updated when we get an update on the investigation.

 

Thanks

 

Stuart

 

 

0 Ratings
Highlighted
Aspiring Contributor
573 Views
Message 52 of 260

Re: Major Packet Loss

Post made in error.

0 Ratings
Highlighted
Contributor
566 Views
Message 53 of 260

Re: Major Packet Loss

I have also experianced packet loss with above.net for the last 3 evenings between 7pm and midnight this has caused me disconnections and i am now having to use another connection with another isp and there connection is rock stable!!!

 

when will this be fixed????

 

Its quite sad that i have a bt infinity 2 connection thats not as stable as my dial up or adsl connection that i have to use for a reliable connection come on sort this out asap please!

 

Pinging battlefield.com [72.32.103.134] with 32 bytes of data:
Reply from 72.32.103.134: bytes=32 time=125ms TTL=236
Reply from 72.32.103.134: bytes=32 time=122ms TTL=236
Request timed out.
Request timed out.
Reply from 72.32.103.134: bytes=32 time=122ms TTL=236
Request timed out.
Reply from 72.32.103.134: bytes=32 time=122ms TTL=236
Request timed out.
Reply from 72.32.103.134: bytes=32 time=125ms TTL=236
Reply from 72.32.103.134: bytes=32 time=122ms TTL=236
Reply from 72.32.103.134: bytes=32 time=123ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Request timed out.

Ping statistics for 72.32.103.134:
Packets: Sent = 13, Received = 8, Lost = 5 (38% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 125ms, Average = 122ms
Control-C

 

C:\>ping -t battlefield.com

Pinging battlefield.com [72.32.103.134] with 32 bytes of data:
Reply from 72.32.103.134: bytes=32 time=115ms TTL=225
Reply from 72.32.103.134: bytes=32 time=115ms TTL=225
Reply from 72.32.103.134: bytes=32 time=115ms TTL=225
Reply from 72.32.103.134: bytes=32 time=114ms TTL=225
Reply from 72.32.103.134: bytes=32 time=114ms TTL=225
Reply from 72.32.103.134: bytes=32 time=115ms TTL=225
Reply from 72.32.103.134: bytes=32 time=115ms TTL=225
Reply from 72.32.103.134: bytes=32 time=114ms TTL=225
Request timed out.
Request timed out.
Reply from 72.32.103.134: bytes=32 time=114ms TTL=225
Request timed out.
Reply from 72.32.103.134: bytes=32 time=115ms TTL=225
Reply from 72.32.103.134: bytes=32 time=114ms TTL=225
Reply from 72.32.103.134: bytes=32 time=115ms TTL=225
Reply from 72.32.103.134: bytes=32 time=114ms TTL=225
Reply from 72.32.103.134: bytes=32 time=125ms TTL=225
Reply from 72.32.103.134: bytes=32 time=115ms TTL=225
Reply from 72.32.103.134: bytes=32 time=114ms TTL=225
Reply from 72.32.103.134: bytes=32 time=114ms TTL=225
Reply from 72.32.103.134: bytes=32 time=114ms TTL=225
Request timed out.
Reply from 72.32.103.134: bytes=32 time=114ms TTL=225
Reply from 72.32.103.134: bytes=32 time=115ms TTL=225
Request timed out.

Ping statistics for 72.32.103.134:
Packets: Sent = 25, Received = 20, Lost = 5 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 114ms, Maximum = 125ms, Average = 115ms
Control-C
^C
C:\>

C:\>ping -t battlefield.com

Pinging battlefield.com [72.32.103.134] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Reply from 72.32.103.134: bytes=32 time=125ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Request timed out.
Reply from 72.32.103.134: bytes=32 time=122ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Request timed out.
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236

Ping statistics for 72.32.103.134:
Packets: Sent = 21, Received = 16, Lost = 5 (23% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 125ms, Average = 120ms
Control-C
^C
C:\>

C:\>ping -t battlefield.com

Pinging battlefield.com [72.32.103.134] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Reply from 72.32.103.134: bytes=32 time=125ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Request timed out.
Reply from 72.32.103.134: bytes=32 time=122ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Request timed out.
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236

Ping statistics for 72.32.103.134:
Packets: Sent = 21, Received = 16, Lost = 5 (23% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 125ms, Average = 120ms
Control-C
^C
C:\>ping -t battlefield.com

Pinging battlefield.com [72.32.103.134] with 32 bytes of data:
Reply from 72.32.103.134: bytes=32 time=121ms TTL=236
Reply from 72.32.103.134: bytes=32 time=131ms TTL=236
Reply from 72.32.103.134: bytes=32 time=159ms TTL=236
Reply from 72.32.103.134: bytes=32 time=122ms TTL=236
Reply from 72.32.103.134: bytes=32 time=123ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=123ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Request timed out.
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Reply from 72.32.103.134: bytes=32 time=120ms TTL=236
Request timed out.

Ping statistics for 72.32.103.134:
Packets: Sent = 13, Received = 11, Lost = 2 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 159ms, Average = 125ms
Control-C
^C
C:\>tracert battlefield.com

Tracing route to battlefield.com [72.32.103.134]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BTHomeHub.home [192.168.1.254]
2 8 ms 7 ms 7 ms 217.32.145.137
3 66 ms 8 ms 8 ms 217.32.145.206
4 8 ms 8 ms 8 ms 213.120.156.58
5 8 ms 8 ms 8 ms 217.41.168.35
6 9 ms 8 ms 8 ms 217.41.168.107
7 8 ms 8 ms 8 ms 109.159.249.112
8 11 ms 15 ms 15 ms core1-te0-15-0-7.faraday.ukcore.bt.net [109.159.
249.37]
9 17 ms 8 ms 9 ms host213-121-193-115.ukcore.bt.net [213.121.193.1
15]
10 * * 9 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]

11 11 ms 10 ms 12 ms ge-3-0-0.mpr1.lhr2.uk.above.net [64.125.28.126]

12 115 ms 83 ms 85 ms xe-5-2-0.cr1.dca2.us.above.net [64.125.26.21]
13 117 ms 108 ms 107 ms xe-2-2-0.cr1.iah1.us.above.net [64.125.29.37]
14 115 ms 113 ms 113 ms xe-2-1-0.cr1.dfw2.us.above.net [64.125.30.58]
15 113 ms 113 ms 113 ms xe-8-2-1.er1.dfw2.us.above.net [64.125.30.85]
16 120 ms 120 ms 120 ms main1.above.net [209.133.126.42]
17 122 ms 125 ms 126 ms coreb.dfw1.rackspace.net [74.205.108.40]
18 122 ms 120 ms 120 ms core7.dfw1.rackspace.net [74.205.108.31]
19 120 ms 120 ms 123 ms aggr502a-2-core7.dfw1.rackspace.net [98.129.84.2
3]
20 121 ms * 120 ms 72.32.103.134

Trace complete.

 

0 Ratings
Highlighted
Moderator
Moderator
551 Views
Message 54 of 260

Re: Major Packet Loss

Hi Guys

 

An investigation has been raised today and it has been escalated to try to resolve the issue, we will monitor and update here as and when we get the updates.

 

Thanks

 

Stuart

0 Ratings
Highlighted
Contributor
545 Views
Message 55 of 260

Re: Major Packet Loss

I am having packet loss now and it gets worse in the evening this has made my bt infinity2 connection unrealiable and i am having to use another isp to connect.

 

i am losing packets as below on hop 2,3 which i believe is bt also on above.net hops come on BT sort out what has been a great connection for the last 6 months that now for the last four days has been offline allmost every day and when its up i drops packets!!!  other isp's are fine it just seems that infinity is not.

 

 

 

WinMTR statistics

 

Host%SentRecvBestAvrgWrstLast
BTHomeHub.home01001000000
217.32.145.13701001007788
217.32.145.20639290713888
213.120.177.2296958898
217.41.168.7501001008898
217.41.168.10701001008898
109.159.249.6801001007898
core1-te0-0-0-7.faraday.ukcore.bt.net01001008111711
peer1-xe-8-1-0.redbus.ukcore.bt.net010010089518
ge-2-1-0.mpr1.lhr2.uk.above.net39290810579
ge-4-1-0.mpr1.lhr2.uk.above.net78075810539
xe-5-2-0.cr1.dca2.us.above.net7807580819984
xe-4-0-0.cr1.iah1.us.above.net87670107110140111
xe-1-2-0.cr1.dfw2.us.above.net107265112115178115
xe-0-1-0.er1.dfw2.us.above.net87670112115153113
main1.above.net156455113119125121
corea.dfw1.rackspace.net87670114119122120
core7.dfw1.rackspace.net77974114121124123
aggr502a-2-core7.dfw1.rackspace.net1072650119121120
72.32.103.13448885114119124121
0 Ratings
Highlighted
Aspiring Contributor
518 Views
Message 56 of 260

Re: Major Packet Loss

I can concurr with others that it has already started this evening.

 

 

WinMTR statistics

 

Host%SentRecvBestAvrgWrstLast
FTTC-BT01011010000
217.32.143.131010110112121312
217.32.143.1580101101121512012
213.120.181.238010110112121413
217.41.169.33010110112121313
217.41.169.107010110113131413
109.159.251.85010110112137012
core2-te-0-3-0-3.ilford.ukcore.bt.net010110119243125
62.6.200.199010110119229319
ge-2-1-0.mpr1.lhr2.uk.above.net7827719207319
ge-4-1-0.mpr1.lhr2.uk.above.net5868219203619
xe-5-2-0.cr1.dca2.us.above.net176252909211490
xe-1-3-0.cr1.iah1.us.above.net58682117120152119
xe-2-1-0.cr1.dfw2.us.above.net97871122124167123
xe-0-0-0.er3.dfw2.us.above.net107467122125215152
64.124.193.221.t01263-01.above.net87872122127189139
xe-5-3-0.core4.dllstx01.corexchange.com87872124129195124
premium-network.incero.com58783123124131126
cg.incero.com78277126126131126
23.29.127.15449087126126130126
108.166.187.3558682123124131124
0 Ratings
Highlighted
Contributor
509 Views
Message 57 of 260

Re: Major Packet Loss

Any official word from BT on the topic yet?  Has it even made it to their fault board?

0 Ratings
Highlighted
Contributor
497 Views
Message 58 of 260

Re: Major Packet Loss

@ randal24, nothing on the service status as of yet
0 Ratings
Highlighted
Aspiring Expert
494 Views
Message 59 of 260

Re: Major Packet Loss

Here we go again - been working OK'ish on and off all day and now it has finally broken lol!  Really need FTP access to my server but not much chance at the mo!

0 Ratings
Highlighted
Contributor
487 Views
Message 60 of 260

Re: Major Packet Loss

yes it has started again - downhill now until about 12 am

0 Ratings