Wednesday, November 17, 2004

Network Outage

Looks like we've been disconnected since 8:02pm PST. Speakeasy status hotline reports, "We are experiencing a problem with the DS3 servicing QWest-partnered customers in the Seattle area."
No ETA on a fix, yet.

Update: (10:27pm PST)
"After remote troubleshooting, a technician has been dispatched to the Central Office. ETA for arrival is 1 hour."
Still no ETA for repair.

Update: (Thu. 1:55am PST)
"Outage issue has been isolated and repair has been implemented at this time." I suppose it won't be too long now, but they're still not giving an ETA.

Update: (Thu. 2:40am PST)
Heyhey, we have ping. And I see people connecting again. Yay.

Bedtime pour moi.

Friday, November 12, 2004

Made it

Things seem to have survived the trip and we are back up at the new IP.

(DNS appears to have updated, but see previous post about what to do if you're not getting the right (69....) IP for

Update:  FTP site and mail are back as well.

Road trip

Server box is now on the road. If all goes well, we'll be back up in about 30-60 minutes.

There will be a new IP address.'s old DNS entry is set to time out about 15 minutes from now, so you should just be getting it automatically. But if you still find it resolving to the 67. address and you can't convince your DNS cache to flush itself, try

Saturday, November 06, 2004

Firewall rebooted

Apparently, this time it had gotten into a state where old connections were okay, but new connection attempts were losing (and it had stopped responding to pings).

First post

Hm. That was easier than I thought it would be.

And yes, we're still up, so far as I can tell.