DNS propogation. What a fun topic.
When you type in the name of a website, your computer asks your internet provider (ISP) what the real address is for the website you've requested. If you type
www.google.com, your ISP comes back with 209.85.173.103. This is called a DNS lookup.
Now there are 11 master DNS servers around the world which contain the latest information. But they would be overloaded and crash if when every person on the Internet typed in an address, they were consulted. So how it works is, ach website (like google.com, serenescreen.com, or fish-byte.com) has an expiration date attached to its DNS record. This expiration date is called Time To Live (TTL) and is typically 72 hours.
So for 71 hours and 59 minutes, when I type
www.google.com into my web browser, my ISP assumes that its information is correct. Once every 72 hours, it will ask one of those 11 master DNS servers if anything has changed.
Now what gets interesting is that that 72 hour timer starts at different times for different people. Whenever the first person looks up fish-byte.com on your ISP, that's when the timer is set in motion. So my ISP might've done its last check 1 hour ago, so I have 71 hours to wait until I see a change. Your ISP might have done this check 68 hours ago, so for you you only have 4 hours to go until you see the new page.
Clear as mud?
Good!
P.S. Most domain name registrars (the people who sell you the .com, .net, etc. address) allow you to change the TTL for your domain name. If I know in advance that I will be pulling the plug and moving my website to a new place (with the same name), I will lower the TTL to, say, 4 hours, so that everyone is checking back much more frequently. Once I have settled down at the new location, I dial it back up to 72 hours.
P.P.S. If you really need a fish-byte.com fix, you can visit it at
http://74.52.90.230/.