nsanedown.com wont open

[downloadersss]

not working here too

[shought]

Our host is working on getting the problem fixed, but as I mentioned before this is a difficult problem.

Are there any other sites with which you are experiencing problems (similar to the problems you're experiencing on our site)?

[kitkatforme013]

Not connected to the Japan Earthquake, just asked ISP Provider about it.

[ck_kent]

Our host is working on getting the problem fixed, but as I mentioned before this is a difficult problem.

Are there any other sites with which you are experiencing problems (similar to the problems you're experiencing on our site)?

I was wondering that same thing too, about other sites affected like nsanedown.com. But on my end all the sites that I frequent to are fine.

[downloadersss]

worked here

[downloadersss]

again worked one day and not working again :badmood:

[downloadersss]

worked today :dance2:

if it does not work tomorrow then :frusty:

[DKT27]

worked today :dance2:

if it does not work tomorrow then :frusty:

Well, I guess restarting your router whenever you cannot connect would probably be the temporary fix for now. Restarting the router will give you a new IP address, and will allow you to connect.

PS. I'm not aware in depth about it, just guessing from all the comments.

[downloadersss]

not working today :chair:

[Lite]

There is one hub that seems to be experiencing massive packet loss - sometimes you are unlucky and seem to attempt to transit via this hub. The issue has been reported, we are just waiting for it to be fixed.

[downloadersss]

thanks

[shought]

Could some of you (who are currently experiencing connection issues to nsanedown.com) run some tracerts to google.com and coral.lt as well?

[kitkatforme013]

NSANEDOWN TRACERT:

Tracing route to nsanedown.com [77.79.7.88]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1

2 226 ms 331 ms 186 ms 112.201.128.1.pldt.net [112.201.128.1]

3 * 247 ms 227 ms 119.93.254.181

4 230 ms 225 ms 298 ms 210.213.132.10.static.pldt.net [210.213.132.10]

5 256 ms * 190 ms 210.213.128.82.static.pldt.net [210.213.128.82]

6 317 ms 171 ms 264 ms 210.213.129.45.static.pldt.net [210.213.129.45]

7 143 ms * 333 ms 210.213.128.49.static.pldt.net [210.213.128.49]

8 134 ms 187 ms 178 ms 210.213.131.93.static.pldt.net [210.213.131.93]

9 * 476 ms 367 ms 210.213.128.105.static.pldt.net [210.213.128.105]

10 493 ms * 386 ms ix-0-1-1-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.53]

11 561 ms * 747 ms if-8-1508.tcore2.AEQ-Ashburn.as6453.net [64.86.252.74]

12 * 686 ms 739 ms if-10-2.tcore1.FR0-Frankfurt.as6453.net [195.219.50.97]

13 * * * Request timed out.

14 791 ms 746 ms 896 ms if-3-0-0.core1.STK-Stockholm.as6453.net [195.219.36.2]

15 560 ms 631 ms * ix-6-0.core1.STK-Stockholm.as6453.net [195.219.131.42]

16 529 ms * 551 ms 87.110.223.238

17 739 ms * 549 ms 195.13.173.45

18 646 ms 655 ms 610 ms 88.216.87.35

19 589 ms 590 ms 898 ms 84.32.142.180

20 577 ms 608 ms 500 ms sl-104.splius.lt [62.80.224.104]

21 594 ms * 691 ms vade.aleja.lt [77.79.7.254]

22 606 ms * 575 ms server.nsanedown.com [77.79.7.88]

Trace complete.

GOOGLE TRACERT

Tracing route to google.com [74.125.235.18]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 204 ms 124 ms 117 ms 112.201.128.1.pldt.net [112.201.128.1]

3 189 ms 223 ms 205 ms 119.93.254.177

4 174 ms 332 ms 124 ms 210.213.133.34.static.pldt.net [210.213.133.34]

5 222 ms 387 ms 225 ms 210.213.133.5.static.pldt.net [210.213.133.5]

6 220 ms 343 ms 224 ms 210.14.2.146

7 224 ms 222 ms 252 ms 209.85.254.166

8 243 ms 221 ms 169 ms 72.14.233.107

9 * 130 ms 172 ms 74.125.235.18

Trace complete.

coral.it TRACERT

Tracing route to coral.it [80.68.200.108]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 251 ms * 279 ms 112.201.128.1.pldt.net [112.201.128.1]

3 426 ms 289 ms 240 ms 119.93.254.181

4 445 ms 371 ms * 210.213.132.6.static.pldt.net [210.213.132.6]

5 221 ms 202 ms 206 ms 210.213.128.74.static.pldt.net [210.213.128.74]

6 411 ms 289 ms * 210.213.129.29.static.pldt.net [210.213.129.29]

7 222 ms 189 ms 200 ms 210.213.128.25.static.pldt.net [210.213.128.25]

8 178 ms * 314 ms 210.213.130.137.static.pldt.net [210.213.130.137]

9 356 ms 653 ms * 210.213.128.5.static.pldt.net [210.213.128.5]

10 593 ms 575 ms * xe-0-6-0-0.r04.lsanca03.us.bb.gin.ntt.net [204.1.254.81]

11 343 ms 311 ms 411 ms ae-6.r21.lsanca03.us.bb.gin.ntt.net [129.250.5.69]

12 530 ms 634 ms 861 ms ae-2.r20.asbnva02.us.bb.gin.ntt.net [129.250.3.54]

13 683 ms 423 ms * ae-6.r23.nycmny01.us.bb.gin.ntt.net [129.250.2.8]

14 758 ms 509 ms 545 ms ae-1.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.69]

15 482 ms 684 ms 559 ms xe-6-4.r02.nycmny03.us.bb.gin.ntt.net [129.250.2.47]

16 520 ms 449 ms 484 ms ge-3-13.r02.nycmny03.us.ce.gin.ntt.net [129.250.193.34]

17 * * * Request timed out.

18 798 ms 576 ms 867 ms 62.152.114.106

19 562 ms * 519 ms EURNetSW01.EURNetCity.net [80.68.192.5]

20 623 ms 629 ms 602 ms hosting.userspace.it [80.68.200.108]

Trace complete.

[kitkatforme013]

sorry this is for the coral.lt

C:\Documents and Settings\0>tracert coral.lt

Tracing route to coral.lt [77.79.12.51]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1

2 307 ms 488 ms 533 ms 112.201.128.1.pldt.net [112.201.128.1]

3 * * * Request timed out.

4 612 ms * 389 ms 210.213.132.6.static.pldt.net [210.213.132.6]

5 * 542 ms 420 ms 210.213.128.74.static.pldt.net [210.213.128.74]

6 553 ms * 300 ms 210.213.129.45.static.pldt.net [210.213.129.45]

7 * 190 ms 248 ms 210.213.128.41.static.pldt.net [210.213.128.41]

8 * 340 ms 253 ms 210.213.131.89.static.pldt.net [210.213.131.89]

9 318 ms * 606 ms 210.213.128.105.static.pldt.net [210.213.128.105]

10 * 581 ms 674 ms ix-0-1-1-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.53]

11 * 743 ms * if-8-1508.tcore2.AEQ-Ashburn.as6453.net [64.86.252.74]

12 654 ms 581 ms 681 ms if-10-2.tcore1.FR0-Frankfurt.as6453.net [195.219.50.97]

13 * * * Request timed out.

14 635 ms * * if-3-0-0.core1.STK-Stockholm.as6453.net [195.219.36.2]

15 667 ms 640 ms 713 ms ix-6-0.core1.STK-Stockholm.as6453.net [195.219.131.42]

16 * 690 ms 759 ms 87.110.223.238

17 582 ms 807 ms 540 ms 195.13.173.45

18 572 ms 967 ms 702 ms 88.216.87.35

19 781 ms 713 ms 858 ms 84.32.142.180

20 656 ms 636 ms 652 ms sl-104.splius.lt [62.80.224.104]

21 681 ms 813 ms 730 ms hst-12-50.duomenucentras.lt [77.79.12.50]

22 707 ms 795 ms 718 ms hst-12-51.duomenucentras.lt [77.79.12.51]

Trace complete.

C:\Documents and Settings\0>

[kitkatforme013]

still have no connection…

[matias067]

hi sought...

Philippines also here...:

>tracert www.nsanedown.com

Tracing route to www.nsanedown.com [77.79.7.88]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 585 ms 935 ms 1393 ms 112.203.0.1.pldt.net [112.203.0.1]

3 1006 ms 421 ms 296 ms 119.93.254.161

4 162 ms 277 ms 130 ms 210.213.130.82.static.pldt.net [210.213.130.82]

5 518 ms 676 ms 501 ms 210.213.128.22.static.pldt.net [210.213.128.22]

6 358 ms 264 ms 389 ms 210.213.129.6.static.pldt.net [210.213.129.6]

7 701 ms 708 ms 709 ms 210.213.128.37.static.pldt.net [210.213.128.37]

8 304 ms 541 ms 103 ms 210.213.131.89.static.pldt.net [210.213.131.89]

9 756 ms 905 ms 768 ms 210.213.128.137.static.pldt.net [210.213.128.137

10 338 ms 361 ms 502 ms ix-0-1-1-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.53]

11 1483 ms 1009 ms 680 ms if-8-1508.tcore2.AEQ-Ashburn.as6453.net [64.86.252.74]

12 859 ms 1641 ms 1908 ms if-10-2.tcore1.FR0-Frankfurt.as6453.net [195.219.50.97]

13 * * * Request timed out.

14 750 ms 547 ms 719 ms if-3-0-0.core1.STK-Stockholm.as6453.net [195.219.36.2]

15 782 ms 599 ms 567 ms ix-4-0-0.core1.STK-Stockholm.as6453.net [195.219.131.38]

16 1305 ms 1205 ms 900 ms 87.110.223.238

17 1006 ms 776 ms 721 ms 195.13.173.45

18 1221 ms 1128 ms 964 ms 88.216.87.35

19 682 ms 786 ms 1222 ms 84.32.142.180

20 1204 ms 764 ms 628 ms sl-104.splius.lt [62.80.224.104]

21 * 1177 ms 985 ms vade.aleja.lt [77.79.7.254]

22 * * 1439 ms server.nsanedown.com [77.79.7.88]

Trace complete.

btw...my last visit on nsanedown was on January 6...(when I downloaded ESET Smart Security™ 4.2.67.10) after that I couldn't access anymore nsanedown.com

[shought]

We're probably going to move to another host because of this (as our current host (BalticServers) does not want to look into the problems nor even recognizes the fact that there are problems). Finding and moving to another host is however a time consuming process, so patience is advised ;)

In the mean time please try using a proxy to access our site.

Thanks for your understanding :)

[teamacc]

Holland reporting in:

Not working from here either.

Pinging works

Tracert shows no problems.

Can reach it from other ISPs (4 confirmed working, 1 doesnt work)

Can reach it from an (unsecure) vpn connection, so it shouldnt be deep packet inspection blocking it.

Proxys etc all work fine.

I hope you can either set up a proxy that redirects to nsane at a different isp, or move the entire site (as the isp is unwilling)

Would like to host a proxy, but, as stated above, i cannot reach nsane...

[shought]

We are aware of the problems and we've noticed that they seem to be 'expanding'. Previously the Philippines and southern India were affected, now someone from Portugal, the Netherlands (you) and our forum database in the US are affected as well.

We're looking for a new host and are planning to move as soon as possible, in the mean time please try using any of the publicly available proxies out there.

Technical stuff: You can ping and do tracerts to our server perfectly fine because for some reason (this is not too weird actually, but still) our upstream bandwidth takes a different route than our downstream bandwidth does. So your requests reach the server, the server produces the page and send it back but you never receive it.

[teamacc]

Well, that sounds perfectly reasonable, but, if you are saying that downstream traffic takes a different route, how come the site can receive and respond to ping requests?

Seems like the ping to the server is "downstream" (as seen by the server) and the response is "upstream" (again, from the perspective of the server)

[shought]

Well, the answer lies in what I just said: because it takes a different route. A ping from the server (for some reason) takes a different route than a ping towards the server, even though they seem to be the same thing (reversed).

So where your ping makes use of the routers A, B, C the ping from the server makes use of the routers D, B, A. (D being the messed up one.)

(I'm not entirely sure about the following, but I believe ping does not work like this:

you --> A

you --> A --> B

you --> A --> B --> C

but rather:

you --> A

A --> B

B --> C

C --> server

Whereas the server would do:

server --> D

D --> B

B --> A

A --> you

(The above is obviously simplified, but the basic principle is sound, I think :P))

[teamacc]

Well, then again, in order to respond to a ping request, the server has to "upload" a few bytes, going through router D (damaged one), which ensures it would never reach me. This seems untrue, as it does reach me.

[shought]

No no ;)

Because, as I just suggested, I believe it works like this:

you --> A

A --> B

B --> C

C --> server

Because the ping too the route A, B, C, the server will respond to the C router. I believe (again not 100% sure) that pinging is not:

you --> A

you --> B

you --> C

you --> server

But it is what I just mentioned, can you see how those are different?

[Corragio]

Holland reporting in:

Not working from here either.

Pinging works

Tracert shows no problems.

Can reach it from other ISPs (4 confirmed working, 1 doesnt work)

Can reach it from an (unsecure) vpn connection, so it shouldnt be deep packet inspection blocking it.

Proxys etc all work fine.

I hope you can either set up a proxy that redirects to nsane at a different isp, or move the entire site (as the isp is unwilling)

Would like to host a proxy, but, as stated above, i cannot reach nsane...

I can confirm what teamacc says.

Here from the Netherlands some ISP's are not showing the site, but ping does.

My ISP (TweakDSL) doesn't reach, but at my work ISP (XS4ALL) does work and reaches the site.

Anonymous proxy works.

Hope there will be a fix soon.

[teamacc]

Just to kick an old(ish) topic:

Its working again!

I dont know if you guys migrated to another ISP, or the ISP fixed stuff for you, but nsanedown is opening faster than ever.

Also (offtopic): Id like to support you by viewing the ads, but im running opera. Is there any way to add an exception for nsanedown in the urlfilter.ini stuff?