- Impact
- 311
From Twitter reports, it appears the entirety of the .co tld was down from about 1215 PST to 1315PST. In particular, Google and Twitter's g.co and t.co domains did not resolve during the period. I started diagnosing the problem on my own domains at 1310 and things starting reappearing before I made any progress.
Hacker News thread (https://news.ycombinator.com/item?id=8940980):
"It appears to be a DNS problem, with no A records being reported when running a simple 'dig t.co'. I personally can't load any .co domains. Someone suggested it may be an AWS -> .co issue: https://twitter.com/maccaw/status/559077778507571201"
Hacker News thread (https://news.ycombinator.com/item?id=8940980):
"It appears to be a DNS problem, with no A records being reported when running a simple 'dig t.co'. I personally can't load any .co domains. Someone suggested it may be an AWS -> .co issue: https://twitter.com/maccaw/status/559077778507571201"






