They confirmed that they&#x27;re working on it but it&#x27;s not clear that it was a purely a problem with Apple&#x27;s code. Given all of the well-documented general stability problems t.co has had over the years it would not surprise me to learn that Chrome has a more aggressive recovery mode from a bad DNS server, failures returned by only one of the multiple servers which that hostname resolves to, etc.<p>I&#x27;ve seen plenty of t.co errors in Firefox as well as Safari, but never in Chrome and the network stack is one of the areas where they&#x27;ve clearly put a lot of effort.