| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
X-Original-To: nanog@nanog.org
Date: Mon, 16 May 2016 20:03:52 +0000 (UTC)
To: David Hubbard <dhubbard@dino.hostasaurus.com>,
"nanog@nanog.org" <nanog@nanog.org>
In-Reply-To: <443BEA4A-3E0C-4852-A3F3-4733BF2C6985@dino.hostasaurus.com>
From: Tom Beecher via NANOG <nanog@nanog.org>
Reply-To: Tom Beecher <beecher@yahoo-inc.com>
Errors-To: nanog-bounces@nanog.org
Was looking at an internal report not long ago. L3 NYC to Miami looked to b=
e in really rough shape. As I was watching, things flipped inside L3 to go =
NYC->Boston, then handed off to Cogent.=C2=A0
Didn't dig further than that, but methinks they have something going on, ye=
s.=C2=A0=C2=A0Thanks,
Beecher
=20
On Monday, May 16, 2016 3:51 PM, David Hubbard <dhubbard@dino.hostasaur=
us.com> wrote:
=20
Anyone seeing issues with Level 3 networking right now?=C2=A0 We=E2=80=99r=
e seeing huge latency and loss on traffic coming inbound (to us, AS33260) b=
ut it seems to be at the peering points with other major ISP=E2=80=99s and =
Level 3.=C2=A0 Comcast for example:
=C2=A0 3=C2=A0 =C2=A0 33 ms=C2=A0 =C2=A0 21 ms=C2=A0 =C2=A0 70 ms=C2=A0 te-=
3-5-ur01.hershey.pa.pitt.comcast.net [68.85.42.29]
=C2=A0 4=C2=A0 =C2=A0 *=C2=A0 =C2=A0 =C2=A0 33 ms=C2=A0 106 ms=C2=A0 162.15=
1.48.173
=C2=A0 5=C2=A0 214 ms=C2=A0 =C2=A0 54 ms=C2=A0 =C2=A0 41 ms=C2=A0 162.151.2=
1.229
=C2=A0 6=C2=A0 561 ms=C2=A0 764 ms=C2=A0 459 ms=C2=A0 4.68.71.133
Thanks,
David
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |