Polsat news website blocked by Elisa

The problem seems to be global. Also Down for Everyone or Just Me reports polsatnews.pl as down.

No, the website’s servers are fine. It’s working, but not trough Elisa networks.

Initially I thought the server is down, but I asked friends from Poland if they also experience it - they refused. Also, when I connect through my corporate network - it’s working ok, all the time. I checked 2 minutes ago.

It seems that polsatnews do not open with Telia’s subscription either. Maybe something wrong with corenetwork??

Ping does not work either.

ping polsatnews.pl

Pinging polsatnews.pl [37.247.239.155] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Maybe the site is under denial of service attack and they have to throttle connections from outside Poland. If your corporate VPN terminates in Poland, everyone of course thinks you are connecting from Poland, when you use VPN.

Have you tried running traceroute polsatnews.pl, or tracert polsatnews.pl on Windows systems? I got as far as be2486.rcr21.b016833-0.waw01.atlas.cogentco.com before the trace went cold.

DDOS attack taking 4 days? Unlikely.

My corporate network ends-up in Switzerland. It works from there and probably the rest of Europe.

Seems that it’s not a problem with DNS. I tried “DNS over https” setting in firefox and selected “cloudflare DNS”. That had no effect.  Besides that my ping gives IP address: 37.247.239.156, which proves it’s correct.

ping polsatnews.pl

PING polsatnews.pl (37.247.239.156) 56(84) bytes of data.

Traceroute gives no information at all.

I tried it with Kaisanet internet access and end up with the same result.

I tested with Elisa’s subscription:

tracert polsatnews.pl

Tracing route to polsatnews.pl [37.247.239.156]
over a maximum of 30 hops:

 ………………………………………………………………………..

  4    18 ms    16 ms    17 ms  213.192.186.78
  5    21 ms    16 ms    16 ms  ae3.bbr1.esp1.fi.ip4.elisa.net [213.192.186.77]

  6    40 ms    40 ms    40 ms  213.192.184.101
  7     *        *        *     Request timed out.
  8    43 ms    43 ms    43 ms  be3458.ccr42.ams03.atlas.cogentco.com [154.54.39
.185]
  9    48 ms    48 ms    48 ms  be2816.ccr42.ham01.atlas.cogentco.com [154.54.38
.210]
 10    61 ms    61 ms    61 ms  be2484.ccr21.waw01.atlas.cogentco.com [130.117.5
1.105]
 11    60 ms    60 ms    60 ms  be2486.rcr21.b016833-0.waw01.atlas.cogentco.com [154.54.37.42]
 12     *        *        *     Request timed out.
--------------------------------------------------------------
 30     *        *        *     Request timed out.

Trace complete.

Trace starts ok , but stops after step 11. It seems that somewhere in the core network is a faulty or wrong configured router.  I don’t know who is responsible to correct that???