Cadetstuff down?

[pixelwonk]

Its back up!

For now. 

...and there was much rejoicing.      Yaaay.

They must've eaten Sir Robin's Minstrels

[PWK-GT]

They must've eaten Sir Robin's Minstrels

Brave, brave, Sir Robin............

[Pylon]

Uh-oh.  Is it down again?   It's not responding for me.   

[pixelwonk]

Uh-oh.  Is it down again?   It's not responding for me.   

Apparently Sir Robin's minstrels caused quite a gastrointestinal upset.  Perhaps if we give the'Stuff the little purple pill it will come back.

Or maybe a shrubbery...

[shorning]

Just think of the down time as CadetStuff's way of helping you fight your CadetStuff addiction. 

This community service annoucement has been brought to you by the number 3 and the letter Q.

[footballrun21]

I can get on it.  Don't know why me and not others.

[pixelwonk]

Just think of the down time as CadetStuff's way of helping you fight your CadetStuff addiction. 

Or forcing me to finish my school papers on the Truman Doctrine and the Marshall Plan. 
what fun!

[shorning]

Just think of the down time as CadetStuff's way of helping you fight your CadetStuff addiction. 

Or forcing me to finish my school papers on the Truman Doctrine and the Marshall Plan. 
what fun!

I'll take "sharp-stick-in-the-eye" for $100, Alex.

[pixelwonk]

I'll take "sharp-stick-in-the-eye" for $100, Alex.

That would be an oh-far-too-pleasant of a diversion right about now.

[NIN]

Today's outage seemed to be DNS related, but the outage on Saturday was related to the routes to our host being hosed up someplace in Chicago and totally out of our control. Today's hiccup could have been related.  I wasn't in a place to be able to tell much.

I was at home Saturday &  could not tracert to the site, but from a Level3 diagnostic tool, from DC I could see it and my home. Same with NY, Boston, etc. But try to route thru Chicago, as it appeared my packets were trying to, and forget it!   They fell off the grid on a Sprintlink hop someplace, never to be seen again.

I thought TCP/IP was supposed to be "catatstrophic loss of node" tolerant?  Guess not!

[PWK-GT]

But try to route thru Chicago, as it appeared my packets were trying to, and forget it!   

And I thought only TRAFFIC didn't move around this town.......GEEZ >gridlock<

[pixelwonk]

Today's outage seemed to be DNS related, but the outage on Saturday was related to the routes to our host being hosed up someplace in Chicago and totally out of our control. Today's hiccup could have been related.  I wasn't in a place to be able to tell much.

I was at home Saturday &  could not tracert to the site, but from a Level3 diagnostic tool, from DC I could see it and my home. Same with NY, Boston, etc. But try to route thru Chicago, as it appeared my packets were trying to, and forget it!   They fell off the grid on a Sprintlink hop someplace, never to be seen again.

I thought TCP/IP was supposed to be "catatstrophic loss of node" tolerant?  Guess not!

And for those without the pi-shaped "geek chromosome"... the layman's explanation:

DNS: Domain Name system (... or service, server)-
It's like a Star Wars Protocol Droid, that among speaking Bocce, also translates website URLS into numbers the computer world can understand, and vice versa.


Continuing on with the geeky and poor Star Wars analogy, DNS'3PO' takes the website URL we give him and translates it into blippity-beepity numbers his R2 unit friend can understand.

And with a curt insult and a smack to the rusty innards of the R2 unit, the little droid displays a fine looking website in his holographic projector.

such as this one...

Now, say the DNS'3PO' droid comes across an angry bunch of ugnaughts who wish to disassemble him and send him down the conveyor for scrap...
well, you have what happened to CadetStuff recently.   


Ok, well that was still nerdy, wasn't it?

[SarDragon]

Tedd, you owe me a keyboard.