It sounds like a routing problem to me. If it happens again try this:
Open a Command Prompt window (Start > Programs > Accessories > Command Prompt) and enter the following command:
tracert
www.wildaboutbritain.co.uk
The output will show something like this:
Quote:
Tracing route to wildaboutbritain.co.uk [207.210.86.107] over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 19 ms 18 ms 19 ms ge-1-0-0.cr1.gs1.systems.pipex.net [62.241.161.94]
4 19 ms 20 ms 19 ms ge1-0.mr02.ldn01.pccwbtn.net [217.79.160.127]
5 117 ms 117 ms 212 ms gnax.ge2-3.br01.atl01.pccwbtn.net [63.216.31.158]
6 117 ms 117 ms 118 ms 209.51.149.109
7 117 ms 131 ms 117 ms 209.51.137.98
8 118 ms 118 ms 117 ms 207.210.80.130
9 117 ms 118 ms 117 ms 207.210.86.107
Trace complete.
|
The first line shows the IP address returned by the DNS and is followed by a list of the "hops" along the route. The first two hops above are my router and can be ignored. If there is a routing problem then you'll see Request Timed Out repeating at the end of the list.
If this happens then make a note of the tracert output and post it here once the site is back up again as it will reveal exactly where the problem lies.
Each machine on the internet is only connected to a limited number of machines, a bit like a spiders web. Each junction (hop) can send data in a couple of different directions and will choose the one that is in the generally right direction.
If one of the junctions is broken or missing the route cannot be completed and the data needs routing around it but this doesn't happen automatically and sometimes can't happen at all - the internet isn't generally as well connected as a spider's web!