3 ms·

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 th

by tinco 10y ago

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.

deleted 10y ago
[deleted]
dtech 10y ago
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.
- deleted 10y ago
  [deleted]
vincnetas 10y ago
could you explain with more details. I'm curious what is all about.
Mojah 10y ago
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 nothing to do with this.
- tinco 10y ago
  Alright, thanks, and sorry for implicating you. I guess it's the history of ISP's messing with transport layer protocols that got me finger pointing.
daenney 10y ago
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.

by tinco 10y ago

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.

deleted 10y ago

[deleted]

dtech 10y ago

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.

deleted 10y ago
[deleted]

vincnetas 10y ago

could you explain with more details. I'm curious what is all about.

Mojah 10y ago

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 nothing to do with this.

tinco 10y ago
Alright, thanks, and sorry for implicating you. I guess it's the history of ISP's messing with transport layer protocols that got me finger pointing.

daenney 10y ago

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.