derg Apparently a "terse" writer Staff member Apr 2, 2009 #1 ...having connectivity issues? I guess f you were, you wouldn't be seeing this... Hmm..
Cessnaflyer Wooooooooooooooooooooooooooooooo Apr 2, 2009 #2 I did for a few hours but I am in Washington
SteveC "Laconic" Staff member Apr 2, 2009 #4 Not working for a while here...where am I?....oh yeah...ROA.
derg Apparently a "terse" writer Staff member Apr 2, 2009 #5 Should have been a sporadic but temporary outage when I was switching DNS's around this afternoon.
JEP Does It Really Matter....? Staff member Apr 3, 2009 #6 Doug Taylor said: Should have been a sporadic but temporary outage when I was switching DNS's around this afternoon. Click to expand... Come on Dough, you cant get us all hopped up on JC and then cut us off in the middle of the day with no warning... anic:
Doug Taylor said: Should have been a sporadic but temporary outage when I was switching DNS's around this afternoon. Click to expand... Come on Dough, you cant get us all hopped up on JC and then cut us off in the middle of the day with no warning... anic:
scramjet Well-Known Member Apr 3, 2009 #7 I couldn't access JC at all from around 7pm to 10pm last night.
matteo Well-Known Member Apr 3, 2009 #8 scramjet said: I couldn't access JC at all from around 7pm to 10pm last night. Click to expand... Same. and I'm in MD.
scramjet said: I couldn't access JC at all from around 7pm to 10pm last night. Click to expand... Same. and I'm in MD.
n57flyguy Well-Known Member Apr 3, 2009 #9 On the PA/MD border, could not get on last night. What was up?
derg Apparently a "terse" writer Staff member Apr 4, 2009 #10 Turns out some of the ISP's haven't refreshed their DNS cache, but I'll check again in JFK. It shouldn't have been more than 48 hours.
Turns out some of the ISP's haven't refreshed their DNS cache, but I'll check again in JFK. It shouldn't have been more than 48 hours.