2 ms·
but a lot of other sites and systems weren't -- even when accessing by IP. So it wasn't really a DNS issue. That's just an intermittent issue that Comcast
by LukeShu 11y ago
but a lot of other sites and systems weren't -- even when
accessing by IP. So it wasn't really a DNS issue.
That's just an intermittent issue that Comcast customers deal with--I experienced that in Indiana a couple of months ago.
I believe that it relates to them re-jiggering routers such that the appropriate default gateway for your modem changes, but because your modem is already up, it doesn't get notified of the change. So the modem doesn't send the message to the correct router, and the router it sends it to may or may not know how to get it to the destination.
- thaumaturgy 11y agoI typically have logs streaming through terminal windows from several servers and multitask online -- I notice even brief transient network issues. FWIW what you're describing hasn't been a problem for me (though I don't doubt it is for lots of customers), and the San Jose outage was definitely out of the ordinary. Anyway, I wish Sacramento was a bigger network hub, is all.