Can you get on this site?

Danni · Jan 11, 2009, 21:39:04

I'm having trouble getting to http://alexadaikon.com

I can access it through a proxy, so I know the server is up (if a little slow, which I'd like to fix if I could get to it).

Can anyone else on IDNet access it? I'm on gw5.

Den · Jan 11, 2009, 21:43:12

No problem, opens up straight away and I am gw5 as well

Danni · Jan 11, 2009, 21:44:50

Okay, so it's more local. Thanks, Den

Philip · Jan 11, 2009, 21:45:38

works for me, I'm on dsl4

Ted · Jan 11, 2009, 21:50:39

Comes up ok but a little slow, about 15-20 secs. GW5

Danni · Jan 11, 2009, 21:58:08

And after rebooting router, and rebooting computer (it was wanting to be rebooted) still nothing for that site or any other on the server.

It's not the server, as though it's being slow it is up. Should I email IDNet?

Sebby · Jan 11, 2009, 22:17:21

It's opening very slowly here, Danni. I think it's the site, rather than IDNet.

Danni · Jan 11, 2009, 22:28:35

I know it's slow, and I'm trying to get into it so I can reboot the server. The problem is I can't access it at all. Keeps timing out, can't ping it (though I can ping from dnsstuff.com), can't ssh into it, or do anything. Since Colin is at the pub, I've got to try and fix it, and I can't if I can't get in.

Sebby · Jan 11, 2009, 22:32:11

Try OpenDNS?

Danni · Jan 11, 2009, 22:49:03

Doesn't make a difference. I'm wondering what the problem is, as slowness I can understand. Complete timeouts, not so much.

From home computer:
danni@Matilda:~$ ping alexadaikon.com -c 10
PING alexadaikon.com (64.92.171.50) 56(84) bytes of data.

--- alexadaikon.com ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

From other server:
danni@dannimatzk.co.uk [~]# ping alexadaikon.com -c 10
PING alexadaikon.com (64.92.171.50) 56(84) bytes of data.
64 bytes from server2.jndhostns.com (64.92.171.50): icmp_seq=2 ttl=54 time=14.4 ms
64 bytes from server2.jndhostns.com (64.92.171.50): icmp_seq=3 ttl=54 time=26.7 ms
64 bytes from server2.jndhostns.com (64.92.171.50): icmp_seq=4 ttl=54 time=2.14 ms
64 bytes from server2.jndhostns.com (64.92.171.50): icmp_seq=5 ttl=54 time=48.0 ms
64 bytes from server2.jndhostns.com (64.92.171.50): icmp_seq=6 ttl=54 time=2.10 ms
64 bytes from server2.jndhostns.com (64.92.171.50): icmp_seq=7 ttl=54 time=11.7 ms
64 bytes from server2.jndhostns.com (64.92.171.50): icmp_seq=8 ttl=54 time=14.9 ms
64 bytes from server2.jndhostns.com (64.92.171.50): icmp_seq=9 ttl=54 time=5.92 ms

--- alexadaikon.com ping statistics ---
10 packets transmitted, 8 received, 20% packet loss, time 9004ms
rtt min/avg/max/mdev = 2.106/15.780/48.068/14.371 ms, pipe 2

...okay, that's interesting.

Just done two traceroutes- one from home computer, one from server. Both take the same route from a certain place, but then I get blocked, but the server doesn't.

Home computer:
danni@Matilda:~$ traceroute alexadaikon.com
traceroute to alexadaikon.com (64.92.171.50), 30 hops max, 40 byte packets
1 192.168.1.254 (192.168.1.254) 5.770 ms 5.751 ms 5.829 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 88.795 ms 88.792 ms 88.791 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 35.272 ms 35.269 ms 37.250 ms
4 ldn-d4-link.telia.net (193.45.0.189) 39.492 ms 39.489 ms 39.488 ms
5 ldn-bb2-link.telia.net (80.91.251.14) 45.256 ms ldn-bb2-link.telia.net (80.91.249.133) 45.248 ms ldn-bb2-link.telia.net (80.91.250.238) 47.043 ms
6 nyk-bb2-link.telia.net (80.91.253.118) 118.497 ms nyk-bb2-link.telia.net (80.91.248.254) 100.782 ms nyk-bb1-pos0-2-0.telia.net (213.248.65.90) 100.744 ms
7 nyk-b5-link.telia.net (80.91.248.146) 106.603 ms nyk-b5-link.telia.net (80.91.248.142) 104.873 ms nyk-b5-link.telia.net (80.91.248.158) 104.801 ms
8 208.173.129.69 (208.173.129.69) 104.342 ms 106.878 ms 108.735 ms
9 cr2-tengig-0-15-4-0.NewYork.savvis.net (204.70.198.17) 110.334 ms 110.321 ms 110.419 ms
10 cr2-tengig0-7-0-0.dallas.savvis.net (204.70.196.214) 153.656 ms 153.649 ms 153.754 ms
11 hr1-tengig-12-0-0.dallasda1.savvis.net (204.70.203.58) 155.456 ms 159.444 ms 143.745 ms
12 216.39.79.98 (216.39.79.98) 147.718 ms 147.714 ms 155.902 ms
13 * * *
14 * * *
15 * * *
(and so on until hop 30)

Other server:
danni@dannimatzk.co.uk [~]# traceroute alexadaikon.com
traceroute to alexadaikon.com (64.92.171.50), 30 hops max, 38 byte packets
1 1.162.232.72.static.reverse.ltdomains.com (72.232.162.1) 0.253 ms 0.216 ms 0.212 ms
2 aw_pod22a.databank.com (63.164.96.241) 0.234 ms 0.171 ms 0.170 ms
3 ce_aw_10g.databank.com (63.164.96.65) 0.285 ms 0.347 ms 0.344 ms
4 xe-9-0-0.edge3.Dallas1.Level3.net (4.71.170.5) 0.345 ms 0.350 ms 0.336 ms
5 ae-14-69.car4.Dallas1.Level3.net (4.68.19.6) 0.932 ms ae-44-99.car4.Dallas1.Level3.net (4.68.19.198) 1.040 ms 1.047 ms
6 er1-te-3-2.dallasequinix.savvis.net (208.173.178.141) 1.081 ms 1.080 ms 0.988 ms
7 pr2-ge-3-0-0.dallasequinix.savvis.net (204.70.204.150) 0.873 ms 0.894 ms 0.771 ms
8 204.70.202.65 (204.70.202.65) 2.133 ms 1.851 ms 1.918 ms
9 216.39.79.98 (216.39.79.98) 1.741 ms 16.363 ms 2.109 ms
10 * * *
11 server2.jndhostns.com (64.92.171.50) 8.982 ms 6.142 ms 6.282 ms

I wonder if my IP has been banned for some reason?

Simon · Jan 11, 2009, 23:14:07

Quote from: Ted on Jan 11, 2009, 21:50:39
Comes up ok but a little slow, about 15-20 secs. GW5

Same here.

Ted · Jan 11, 2009, 23:24:12

Here's a traceroute from my box, don't know if it will help at all.

I notice mine had a problem with hop 13 and recovered, could it be a routing issue?

[root@localhost ted]# traceroute www.alexadaikon.com
traceroute to www.alexadaikon.com (64.92.171.50), 30 hops max, 40 byte packets
1 home (my-local-ip) 5.413 ms 5.365 ms 6.337 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 53.893 ms 56.097 ms 57.872 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 57.885 ms 57.879 ms 59.730 ms
4 ldn-d4-link.telia.net (193.45.0.189) 59.756 ms 61.661 ms 63.648 ms
5 ldn-bb1-link.telia.net (80.91.249.131) 65.498 ms ldn-bb1-link.telia.net (80.91.249.77) 67.488 ms ldn-bb1-link.telia.net (80.91.249.131) 69.383 ms
6 nyk-bb1-pos0-2-0.telia.net (213.248.65.90) 142.265 ms 129.255 ms nyk-bb2-link.telia.net (80.91.248.254) 133.370 ms
7 nyk-b5-link.telia.net (80.91.253.106) 133.329 ms nyk-b5-link.telia.net (80.91.248.158) 182.458 ms 121.532 ms
8 208.173.129.69 (208.173.129.69) 123.412 ms 123.440 ms 125.305 ms
9 cr1-tengig-0-8-3-0.NewYork.savvis.net (204.70.198.13) 129.157 ms 131.109 ms 133.112 ms
10 cr2-tengig0-0-2-0.dallas.savvis.net (204.70.196.210) 174.476 ms 176.391 ms 176.426 ms
11 hr1-tengig-12-0-0.dallasda1.savvis.net (204.70.203.58) 180.286 ms 186.954ms 192.208 ms
12 216.39.79.98 (216.39.79.98) 192.219 ms 192.212 ms 192.482 ms
13 * * *
14 server2.jndhostns.com (64.92.171.50) 218.350 ms 224.173 ms 230.000 ms

Ted · Jan 11, 2009, 23:38:31

Did a tracepath and got the same as your home comp. Hmmmm!

[root@localhost ted]# tracepath www.alexadaikon.com
1: (local-ip) 0.302ms pmtu 1500
1: home (local-ip) 2.266ms
1: home (local-ip) 1.238ms
2: telehouse-gw2-lo1.idnet.net (212.69.63.51) 71.578ms
3: telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 92.371ms
4: ldn-d4-link.telia.net (193.45.0.189) 192.536ms asymm 5
5: ldn-bb2-link.telia.net (80.91.249.133) 73.988ms asymm 6
6: nyk-bb2-link.telia.net (80.91.248.254) 147.253ms asymm 7
7: nyk-b5-link.telia.net (80.91.248.158) 154.959ms asymm 8
8: no reply
9: cr1-tengig-0-8-3-0.NewYork.savvis.net (204.70.198.13) 202.317ms asymm 10
10: cr2-tengig0-0-2-0.dallas.savvis.net (204.70.196.210) 188.426ms asymm 14
11: no reply
12: 216.39.79.98 (216.39.79.98) 190.810ms asymm 15
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500

Sebby · Jan 11, 2009, 23:41:52

The only common factor is Linux.

Ted · Jan 11, 2009, 23:43:47

Quote from: Sebby on Jan 11, 2009, 23:41:52
The only common factor is Linux.

OI!

Danni · Jan 11, 2009, 23:45:09

The other server is Linux as well

somanyholes · Jan 12, 2009, 07:38:30

QuoteI notice mine had a problem with hop 13 and recovered, could it be a routing issue?

As far as that is concerned, that router is probably just blocking icmp trace. Can't see that particular hop causing the issue as it contines to route the packet......

talos · Jan 12, 2009, 08:49:38

Loads much faster on Firefox.

Sebby · Jan 12, 2009, 13:34:04

Quote from: Ted on Jan 11, 2009, 23:43:47
OI!

Danni · Jan 12, 2009, 19:12:30

Was sorted this morning. My IP was blocked

Sebby · Jan 12, 2009, 23:48:14

Colin Burns · Jan 13, 2009, 20:59:19

why do my servers always break when im down the pub and on pint number 6.

Danni · Jan 13, 2009, 21:04:20

Erm, Murphy's law?

Colin Burns · Jan 13, 2009, 21:07:12

danni we have been though this before

Danni · Jan 13, 2009, 21:07:54

We have?

Colin Burns · Jan 13, 2009, 21:13:08

i think we have its about the not confusing me stuff

Danni · Jan 13, 2009, 21:18:22

Ohh...

Murphy's Law- if anything can go wrong, it will.

Sebby · Jan 13, 2009, 22:13:56

I thought that was BT's slogun.

Danni · Jan 14, 2009, 01:27:14

It is

Colin Burns · Jan 19, 2009, 10:45:49

yea they released the anousement last thursday but they wont be releasing the information till the 30/02/2009 for fears that it will catch on and people will out them