I can't see / access my site

PHEW!

@esmi

I believe that I missed something because I don’t see any timeout on my traceroute.

Since both trace routes failed once

Could you please elaborate your statement?

Thank you.

Okay, I gotta run soon, can’t wait for esmi

@vikkineal

run this from the terminal

ping 82.165.22.127

Let me know.

it’s doing the following (and still carrying on)

PING 82.165.22.127 (82.165.22.127): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17

Thanks.

Considering the previous traceroute and this test,
99% is that your IP range got fire-walled by your host.

My ping reads:

64 bytes from 82.165.22.127: icmp_req=1 ttl=54 time=118 ms
64 bytes from 82.165.22.127: icmp_req=2 ttl=54 time=115 ms
64 bytes from 82.165.22.127: icmp_req=3 ttl=54 time=115 ms
64 bytes from 82.165.22.127: icmp_req=4 ttl=54 time=115 ms
64 bytes from 82.165.22.127: icmp_req=5 ttl=54 time=116 ms
64 bytes from 82.165.22.127: icmp_req=6 ttl=54 time=115 ms
64 bytes from 82.165.22.127: icmp_req=7 ttl=54 time=116 ms
64 bytes from 82.165.22.127: icmp_req=8 ttl=54 time=116 ms
64 bytes from 82.165.22.127: icmp_req=9 ttl=54 time=116 ms

and in the end

--- 82.165.22.127 ping statistics ---
26 packets transmitted, 26 received, 0% packet loss, time 25035ms

ipconfig /flushdns

chk site out will need to repeat this until they get the issue resolved.

I’m just going to send them a link to this thread! Thanks ??

Still no reply from 1&1.

I’ve sent them two tracert logs, one when I can get to the site and one when I can’t. The last few are identical to yours and stops at the same server.

traceroute uses UDP by default and TCP if you ask for it.

Try to run

traceroute -T www.warringtonstophs2.co.uk

as root.

When I run it with -T, I get another hop in the end

`customerhosting.co.uk (82.165.22.127)

Let us know.

tracert?

You are on Windows, traceroute won’t work for you.
Windows tracert doesn’t allow you to use TCP,

Could you please elaborate your statement?

Sorry – I got called away. I assumed from one of your earlier posts that your trace route was the same as vikkineal’s – hence my response.

We have seen a marked increase in these kinds of issues in the support forums over the past 2 days or so. We do know that some hosts like Netfirms and iPage have been hit with major attacks that have impaired their network connectivity. I’ve also seen a significant number of posts where access via a specific IP seems to have been blocked by the hosting company. Whether this is all connected and whether it has a bearing on your problems, I couldn’t say for sure. However, I wouldn’t be surprised if a lot of hosts aren’t struggling with attack issues atm.

@esmi – would you recommend moving away from 1&1 then?

Thanks, esmi.

I got it, no prob.

would you recommend moving away from 1&1 then?

From a purely personal pov, they’re not my favourite hosts. I think their support can be a bit lacking at times but that could just be the luck of the draw. But I would certainly hope that the current issues are purely temporary and may be resolved in a couple of days.

If you do want to look for another host, there are some hosts listed here. What I can say about Dreamhost is that one of their support people is on here almost every day.

Ok thanks for the info. I’ll see what 1&1 have to say for themselves and then take it from there. Hopefully.