[184108] in North American Network Operators' Group
Recent trouble with QUIC?
daemon@ATHENA.MIT.EDU (Ca By)
Fri Sep 25 19:20:48 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <CABJRgnVV7-6JAz40dRyK02sB_qCAFBmxLZ82YArwF29UoLiKQg@mail.gmail.com>
Date: Fri, 25 Sep 2015 16:20:44 -0700
From: Ca By <cb.list6@gmail.com>
To: Cody Grosskopf <codygrosskopf@gmail.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Friday, September 25, 2015, Cody Grosskopf <codygrosskopf@gmail.com
<javascript:_e(%7B%7D,'cvml','codygrosskopf@gmail.com');>> wrote:
> a) yes, 56,000 students and any on Chrome failed. I immediately blocked
> quic and told users to restart Chrome. Luckily the fallback to good ol' tcp
> saved the day.
>
> b) I had this issue a few months ago and it subsided quickly
>
> Google reports it's an issue in this version of Chrome and the next version
> will have a little smarts to automatically re initiate the connection with
> TCP automatically without having to disable quic.
>
>
I remained very disappointed in how google has gone about quic.
They are dismissive of network operators concerns (quic protocol list and
ietf), cause substantial outages, and have lost a lot of good will in the
process
Here's your post mortem:
RFO: Google unilaterally deployed a non-standard protocol to our production
environment, driving up helpdesk calls x%
After action: block udp 80/443 until production ready and standard ratified
use deployed.
And.
Get off my lawn.
On Wed, Sep 23, 2015 at 5:01 PM, Sean Hunter <jamesb2147@gmail.com> wrote:
>
> > Hi all,
> >
> > I work for a 2500 user university and we've seen some odd behavior
> > recently. 2-4 weeks ago we started seeing Google searches that would fail
> > for ~2 minutes, or disconnects in Gmail briefly. This week, and
> > particularly in the last 2-3 days, we've had reports from numerous users
> on
> > campus, even those who generally do not complain unless an issue has been
> > ongoing for a while. Those reports include Drive disconnecting, searches
> > failing, Gmail presenting a "007" error, and calendar failing to create
> > events.
> >
> > In fact, the issue became so widespread today, that the campus paper is
> > writing about it as a last minute article before they're weekly
> > publication's deadline this evening. (Important in our little world where
> > we try to look good.)
> >
> > We aren't really staffed or equipped to figure out exactly what's
> happening
> > (and issues are sporadic, so packet captures are difficult, to say the
> > least), but we found that disabling QUIC dramatically and immediately
> > improved the experience of a couple of users on campus. We're
> recommending
> > via the paper that others do so as well.
> >
> > What I'm curious about is:
> >
> > a) Has anyone here had a similar experience? Was the root cause QUIC in
> > your case?
> >
> > b) Has anyone noticed anything remotely similar in the last few
> > weeks/days/today?
> >
> > We're an Apps domain, so this may be specific to universities in the Apps
> > universe.
> >
> > If anyone has any useful information or hints, or if someone from Google
> > would like more information, please feel free to contact me, on or off
> > list.
> >
> > Thanks for reading and have a great night everyone! Happy Wednesday!
> >
>
