Live data from Hacker News

Chrome/macOS users in The Netherlands cannot visit google.com or google.nl

news.ycombinator.com

51–60 of 72 posts

Re: Chrome/macOS users in The Netherlands cannot visit google.com or google.nl

#51

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…

Yup, Edge is finally more stable in 1703, but that's a week away ;)

Re: Chrome/macOS users in The Netherlands cannot visit google.com or google.nl

#52
post #51

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…

Yup, Edge is finally more stable in 1703, but that's a week away ;)

That's what they always say about IE: it'll be good next patch or version.

Re: Chrome/macOS users in The Netherlands cannot visit google.com or google.nl

#53
post #41

I've had problems with QUIC in various networks (corp, home) mainly in Singapore for more than a year. Until the point I disable QUIC as one of the first steps when I encounter GMail connectivity problems from Chrome/Chromium on a fresh machine. I find it odd that QUIC is enabled by default when it apparently has poor fallback capabilities to "non-QUIC" mode.

The internet is in a pretty sad state if a simple UDP stream isn't possible any more because of interfering middleboxes. It's not like QUIC is a new IP protocol. One of the reasons for lack of good fallback is probably an expectation that basic IP operations are functional.

Re: Chrome/macOS users in The Netherlands cannot visit google.com or google.nl

#54
post #29

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.

They wouldn't be the first ISP to break the law, and they most certainly wouldn't be the last.

Re: Chrome/macOS users in The Netherlands cannot visit google.com or google.nl

#55
post #20

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.

The title isn't misleading, it's describing exactly what the parent was experiencing, "Chrome/macOS users in The Netherlands cannot visit google.com or google.nl". There was no assignment of blame to Google or anyone else.

> Google has not broken anything, Dutch providers have.

Based on what evidence, exactly? Aside from a grand scheme of evil world domination by Dutch ISPs, what exactly would their motive be for a coordinated action like this one which seems to only hurt Google properties and only over QUIC? Aside from a court order or responding to some kind of attack, I can't find a single compelling reason for ISPs to do this (and the fact that it's illegal by law and the fines are pretty big) unless they have a desire to flood their help desks.

Re: Chrome/macOS users in The Netherlands cannot visit google.com or google.nl

#56
post #42

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…

No dedicated testing team is ever going to beat the developers dogfooding the tool daily. I wish I had access to metrics from stackoverflow et al, to see if Microsoft inhouse developers use Edge

I don't think they use Office either.

The only software where you can tell that they dogfood it is Visual Studio. Every change makes sense, is useful, user friendly and corresponds to problems I have met.

The other software that you would assume they dogfood but it doesn't show is Windows 10...

Re: Chrome/macOS users in The Netherlands cannot visit google.com or google.nl

#57
post #29

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.

In a world where every router has the capability to do things which are illegal in various countries, do you think that Netherlands ISPs always obey the law? In the US, convention center operators keep on getting busted for sending deauth packets to "rogue" WiFi access points, i.e. those brought in by conference attendees and exhibitors.

Re: Chrome/macOS users in The Netherlands cannot visit google.com or google.nl

#59

Earlier quoted context omitted.

This is probably not the case, as traffic shaping is illegal in The Netherlands.

In a world where every router has the capability to do things which are illegal in various countries, do you think that Netherlands ISPs always obey the law? In the US, convention center operators keep on getting busted for sending deauth packets to "rogue" WiFi access points, i.e. those brought in by conference attendees and exhibitors.

The Dutch internet market is not really comparable to the US market. We do not have data limits for cable/dsl/fiber and I've never had issues downloading torrents at full speed, even before the net neutrality law.
Post reply on HN