41–50 of 72 posts
I find it odd that QUIC is enabled by default when it apparently has poor fallback capabilities to "non-QUIC" mode.
same here in Germany on windows this morning.. also had to disable QUIC. Funnily I switched to Microsoft Edge for a short while, but have once again realized why its unusable. After about 1-2 minutes using it, the entire browser became unresponsive for about 60 seconds. Afterwards I couldnt press sign-in on YouTube because an invisible IFrame from the OneNote Web Clipper Extension was overlaying it. Nobody seems to b…
Direct fiber connection to Level 3 (Columbus, Ohio) here at work. Had to disable QUIC as I am getting the same errors as well when trying to access Google. Using local DNS, not sure what upstream DNS we are using though.
Is this the reason googleapis is having trouble? Maps and fonts are really slow for me today.
Earlier quoted context omitted.
So.. Dutch ISPs - or someone else along the route - interfering with UDP traffic?
I suspect they are throttling UDP traffic on "non-web" ports, traffic might look like torrent encrypted stream :). Anyway you can test whats going on with https://github.com/lucas-clemente/quic-go
The title is misleading, Google has not broken anything, Dutch providers have. I hope Google will do nothing, and the providers will be pressured into fixing their shitty hardware.
I work a Belgian hosting provider, directly uplinked to our datacenter via Cogent/TINET. The same happened here. There's no hardware cause, it appears to be a minor chrome update combined with a QUIC server-side update (unconfirmed) that caused issues. As soon as Chrome auto-updates to the next minor release, things appear better (but not fully fixed). It's entirely in the browser Google server-side, ISPs have nothin…
The title is misleading, Google has not broken anything, Dutch providers have. I hope Google will do nothing, and the providers will be pressured into fixing their shitty hardware.
Can you provide a source? If this is the case that's quite a serious fault, but it seems unlikely that multiple independent providers would simultaneously do this.
I'm going to hijack this thread to describe something weird that's happened to me yesterday w/ Google: just connected on my usual BT (UK) wifi, and when I opened google.com, Safari complained about an invalid SSL certificate: it was self-signed, with expiration in 2111. After a dozen refreshes, everything started to work, with the correct certificate. Anybody seen anything like that? Is it possible that a corrupted p…
I'm going to hijack this thread to describe something weird that's happened to me yesterday w/ Google: just connected on my usual BT (UK) wifi, and when I opened google.com, Safari complained about an invalid SSL certificate: it was self-signed, with expiration in 2111. After a dozen refreshes, everything started to work, with the correct certificate. Anybody seen anything like that? Is it possible that a corrupted p…
You should post the certificate details here. Issuer, fingerprint, etc.
Earlier quoted context omitted.
I suspect they are throttling UDP traffic on "non-web" ports, traffic might look like torrent encrypted stream :). Anyway you can test whats going on with https://github.com/lucas-clemente/quic-go
This is probably not the case, as traffic shaping is illegal in The Netherlands.