 by Marcus » Tue, 08Feb19 05:53
by Marcus » Tue, 08Feb19 05:53 
			
			Hi,
Just thought I'd give you some more information concerning this, as we are also experiencing the same issue here.
Here's the tracert from my own PC:
Tracing route to sharks-lagoon.fr [85.31.220.21]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     9 ms     7 ms    11 ms  10.0.224.1
  3     9 ms     8 ms    11 ms  vl-201.gw03.flfrd.phub.net.cable.rogers.com [66.185.90.241]
  4    12 ms    14 ms     7 ms  gi-2-0.gw01.flfrd.phub.net.cable.rogers.com [66.185.83.169]
  5    13 ms    24 ms    13 ms  so-4-0-0.gw02.ym.phub.net.cable.rogers.com [66.185.82.125]
  6    14 ms    12 ms    13 ms  so-2-0-0.gw02.mtnk.phub.net.cable.rogers.com [66.185.80.185]
  7    31 ms    31 ms    31 ms  pos-2-0.igw01.ny8th.phub.net.cable.rogers.com [66.185.81.102]
  8     *        *        *     Request timed out.
  9    39 ms    40 ms    43 ms  vl3491.ccr04.jfk02.atlas.cogentco.com [154.54.7.9]
 10   117 ms   113 ms   115 ms  te4-3.mpd02.par01.atlas.cogentco.com [130.117.2.10]
 11   127 ms   125 ms   128 ms  te2-1.ccr01.mrs01.atlas.cogentco.com [130.117.2.213]
 12   128 ms   125 ms   125 ms  ip-star.demarc.cogentco.com [149.6.83.174]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *     ^C
And here's the tracert from an online tool:
1	sackett.la.cyberverse.net (209.151.232.33)	0%	0.25	23.01	116.04
2	a.flint-sackett.la.cyberverse.net (209.151.232.1)	0%	0.23	0.29	0.39
3	ge-3-1-0.mpr1.lax9.us.above.net (209.133.76.33)	0%	0.23	0.99	8.16
4	so-0-0-0.mpr4.lax9.us.above.net (64.125.26.146)	0%	0.42	9.65	45.06
5	so-0-1-0.mpr2.sjc2.us.above.net (64.125.26.30)	0%	9.00	9.06	9.19
6	so-3-0-0.mpr1.sjc7.us.above.net (64.125.30.177)	0%	9.25	10.45	21.95
7	g4-6.pr01.sjc03.atlas.psi.net (64.125.12.90)	0%	11.10	11.26	11.54
8	vl3498.ccr02.sjc01.atlas.cogentco.com (154.54.6.233)	0%	11.58	11.65	11.72
9	te8-3.ccr02.sfo01.atlas.cogentco.com (154.54.2.137)	0%	12.67	12.75	12.86
10	te2-3.ccr02.mci01.atlas.cogentco.com (154.54.24.110)	0%	44.92	46.49	61.26
11	te2-1.ccr02.ord01.atlas.cogentco.com (154.54.5.174)	0%	55.99	56.12	56.94
12	te8-2.ccr04.jfk02.atlas.cogentco.com (154.54.7.205)	0%	75.24	75.31	75.55
13	te7-2.mpd02.par01.atlas.cogentco.com (154.54.1.22)	0%	148.99	149.09	149.19
14	te1-1.ccr01.lys01.atlas.cogentco.com (130.117.2.186)	0%	156.03	156.11	156.24
15	te1-1.ccr01.mrs01.atlas.cogentco.com (130.117.1.209)	0%	160.76	202.85	372.10
16	ip-star.demarc.cogentco.com (149.6.83.174)	10%	160.80	160.87	160.95
17	liberty-multimedia-customers.ip-star.net (193.34.16.38)	10%	160.81	160.93	161.06
18	85.31.220.21 (85.31.220.21)	10%	161.24	161.40	161.56
==================================================
This means that it's NOT a problem with shark's site.
It is also not a problem with Browser Settings. What seems to be happening is that the site is being blocked as a part of "regional filtering" of some sort, somewhere in between (ip-star.net?).
As was mentioned above, using an anonymous proxy would probably work as a work around. I don't think there's any easy solution except to have the site moved again. (There may be another way, but you'll have to let me see if I can get it to work; I'll get back to you all.)