CathInfo (and the rest of my server) got unexpectedly moved to a NEW IP ADDRESS: 216.45.85.184

So we're looking at a propagation delay of 8-24 hours before your "neck of the woods" gets the new IP address.

You can add to your HOSTS file to get at CathInfo.com RIGHT NOW:
216.45.85.184 www.cathinfo.com

If you type "ping www.cathinfo.com" and it tries to contact 68.235.165.156 then you need to reboot your PC, reboot your router, or wait another few hours for the update to reach your part of the country.

An unsuccessful ping will look like this:

PING cathinfo.com (68.235.165.156) 56(84) bytes of data.


I apologize for the inconvenience. We got a new router, and I didn't know that my ISP was going to rip away our static IP!

An unsuccessful ping will look like this:

PING cathinfo.com (68.235.165.156) 56(84) bytes of data.

Actually, there's nothing about what you excerpted that demonstrates that the ping was unsuccessful in fact; that your excerpt shows the old IPA merely provides the reasonable expectation of failure, and would've typically been successful until late yesterday.

A ping that's unsuccessful in fact looks like this [†], which is what I've seen this morning:

    C:\>ping www.cathinfo.com
    Pinging cathinfo.com [216.45.85.184] with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Ping statistics for 216.45.85.184:
      Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    C:\>

-------
Note †: The presentation seen by other readers on their own computers will vary.  What I show above is per the command window of a widespread version of MS Windows.