From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by huchra.bufferbloat.net (Postfix) with ESMTP id 0708E21F5FA for ; Thu, 18 Jun 2015 12:32:37 -0700 (PDT) Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id DC547406057; Thu, 18 Jun 2015 12:32:33 -0700 (PDT) X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: bloat@lists.bufferbloat.net From: Hal Murray Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jun 2015 12:32:33 -0700 Message-Id: <20150618193233.DC547406057@ip-64-139-1-69.sjc.megapath.net> Cc: Hal Murray 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: Thu, 18 Jun 2015 19:33:06 -0000 I don't think you can measure backbone loss using ping unless you control both ends and ensure that both last-miles are not contributing to the problem. I think there are several different areas to investigate. The main one is whether your packet gets handed off between two "backbone" IPSs that are currently squabbling about who is going to pay whom how much. The obvious example is Netflix vs Comcast. I don't have any numbers, but I think over the past 5 or 10 years, all the major ISPs have set things up so that all their internal links are overprovisioned. You might notice packet loss when a link goes down and the traffic patterns get rearranged. (I know you can see changes in transit time using NTP.) I have an old/slow DLS link. I get close to 0% packet loss if my last mile is not busy and lots of loss when it is overloaded. -- These are my opinions. I hate spam.