Blocking the site by the provider Rostelecom or the curvature of the hands?

Question

Nginx

Dear community! Please help me to solve a problem, possibly similar to this one .
There are 2 sites (php) on nginx, static ip address and internet from RT. Until recently, everything worked, after May 21, 2013, the low traffic of the site and the issuance of search engines fell sharply.
So, what are the symptoms:
1) some users from certain ip cannot log in - the server just does not respond
2) through anonymizers - does not log in
3) Tor - does not log in, with the rare exception of some ip addresses (193.*.*.*., 128.*.*.*., 18.*.*.*.,)
4) opera mini via phone - 408 error
5) Opera turbo mode - does not open
(if you specify an html, txt, xml document on the servers - these methods open these documents. png, jpeg, ico, swf - do not open)
The site opens:
1) Via LAN
2) Via Yandex browser in turbo mode
3) Tor - very rarely
4) MTS via 3G modem
Until the specified date, all of the listed methods opened sites. Configs, server, network settings did not change. The server also works locally. Search bots are coming. ). Some services see the site (View as Googlebot or 2ip), all others say that the site is dead.

I called technical support - they pinged - they said everything is pinging normally. Is the internet working? Works. We didn't block anything. We provide only Internet access services, the rest is your problem. The site itselfz-torrents.ru
Suspicions on the server, network, router — all shoveled. There were no messages like "We're sorry, but access to this site is closed ..." was not. IP and domains in the registry do not appear. There are only 2 domains on IP.
Where to dig? Change provider or straighten your arms?
UPD 07/29/13: I installed a server on a different hardware - the site is available. So it's still crooked hands. I will dig further. Remaining hardware or server settings

Answer 1

Dom.Ru Nizhny Novgorod, test index.html opens, normal index fails. When you turn on the turbo mode in Yandex.Browser (an analogue of Turbo in Opera), everything immediately opens.

Answer 2

There is a possibility that it is Rostelecom. In the Kirov region, for example, lurkmore.to does not work directly. No messages are also issued, it just does not load and that's it. Through OperaTurbo works.

Answer 3

From the Rostov region:
$ ping z-torrents.ru
PING z-torrents.ru (95.188.69.175) 56(84) bytes of data.
64 bytes from stc.175.69.188.95.dsl.krasnet.ru (95.188.69.175): icmp_req=1 ttl=55 time=128
ms icmp_req=2 ttl=55 time=150 ms 64 bytes
from stc.175.69.188.95.dsl.krasnet.ru (95.188.69.175)
:
-torrents.ru (95.188.69.175), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.636 ms 0.881 ms 1.101 ms
2 196.214.221.83. ms 36.939 ms
3 212.214.221.83.static.donpac.ru (83.221.214.212) 37.692 ms 39.087 ms
4 xe-1-3-3.rndn-rgr1.ug.ip.rostelecom.ru (188.128.0.237) 44.055 ms xe-2-0-0.rndn-rgr3.ug.ip.rostelecom.ru (188.254.36.213 ) 48.529 ms xe-0-2-0.rndn-rgr3.ug.ip.rostelecom.ru (188.254.36.205) 50.226 ms
5 95.167.92.14 (95.167.92.14) 135.835 ms 141.315 ms 95.167.93.14.95.14.95.167.93.14. 147.564 ms
6 customer-AS41440.xe-0-3-0.797.krsn-rgr4.sib.ip.rostelecom.ru (87.226.231.142) 156.370 ms ) 109.453 ms
7 xe-8-2-0.ksk-dr2.ncc.sibirtelecom.ru (213.228.105.21) 124.323 ms xe-4-1-0.ksk-dr2.ncc.sibirtelecom.ru (213.228.105.17) 128.324ms 123.298ms
8 TE2-0-0.ksk-bbar1.ncc.sibirtelecom.ru (213.228.119.170) 136.070 ms TE4-0-0.ksk-bbar1.ncc.sibirtelecom.ru (213.228.119.166) 134.680 ms TE2-0-0 .ksk-bbar1.ncc.sibirtelecom.ru (213.228.119.170) 124.373ms
9 stc.175.69.188.95.dsl.krasnet.ru (95.188.69.175) 144.489ms 147.885ms 1947.606ms
10 .ru (95.188.69.175) 157.422 ms 150.291 ms 153.986 ms
Nmap shows that port 80 is open. At the same time, not a single byte from the server reaches HTTP.
Either you now have something with the web server, or Rostelecom really cuts traffic from you.
Another point - you have an unknown service hanging on port 2710, but it seems that it is connected either with a torrent or with VoIP / SIP. I had a situation when a provider at a corporate rate suddenly silently began to cut SIP traffic, and a month later began to offer telephone numbers with VoIP.
Verdict: if the situation is not resolved in a couple of weeks, then the move.

Answer 4

all sorts of pings

tracert z-torrents.ru
Трассировка маршрута к z-torrents.ru [95.188.69.175]
с максимальным числом прыжков 30:
1 1 ms 1 ms <1 мс pool-ЧЁТА-ТАМ.is74.ru [31.207.224.1]
2 1 ms <1 мс 1 ms 10.100.40.41
3 1 ms 1 ms 1 ms 10.100.14.129
4 1 ms 1 ms 1 ms 10.100.14.130
5 33 ms 240 ms <1 мс 87.226.216.125
6 42 ms 42 ms 42 ms 95.167.92.14
7 90 ms 41 ms 40 ms 95.167.15.222
8 43 ms 45 ms 42 ms xe-8-2-0.ksk-dr2.ncc.sibirtelecom.ru [213.228.105.21]
9 72 ms 69 ms 70 ms TE4-0-0.ksk-bbar1.ncc.sibirtelecom.ru [213.228.119.166]
10 60 ms 60 ms 60 ms stc.175.69.188.95.dsl.krasnet.ru [95.188.69.175]
11 60 ms 60 ms 60 ms stc.175.69.188.95.dsl.krasnet.ru [95.188.69.175]
ping z-torrents.ru
Обмен пакетами с z-torrents.ru [95.188.69.175] с 32 байтами данных:
Ответ от 95.188.69.175: число байт=32 время=60мс TTL=54
Ответ от 95.188.69.175: число байт=32 время=60мс TTL=54
Ответ от 95.188.69.175: число байт=32 время=60мс TTL=54
Ответ от 95.188.69.175: число байт=32 время=60мс TTL=54

In the traceroute, I am confused by two identical nodes numbered 10 and 11, maybe some kind of loop, although I don’t understand. It does not open at all in the browser, it just hangs for a very long time. In telnet, if you open and send some kind of crookedness, then nginx replies:

HTTP/1.1 400 Bad Request
Server: nginx/0.8.30
Date: Sun, 28 Jul 2013 10:47:13 GMT
Content-Type: text/html; charset=utf-8
Content Length: 173
Connection: close

<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx/0.8.30</center>
</body>
</html>

Maybe a problem between nginx and Apache (or whatever you have)?

Answer 5

Rostelecom MO - normally opens in the browser

Answer 6

index.html returns.
it would be nice to see the nginx config file.
The root is not given, the logo is also not available.
Checked from the Ukraine server.

curl logo2

mail# curl -Svi z-torrents.ru/images/logo/logo2.png
* About to connect() to z-torrents.ru port 80 (#0)
* Trying 95.188.69.175…
* connected
* Connected to z-torrents.ru (95.188.69.175) port 80 (#0)
> GET /images/logo/logo2.png HTTP/1.1
> User-Agent: curl/7.24.0 (i386-portbld-freebsd8.3) libcurl/7.24.0 OpenSSL/0.9.8q zlib/1.2.3
> Host: z-torrents.ru
> Accept: */*
>
* Recv failure: Operation timed out
* Closing connection #0
curl: (56) Recv failure: Operation timed out

The track was horrendous.

traceroute z-torrents.ru

mail# traceroute z-torrents.ru
traceroute to z-torrents.ru (95.188.69.175), 64 hops max, 40 byte packets
1 gateway.dc.hostvds.net (192.102.6.2) 47.457 ms 48.047 ms 48.362 ms
2 be12.253.cr-1.f17.kiev.volia.net (82.144.193.10) 48.115 ms 48.440 ms 48.109 ms
3 be1.208.cr-1.g50.kiev.volia.net (77.120.1.138) 48.873 ms 50.826 ms 50.004 ms
4 te8-8.ccr02.kbp01.atlas.cogentco.com (149.6.190.13) 47.100 ms 48.462 ms 46.969 ms
5 te0-0-0-4.ccr22.bts01.atlas.cogentco.com (130.117.51.41) 66.689 ms
te0-3-0-1.ccr22.bts01.atlas.cogentco.com (130.117.51.169) 66.758 ms
te0-2-0-1.ccr22.bts01.atlas.cogentco.com (154.54.39.42) 66.894 ms
6 te0-2-0-2.ccr22.muc01.atlas.cogentco.com (154.54.38.253) 74.273 ms
te0-1-0-5.ccr22.muc01.atlas.cogentco.com (154.54.36.18) 72.467 ms
te0-0-0-5.ccr22.muc01.atlas.cogentco.com (130.117.51.166) 73.889 ms
7 te0-2-0-2.mpd22.fra03.atlas.cogentco.com (130.117.50.241) 79.245 ms
te0-6-0-2.mpd22.fra03.atlas.cogentco.com (154.54.74.218) 79.642 ms
te0-6-0-2.ccr22.fra03.atlas.cogentco.com (154.54.74.214) 79.488 ms
8 te0-1-0-1.ccr21.fra06.atlas.cogentco.com (154.54.36.61) 79.635 ms
te0-6-0-5.ccr21.fra06.atlas.cogentco.com (154.54.73.145) 78.000 ms
te0-5-0-7.ccr21.fra06.atlas.cogentco.com (154.54.76.58) 79.366 ms
9 te2-1.ccr01.fra08.atlas.cogentco.com (154.54.62.138) 78.492 ms
te1-2.ccr01.fra08.atlas.cogentco.com (154.54.59.106) 79.363 ms
te3-2.ccr01.fra08.atlas.cogentco.com (154.54.63.242) 78.372 ms
10 149.11.138.10 (149.11.138.10) 79.978 ms
149.11.138.14 (149.11.138.14) 79.611 ms
149.11.138.2 (149.11.138.2) 79.139 ms
11 95.167.93.14 (95.167.93.14) 167.905 ms 177.765 ms
95.167.92.14 (95.167.92.14) 167.817 ms
12 188.254.44.134 (188.254.44.134) 176.110 ms 170.052 ms
customer-AS41440.xe-1-2-0.798.krsn-rgr4.sib.ip.rostelecom.ru (87.226.171.114) 168.068 ms
13 xe-3-1-0.ksk-dr2.ncc.sibirtelecom.ru (213.228.105.9) 177.615 ms 176.394 ms 180.059 ms
14 TE4-0-0.ksk-bbar1.ncc.sibirtelecom.ru (213.228.119.166) 189.538 ms
TE2-0-0.ksk-bbar1.ncc.sibirtelecom.ru (213.228.119.170) 181.671 ms 182.033 ms
15 stc.175.69.188.95.dsl.krasnet.ru (95.188.69.175) 196.867 ms * 187.604 ms
16 stc.175.69.188.95.dsl.krasnet.ru (95.188.69.175) 190.765 ms 189.145 ms 189.742 ms