From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g4t3426.houston.hp.com (g4t3426.houston.hp.com [15.201.208.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smtp.hpe.com", Issuer "Symantec Class 3 Secure Server CA - G4" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 4A42A21F3DE for ; Wed, 17 Jun 2015 13:34:21 -0700 (PDT) Received: from g4t3433.houston.hp.com (g4t3433.houston.hp.com [16.210.25.219]) by g4t3426.houston.hp.com (Postfix) with ESMTP id B3CFC1D8 for ; Wed, 17 Jun 2015 20:34:20 +0000 (UTC) Received: from [16.103.148.51] (tardy.usa.hp.com [16.103.148.51]) by g4t3433.houston.hp.com (Postfix) with ESMTP id 1A86472 for ; Wed, 17 Jun 2015 20:34:18 +0000 (UTC) Message-ID: <5581D9CA.40201@hp.com> Date: Wed, 17 Jun 2015 13:34:18 -0700 From: Rick Jones User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: bloat@lists.bufferbloat.net References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Bloat] backbone loss statistics over the past 15 years or so? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2015 20:34:50 -0000 > Now in 2015 I notice that it is at 0% packet loss worldwide. Looks > like the big boys found a way to fight any connection speed, and > buffer issues that where the cause of what was an ever increasing > packet loss issue. My wish is that it would now make it all the way > down to the end of the last mile. The issues with packet loss due to > buffer bloat that are now at the end of the home and business > connections I feel helps lead to the congestion issues we see during > the high use periods at night. " http://www.internettrafficreport.com/faq.htm#measure > Q: How do you measure "Internet traffic?" > A: A test called "ping" is used to measure round-trip travel time > along major paths on the Internet. We have several servers in > different areas of the globe perform the same ping at the same time. > Each test server then compares the current response to past responses > from the same test to determine if the response was bad or good on a > scale of 0 to 100. The scores from all test servers are averaged > together into a single index. If you drill-down on regions, it will show individual routers. The results seem to be particularly binary - a given router will have either an index of 100 and a loss percentage of 0, or an index of 0 and a loss percentage of 100. Asia seems to have a couple exceptions proving the rule. You will probably get a kick out of: http://www.internettrafficreport.com/faq.htm#packet I'm not sure if they are setup to report fractional packet loss percentages