IssueRaiser

The trouble description seems a bit off.

The trouble description seems a bit off. They had a backbone switch in San Jose fail (according to mtr), but it only affected DNS depending on your routing. In my case, 8.8.8.8 and 8.8.4.4 were both on the working side of the switch, but a lot of other sites and systems weren't -- even when accessing by IP. So it wasn't really a DNS issue. I couldn't ping Hurricane Electric servers, but Slashdot worked OK for example. The frustrating thing was that I was going through a Sacramento hop first but still couldn't reach systems in Reno -- I thought there was fiber all the way up the 80 corridor, but apparently most of my Comcast traffic has to go to San Jose before it can proceed East.

Posted by thaumaturgy on Jun 6, 2015, 4:25 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.6,000 issues0 comments

reliability (Network)

The trouble description seems a bit off.

thaumaturgyJun 6, 2015, 4:25 AM

The trouble description seems a bit off. They had a backbone switch in San Jose fail (according to mtr), but it only affected DNS depending on your routing. In my case, 8.8.8.8 and 8.8.4.4 were both on the working side of the switch, but a lot of other sites and systems weren't -- even when accessing by IP. So it wasn't really a DNS issue. I couldn't ping Hurricane Electric servers, but Slashdot worked OK for example. The frustrating thing was that I was going through a Sacramento hop first but still couldn't reach systems in Reno -- I thought there was fiber all the way up the 80 corridor, but apparently most of my Comcast traffic has to go to San Jose before it can proceed East.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue