Hacker News new | past | comments | ask | show | jobs | submit login

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.




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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: