Other destinations are fine, but I've never seen this behavior before on this link. Excellent points though, thanks for contributing. I've engaged cogent for a peek. FWIW, they say they still have a lot of the NYC area on backup power and even had a batch of "bad fuel" delivered to at least one site. Sandy is still causing them headaches. ~Jeff Agle -----Original Message----- From: Jonathan Lassoff [mailto:jof@thejof.com] Sent: Sunday, November 18, 2012 2:33 AM To: Agle, Jeff Cc: outages@outages.org Subject: Re: [outages] Cogent/Level3 peering issue? On Sat, Nov 17, 2012 at 11:19 PM, Agle, Jeff <jeff.agle@financialpartners.com> wrote:
I'm seeing a lot of high latency and packet loss from my Cogent Co. link in MA towards IP 4.2.2.2. Not present on other local ISP. Traces would seem to indicate the problem is at Cogent's POP to L3. Can anyone confirm, or sympathize?
As discussed many times on here in the past, 4.2.2.2 is a bad (statistically) place to point measurements at. While publicly addressable and pingable, it's sometimes rate-limited. FWIW, I can connect and query the San Jose anycast site just fine. If you're interested in the 4.2.2.2 / 4.2.2.1 resolvers, by all means ping and measure them based on DNS response time. However, if you're just looking for an indication of routing-path health, try measuring other destinations that take similar paths and summarize those points to factor out the behavior of 4.2.2.0/29 hosts. Cheers, jof ---------------------------------------------------------------------- CONFIDENTIALITY NOTICE: This e-mail transmission may contain confidential information. This information is solely for the use of the individual(s) or entity to whom or which it was intended. If not an intended recipient, any review, copying, printing, disclosure, distribution or any other use is strictly prohibited. If you have received this email in error, please immediately notify the sender by reply e-mail. Please delete this e-mail from your files if you are not the intended recipient. Thank you.