Major Packet Loss [ Edited ]

[al2k4]

Who else is getting major packet loss to various US websites including twitter.com?

Here's my ping log:

ping twitter.com /t

Pinging twitter.com [199.59.150.39] with 32 bytes of data
Request timed out.
Request timed out.
Reply from 199.59.150.39: bytes=32 time=172ms TTL=236
Reply from 199.59.150.39: bytes=32 time=158ms TTL=236
Request timed out.
Request timed out.

... (and so on)

Ping statistics for 199.59.150.39:
Packets: Sent = 84, Received = 32, Lost = 52 (61% loss),
Approximate round trip times in milli-seconds:
Minimum = 158ms, Maximum = 230ms, Average = 168ms

The 61% packet loss is causing the Internet to slow down to a crawl...

I have pinged from an external machine and all seems fine there, what is going on?

This is on BT Infinity.

[MilanoChris]

Yes same here. Plus loads of UK sites too. I'm located in Watford.

[patC]

Hi,

Yes I'm experiencing the same thing and it's very annoying as several of the servers I host out there are affected - one of which is a streaming service which BT is currently making look really awful.

The problem lies with BTs peering with above.net in London. Here is an MTR trace to one of the IP addresses:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| FTTC-BT - 0 | 453 | 453 | 0 | 0 | 0 | 0 |
| 217.32.143.131 - 0 | 453 | 453 | 12 | 12 | 13 | 12 |
| 217.32.143.158 - 0 | 453 | 453 | 12 | 16 | 177 | 111 |
| 213.120.181.238 - 0 | 453 | 453 | 12 | 12 | 13 | 13 |
| 217.41.169.73 - 0 | 453 | 453 | 12 | 12 | 15 | 13 |
| 217.41.169.107 - 0 | 453 | 453 | 12 | 13 | 15 | 13 |
| acc1-10GigE-9-2-0.sf.21cn-ipp.bt.net - 0 | 453 | 453 | 12 | 14 | 82 | 12 |
| core1-te0-2-3-0.ealing.ukcore.bt.net - 0 | 453 | 453 | 17 | 22 | 140 | 26 |
| peer1-xe0-1-0.redbus.ukcore.bt.net - 0 | 453 | 453 | 19 | 22 | 80 | 20 |
| ge-2-1-0.mpr1.lhr2.uk.above.net - 40 | 177 | 107 | 18 | 26 | 143 | 21 |
| ge-4-1-0.mpr1.lhr2.uk.above.net - 39 | 178 | 109 | 19 | 22 | 91 | 19 |
| xe-5-2-0.cr1.dca2.us.above.net - 35 | 192 | 126 | 92 | 95 | 146 | 129 |
| xe-2-2-0.cr1.iah1.us.above.net - 41 | 173 | 103 | 118 | 123 | 173 | 120 |
| xe-1-2-0.cr1.dfw2.us.above.net - 36 | 189 | 122 | 122 | 128 | 183 | 126 |
| xe-0-0-0.er3.dfw2.us.above.net - 36 | 189 | 122 | 125 | 131 | 201 | 163 |
| 64.124.193.221.t01263-01.above.net - 39 | 178 | 109 | 123 | 131 | 198 | 124 |
| xe-5-3-0.core4.dllstx01.corexchange.com - 38 | 182 | 114 | 124 | 132 | 234 | 124 |
| premium-network.incero.com - 37 | 186 | 119 | 122 | 125 | 155 | 123 |
| cg.incero.com - 33 | 197 | 132 | 123 | 125 | 190 | 129 |
| 23.29.127.154 - 31 | 205 | 142 | 124 | 126 | 154 | 129 |
| 108.166.187.35 - 37 | 185 | 117 | 124 | 126 | 194 | 124 |
|________________________________________________|______|______|______|______|______|______|

Sort it out BT!

[MilanoChris]

Seems like a router has gone down, or a node. They should use HSRP.

[john46]

have you checked either the status page https://www.bt.com/consumerFaultTracking/public/faults/tracking.do?pageId=31
or the staus line on 0800 169 0199

[patC]

The status page shows the problem as resolved from this morning (it was the same problem). This problem isn't even showing up. And it's going on far too long. Someone somewhere must be either frantic or completely ignorant to the situation and I don't know which.

[john46]

no problems here and there are only a few posts here on the subject it certainly does not seem to worrying many posters

[patC]

John,

I think that is because you're not trying to reach hosts which BT have chosen to route through above.net. It's not all websites by any degree, it's a portion of those hosted in the states by all accounts. I have 7 servers over there on 4 different, geographically seperated hosting providers. 5 are affected by this.

IDNet is my primary broadband connection and it is showing zero loss to any of my servers.

I have customers complaining to me that they are barely able to reach my site(s). It is not as tiny a problem as you might think, given pinging even twitter.com is giving terrible results also.

Pat

[MilanoChris]

There's clearly a large issue somewhere.

[john46]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jhon>tracert twitter.com

Tracing route to twitter.com [199.59.148.82]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms api.home [192.168.1.254]
2 15 ms 15 ms 15 ms 217.32.147.5
3 18 ms 17 ms 17 ms 217.32.147.46
4 20 ms 19 ms 19 ms 213.120.177.66
5 19 ms 19 ms 19 ms 217.41.168.237
6 19 ms 19 ms 19 ms 217.41.168.109
7 19 ms 19 ms 19 ms 109.159.249.246
8 25 ms 23 ms 24 ms core2-te0-0-0-16.faraday.ukcore.bt.net [109.159.
249.131]
9 19 ms 19 ms 19 ms peer1-xe-8-0-1.redbus.ukcore.bt.net [213.121.193
.91]
10 20 ms * 20 ms ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]

11 20 ms * 20 ms ge-2-1-0.mpr1.lhr2.uk.above.net [64.125.28.141]

12 20 ms 20 ms 20 ms so-1-1-0.mpr1.dca2.us.above.net [64.125.31.186]

13 20 ms 21 ms 20 ms xe-1-3-0.cr1.dca2.us.above.net [64.125.29.21]
14 24 ms 23 ms 23 ms xe-3-2-0.er1.iad10.us.above.net [64.125.29.209]

15 24 ms 24 ms 23ms 209.66.115.18.t01337-05.above.net [209.66.115.18
]
16 58 ms 59 ms 90 ms ae60.pao1-cr2.twttr.com [199.16.159.87]
17 62 ms 64 ms 70 ms ae51.smf1-er1.twttr.com [199.16.159.29]
18 63 ms 63ms  62 ms r-199-59-148-82.twttr.com [199.59.148.82]

Trace complete.

The only  noticable  problem  i can see there is with twitter them selves