Well my bet is still on Global Crossing being at fault. It looks like everyone who CAN get to the site does not go through any Global Crossing IPs. There is nothing you can do about this. It just depends on who your ISP peers with and how routes are decided. Proxies or tor will be the only way to get to lunatics until GC notices and fixes their problem. I tried sending them an email but of course they only read email that is part of an existing helpdesk ticket so that went nowhere.

I didn't know how to copy my trace but from Seattle I did not go thru Global Crossing.

Assuming you're in Windows, right click in the command prompt window where you did the trace and click "Mark." Then use your mouse to highlight the trace. While the text is still highlighted, hit the enter key. That will put the trace into you clipboard, which you can then paste here.

---

Well my bet is still on Global Crossing being at fault. It looks like everyone who CAN get to the site does not go through any Global Crossing IPs. There is nothing you can do about this. It just depends on who your ISP peers with and how routes are decided. Proxies or tor will be the only way to get to lunatics until GC notices and fixes their problem. I tried sending them an email but of course they only read email that is part of an existing helpdesk ticket so that went nowhere.

I didn't know how to copy my trace but from Seattle I did not go thru Global Crossing.

First right click on the black area of the command prompt window, then select all and click on that selection, Next right click on the command prompts menu bar at the top of the command prompt window and scroll down to Edit and then copy and click on Copy, then do a paste operation(Press the "ctrl" key and hold that key and then press the "p" key and then release both keys at the same time) into where ever You want to leave the text at.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

that worked...

Tracing route to lunatics.kwsn.net [206.132.254.42]
over a maximum of 30 hops:

1 * * * Request timed out.
2 43 ms 42 ms 42 ms tukw-dsl-gw24-216.tukw.qwest.net [63.231.10.216]

3 42 ms 41 ms 42 ms tukw-agw1.inet.qwest.net [71.217.184.185]
4 42 ms 42 ms 41 ms sea-core-01.inet.qwest.net [67.14.1.194]
5 42 ms 42 ms 42 ms sea-brdr-01.inet.qwest.net [205.171.26.82]
6 43 ms 43 ms 43 ms bpr3-so-2-0-0.seattleswitchdesign.savvis.net [20
8.173.49.1]
7 45 ms 49 ms 51 ms cr1-pos-0-3-0-1.Seattle.savvis.net [208.172.83.6
2]
8 120 ms 120 ms 119 ms cr2-pos-0-0-0-0.Atlanta.savvis.net [204.70.192.6
9]
9 122 ms 126 ms 122 ms msr1-te-0-0-0-0.atlantapaix.savvis.net [204.70.2
00.1]
10 119 ms 119 ms 119 ms 204.70.203.98
11 121 ms 120 ms 121 ms 216.89.82.78
12 119 ms 119 ms 119 ms xconn.core2-edge1.atl.oneringnetworks.net [66.18
7.176.5]
13 121 ms 122 ms 121 ms xconn.dktc-56m.atl.oneringnetworks.net [66.187.1
78.58]
14 120 ms 120 ms 120 ms beat42.gzz.cyb.cream.spectacularrebeats.net [206
.132.254.42]

Trace complete.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

that worked...

Tracing route to lunatics.kwsn.net [206.132.254.42]
over a maximum of 30 hops:

1 * * * Request timed out.
2 43 ms 42 ms 42 ms tukw-dsl-gw24-216.tukw.qwest.net [63.231.10.216]

3 42 ms 41 ms 42 ms tukw-agw1.inet.qwest.net [71.217.184.185]
4 42 ms 42 ms 41 ms sea-core-01.inet.qwest.net [67.14.1.194]
5 42 ms 42 ms 42 ms sea-brdr-01.inet.qwest.net [205.171.26.82]
6 43 ms 43 ms 43 ms bpr3-so-2-0-0.seattleswitchdesign.savvis.net [20
8.173.49.1]
7 45 ms 49 ms 51 ms cr1-pos-0-3-0-1.Seattle.savvis.net [208.172.83.6
2]
8 120 ms 120 ms 119 ms cr2-pos-0-0-0-0.Atlanta.savvis.net [204.70.192.6
9]
9 122 ms 126 ms 122 ms msr1-te-0-0-0-0.atlantapaix.savvis.net [204.70.2
00.1]
10 119 ms 119 ms 119 ms 204.70.203.98
11 121 ms 120 ms 121 ms 216.89.82.78
12 119 ms 119 ms 119 ms xconn.core2-edge1.atl.oneringnetworks.net [66.18
7.176.5]
13 121 ms 122 ms 121 ms xconn.dktc-56m.atl.oneringnetworks.net [66.187.1
78.58]
14 120 ms 120 ms 120 ms beat42.gzz.cyb.cream.spectacularrebeats.net [206
.132.254.42]

Trace complete.

I've known how to do this simple pair of keystrokes since It was announced back in Byte Magazine back in the 90's, Copy is normally "ctrl" "c" instead of "ctrl" "p", How one does copy is exactly the same as in paste, Just a different letter is used, c instead of p.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

that worked...

Tracing route to lunatics.kwsn.net [206.132.254.42]
over a maximum of 30 hops:

1 * * * Request timed out.
2 43 ms 42 ms 42 ms tukw-dsl-gw24-216.tukw.qwest.net [63.231.10.216]

3 42 ms 41 ms 42 ms tukw-agw1.inet.qwest.net [71.217.184.185]
4 42 ms 42 ms 41 ms sea-core-01.inet.qwest.net [67.14.1.194]
5 42 ms 42 ms 42 ms sea-brdr-01.inet.qwest.net [205.171.26.82]
6 43 ms 43 ms 43 ms bpr3-so-2-0-0.seattleswitchdesign.savvis.net [20
8.173.49.1]
7 45 ms 49 ms 51 ms cr1-pos-0-3-0-1.Seattle.savvis.net [208.172.83.6
2]
8 120 ms 120 ms 119 ms cr2-pos-0-0-0-0.Atlanta.savvis.net [204.70.192.6
9]
9 122 ms 126 ms 122 ms msr1-te-0-0-0-0.atlantapaix.savvis.net [204.70.2
00.1]
10 119 ms 119 ms 119 ms 204.70.203.98
11 121 ms 120 ms 121 ms 216.89.82.78
12 119 ms 119 ms 119 ms xconn.core2-edge1.atl.oneringnetworks.net [66.18
7.176.5]
13 121 ms 122 ms 121 ms xconn.dktc-56m.atl.oneringnetworks.net [66.187.1
78.58]
14 120 ms 120 ms 120 ms beat42.gzz.cyb.cream.spectacularrebeats.net [206
.132.254.42]

Trace complete.

So you're having no trouble getting to lunatics?

---

that worked...

Tracing route to lunatics.kwsn.net [206.132.254.42]
over a maximum of 30 hops:

1 * * * Request timed out.
2 43 ms 42 ms 42 ms tukw-dsl-gw24-216.tukw.qwest.net [63.231.10.216]

3 42 ms 41 ms 42 ms tukw-agw1.inet.qwest.net [71.217.184.185]
4 42 ms 42 ms 41 ms sea-core-01.inet.qwest.net [67.14.1.194]
5 42 ms 42 ms 42 ms sea-brdr-01.inet.qwest.net [205.171.26.82]
6 43 ms 43 ms 43 ms bpr3-so-2-0-0.seattleswitchdesign.savvis.net [20
8.173.49.1]
7 45 ms 49 ms 51 ms cr1-pos-0-3-0-1.Seattle.savvis.net [208.172.83.6
2]
8 120 ms 120 ms 119 ms cr2-pos-0-0-0-0.Atlanta.savvis.net [204.70.192.6
9]
9 122 ms 126 ms 122 ms msr1-te-0-0-0-0.atlantapaix.savvis.net [204.70.2
00.1]
10 119 ms 119 ms 119 ms 204.70.203.98
11 121 ms 120 ms 121 ms 216.89.82.78
12 119 ms 119 ms 119 ms xconn.core2-edge1.atl.oneringnetworks.net [66.18
7.176.5]
13 121 ms 122 ms 121 ms xconn.dktc-56m.atl.oneringnetworks.net [66.187.1
78.58]
14 120 ms 120 ms 120 ms beat42.gzz.cyb.cream.spectacularrebeats.net [206
.132.254.42]

Trace complete.

So you're having no trouble getting to lunatics?

None at all, have been all around the site to see.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I'm having trouble getting to the site too.

Ever since May 1st, I havent been able to connect.

Being part of the prerelease testing community, this is annoying to say the least, would like to take part in the testing of SSE2 and so on.

Tracert:

Sporer rute til lunatics.kwsn.net [206.132.254.42]
over et maksimum af 30 hop:

1 1 ms <1 ms <1 ms 172.26.1.1
2 18 ms * * loop0.mxc1-kolx.ip.cybercity.dk [212.242.2.164]
3 19 ms 20 ms 19 ms ge-0-1-6-10.mcr1-arhx.ip.cybercity.dk [212.242.8.53]
4 21 ms 21 ms 47 ms ge-0-0-0.mcr1-aalx.ip.cybercity.dk [212.242.6.13]
5 26 ms 52 ms 26 ms ge-1-0-0.mcr1-soex.ip.cybercity.dk [212.242.6.17]
6 26 ms 26 ms 26 ms ge-0-0-0.br1-soex.ip.cybercity.dk [212.242.6.30]
7 205 ms 220 ms 207 ms te1-3.ar3.CPH1.gblx.net [64.215.27.125]
8 121 ms 121 ms 124 ms 64.209.102.222
9 * * * Anmodning fik timeout.

Looks like it dies at 64.209.102.222, as someone else have pointed out.

---

@Any who want to reach Lunatics but cannot:
You should be able to bypass your ISP by using an anonymous proxy server. Simply create and use a shortcut/favorite using the
following URL:

https://proxify.com/u?lunatics.kwsn.net/index.php

This is a free web-based proxy service. There are many other servers you could use but this one works for me albeit s.l.o.w.l.y and with advertisements added for flavor. But it does work.

Much more info on proxies can be found at http://proxy.org

[EDIT] OOPS, well it does work for reading the site but I now find that I cannot login unless I buy the service. Darn, back to square one. [/EDIT]

[EDIT2] DO NOT use the link I provided earlier. I now find that I cannot ping ANY server, even microsoft.com, even after booting. I'm still investigating. FREE means you get what you pay for.[EDIT]

[FINAL UPDATE] This may be a Verizon thing. Other computers on my lan cannot ping any outside server either although they can ping each other. Using the proxy does work for reaching Lunatics for reading only unless you want to pay $40 for a 6 month subscription in which case you should be able to logon too. No thanks. It works but use with caution.

OK.

Using freeproxyserver.net, I have been able to get to lunatics, and even log in.

It runs fairly quick, so this solution will have to do for now.

---

. .. had a 'single' problem yesterday geting there - but no problems lately

> using TW/RR - used trace (idserve) earlier:

Apache/1.3.34 Ben-SSL/1.57(Unix) PHP/4.4.3 - lunatics.kwsn.net - 206.132.254.42

---

BOINC Wiki . . .

Science Status Page . . .

OK.

Using freeproxyserver.net, I have been able to get to lunatics, and even log in.

It runs fairly quick, so this solution will have to do for now.

Thanks Karsten,
Right now the CGI Proxy says "Down For Maintenance" but I'll keep trying it.

OK.

Using freeproxyserver.net, I have been able to get to lunatics, and even log in.

It runs fairly quick, so this solution will have to do for now.

Thanks Karsten,
Right now the CGI Proxy says "Down For Maintenance" but I'll keep trying it.

Tracing route to lunatics.kwsn.net [206.132.254.42] , snip

Just visited their website, everything is OK, downloaded an app. OK

TRACE from Holland:

Lunatics

---

OK.

Using freeproxyserver.net, I have been able to get to lunatics, and even log in.

It runs fairly quick, so this solution will have to do for now.

Thanks Karsten,
Right now the CGI Proxy says "Down For Maintenance" but I'll keep trying it.

Just visited their website, everything is OK, downloaded an app. OK

Did you use freeproxyserver.net to do so, or is your normal connection working?

Yea, freeproxyserver.net works, I'm just annoyed that I need to use it to get to a site that I had no problem getting to before. I can connect through two different backbones and neither are connecting (Level 3 and Paetec). Both with the last hop returned on the traceroute of 64.209.102.222 yet getting there through two completely different routes.

For those who can get through, this hop isn't on their traceroute.

This just ticks me off.

---

"Life is just nature's way of keeping meat fresh." - The Doctor

Yea, freeproxyserver.net works, I'm just annoyed that I need to use it to get to a site that I had no problem getting to before. I can connect through two different backbones and neither are connecting (Level 3 and Paetec). Both with the last hop returned on the traceroute of 64.209.102.222 yet getting there through two completely different routes.

For those who can get through, this hop isn't on their traceroute.

This just ticks me off.

Last hop for me is 64.209.102.222 also...thats where my traceroute stops :/

lunatics.kwsn.net is unreachable for me.

---

Yea, freeproxyserver.net works, I'm just annoyed that I need to use it to get to a site that I had no problem getting to before. I can connect through two different backbones and neither are connecting (Level 3 and Paetec). Both with the last hop returned on the traceroute of 64.209.102.222 yet getting there through two completely different routes.

For those who can get through, this hop isn't on their traceroute.

This just ticks me off.

Last hop for me is 64.209.102.222 also...thats where my traceroute stops :/

lunatics.kwsn.net is unreachable for me.

Hi!

both http://lunatics.kwsn.net and http://kwsn.net/
resolve to same IP here.
I got nothing with
http://beat42.gzz.cyb.cream.spectacularrebeats.net/

http://206.132.254.42/ gives me kwsn.net.

There is no link from kwsn.net to lunatics.kwsn.net: there might be
some fun behind 206.132.254.42?

Anyhow, try plain kwsn.net. If you get it, then, maybe, kwsn.net admins
can fix it?

BR
Iztok

traceroute from Ljubljana:

traceroute lunatics.kwsn.net
traceroute to lunatics.kwsn.net (206.132.254.42), 30 hops max, 38 byte packets

3 10ge-1-4.ar2.lju.ip.triera.net (213.161.1.125) 6.037 ms 5.230 ms 5.902 ms
4 10ge-e1-4.mar.ip.triera.net (213.161.2.189) 9.639 ms 7.737 ms 7.747 ms
5 10ge-e1-1.vie.ip.triera.net (213.161.2.218) 11.360 ms 15.519 ms 11.662 ms
6 win-b2-link.telia.net (213.248.102.197) 11.886 ms 11.711 ms 13.672 ms
7 ffm-bb1-link.telia.net (80.91.252.78) 23.210 ms 23.549 ms 23.877 ms
8 prs-bb1-link.telia.net (80.91.248.69) 33.771 ms prs-bb1-link.telia.net (80.91.254.205) 35.287 ms prs-bb1-pos7-0-0.telia.net (213.248.64.110) 33.504 ms
9 ash-bb1-link.telia.net (80.91.251.98) 115.904 ms ash-bb1-link.telia.net (80.91.252.36) 115.546 ms ash-bb1-link.telia.net (80.91.251.98) 114.837 ms
10 atl-bb1-link.telia.net (80.91.252.122) 129.239 ms atl-bb1-link.telia.net (213.248.80.142) 138.210 ms atl-bb1-link.telia.net (80.91.252.122) 128.398 ms
11 wbs-116420-atl-bb1.c.telia.net (213.248.90.106) 127.176 ms 129.947 ms 126.725 ms
12 xconn.core2-edge1.atl.oneringnetworks.net (66.187.176.5) 127.279 ms 128.738 ms 125.497 ms
13 xconn.dktc-56m.atl.oneringnetworks.net (66.187.178.58) 128.820 ms 132.603 ms 134.069 ms
14 beat42.gzz.cyb.cream.spectacularrebeats.net (206.132.254.42) 132.087 ms 128.588 ms 127.360 ms


traceroute kwsn.net
traceroute to kwsn.net (206.132.254.42), 30 hops max, 38 byte packets

3 10ge-1-4.ar2.lju.ip.triera.net (213.161.1.125) 9.403 ms 5.340 ms 6.063 ms
4 10ge-e1-4.mar.ip.triera.net (213.161.2.189) 8.807 ms 6.338 ms 7.727 ms
5 10ge-e1-1.vie.ip.triera.net (213.161.2.218) 11.484 ms 11.539 ms 11.635 ms
6 win-b2-link.telia.net (213.248.102.197) 13.606 ms 11.807 ms 10.074 ms
7 ffm-bb1-link.telia.net (80.91.252.78) 24.555 ms 23.781 ms 24.114 ms
8 prs-bb1-link.telia.net (80.91.249.45) 33.463 ms prs-bb1-pos7-0-0.telia.net (213.248.64.110) 33.454 ms prs-bb1-link.telia.net (80.91.254.205) 33.185 ms
9 ash-bb1-link.telia.net (80.91.252.36) 115.046 ms 117.222 ms 115.956 ms
10 atl-bb1-link.telia.net (80.91.251.86) 135.564 ms atl-bb1-link.telia.net (80.91.248.137) 154.410 ms atl-bb1-link.telia.net (213.248.80.142) 129.405 ms
11 wbs-116420-atl-bb1.c.telia.net (213.248.90.106) 125.985 ms 125.610 ms 126.036 ms
12 xconn.core2-edge1.atl.oneringnetworks.net (66.187.176.5) 126.553 ms 126.117 ms 126.397 ms
13 xconn.dktc-56m.atl.oneringnetworks.net (66.187.178.58) 127.704 ms 183.305 ms 128.200 ms
14 beat42.gzz.cyb.cream.spectacularrebeats.net (206.132.254.42) 127.036 ms 126.563 ms 125.889 ms

Hi!

both http://lunatics.kwsn.net and http://kwsn.net/
resolve to same IP here.
I got nothing with
http://beat42.gzz.cyb.cream.spectacularrebeats.net/

spectacularrebeats.com doesn't have anything to do with the server. It just happens to be the reverse dns record that was associated with the IP when we got it.

http://206.132.254.42/ gives me kwsn.net.

There is no link from kwsn.net to lunatics.kwsn.net: there might be
some fun behind 206.132.254.42?

Anyhow, try plain kwsn.net. If you get it, then, maybe, kwsn.net admins
can fix it?

kwsn.net is just the default vhost on the server, so that's what you'll get if you access it by IP address. There's nothing particularly fun going on, unless you find DNS, Apache, PHP, and MySQL fun. As for the lack of a link to lunatics, I'm sorry to say that the kwsn.net website hasn't been updated in a very long time.

However, if anyone is able to get to www.kwsn.net or www.kwsnforum.com and NOT able to get to lunatics.kwsn.net, that would be very interesting information. I don't think that should be the case given that they're all on the same IP, but if you match that description, please post traces.

Toby emailed the guy that's providing our hosting, and he thinks it's probably a peering dispute between Cogent and Global Crossing. He's going to check with his contacts at Oneringnetworks to see if they know anything.

---

Hi!

both http://lunatics.kwsn.net and http://kwsn.net/
resolve to same IP here.
I got nothing with
http://beat42.gzz.cyb.cream.spectacularrebeats.net/

spectacularrebeats.com doesn't have anything to do with the server. It just happens to be the reverse dns record that was associated with the IP when we got it.

http://206.132.254.42/ gives me kwsn.net.

There is no link from kwsn.net to lunatics.kwsn.net: there might be
some fun behind 206.132.254.42?

Anyhow, try plain kwsn.net. If you get it, then, maybe, kwsn.net admins
can fix it?

kwsn.net is just the default vhost on the server, so that's what you'll get if you access it by IP address. There's nothing particularly fun going on, unless you find DNS, Apache, PHP, and MySQL fun. As for the lack of a link to lunatics, I'm sorry to say that the kwsn.net website hasn't been updated in a very long time.

However, if anyone is able to get to www.kwsn.net or www.kwsnforum.com and NOT able to get to lunatics.kwsn.net, that would be very interesting information. I don't think that should be the case given that they're all on the same IP, but if you match that description, please post traces.

Toby emailed the guy that's providing our hosting, and he thinks it's probably a peering dispute between Cogent and Global Crossing. He's going to check with his contacts at Oneringnetworks to see if they know anything.

I get stopped at a Global Crossing IP every time (64.209.102.222). Using freeproxyserver.net I can get there.

---

Clk2HlpSetiCty:::PayIt4ward

Hi!

both http://lunatics.kwsn.net and http://kwsn.net/
resolve to same IP here.
I got nothing with
http://beat42.gzz.cyb.cream.spectacularrebeats.net/

spectacularrebeats.com doesn't have anything to do with the server. It just happens to be the reverse dns record that was associated with the IP when we got it.

http://206.132.254.42/ gives me kwsn.net.

There is no link from kwsn.net to lunatics.kwsn.net: there might be
some fun behind 206.132.254.42?

Anyhow, try plain kwsn.net. If you get it, then, maybe, kwsn.net admins
can fix it?

kwsn.net is just the default vhost on the server, so that's what you'll get if you access it by IP address. There's nothing particularly fun going on, unless you find DNS, Apache, PHP, and MySQL fun. As for the lack of a link to lunatics, I'm sorry to say that the kwsn.net website hasn't been updated in a very long time.

However, if anyone is able to get to www.kwsn.net or www.kwsnforum.com and NOT able to get to lunatics.kwsn.net, that would be very interesting information. I don't think that should be the case given that they're all on the same IP, but if you match that description, please post traces.

Toby emailed the guy that's providing our hosting, and he thinks it's probably a peering dispute between Cogent and Global Crossing. He's going to check with his contacts at Oneringnetworks to see if they know anything.

I get stopped at a Global Crossing IP every time (64.209.102.222). Using freeproxyserver.net I can get there.

I don't use any proxy server, and I can get to lunatics without a problem...

---

Mark

Can't hit lunatics from rochester.rr.com or frontiernet.net

---