Why are some sites being blocked?

[#1]

I hav tried to access some sites and they appear to be blocked through Plusnet I can access the site through my mobile data but not if i turned wifi back on.  One site I was accessing is forum.synology.com though I can access synology.

[#2]

The forum will not load for me , and downdetector cant find it ? odd

[#3]

The forum or the main site don't work for me either, so @mark57 you're not alone there.

[#4]

forum.synology.com Will load over a vpn but not on a BT connection here

[#5]

@dvorak - Does this mean this is a routing issue with BT / PN?

[#6]

That would be my guess

[#7]

Still not looking good - it's been like this for a few days now.

traceroute to forum.synology.com, 20 hops max
1 router
2 lo0.central10.pcn-bng04.plus.net (195.166.130.251) 11.941 ms
3 195.99.125.144 (195.99.125.144) 11.940 ms
4 peer6-hu0-1-0-1.telehouse.ukcore.bt.net (195.99.127.25) 15.307 ms
5 t2c3-et-3-1-0-0.uk-lon1.eu.bt.net (166.49.211.236) 12.443 ms
6 ixp1-xe-11-1-0-0.us-nyc.eu.bt.net (166.49.208.146) 79.784 ms
7 * * () 0.000 ms
8 202.39.83.109 (202.39.83.109) 83.780 ms
9 202.39.83.109 (202.39.83.109) 209.292 ms
10 202.39.91.26 (202.39.91.26) 352.588 ms
11 * * () 0.000 ms
12 * * () 0.000 ms
13 * * () 0.000 ms

[#8]

Ah I just logged on in the first time for ages especially to report this myself!!!    I cannot get to forums.qnap.com via plusnet and when I asked if the site was down on the qnap reddit, only one other person said yes and he was also on plusnet.  Other people living near me but not on plusnet could connect fine.

Going by our traces the holdup appears to be in Taiwan:

Tracing route to forum.qnap.com [211.21.125.36] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254

2 6 ms 6 ms 6 ms lo0.central10.psb-bng03.plus.net [195.166.130.254]

3 7 ms 7 ms 6 ms 411.be7.psb-ir01.plus.net [84.93.253.115]

4 7 ms 6 ms 7 ms core1-BE1.southbank.ukcore.bt.net [195.99.125.130]

5 8 ms 7 ms 7 ms peer6-hu0-6-0-6.telehouse.ukcore.bt.net [195.99.127.3]

6 8 ms 7 ms 8 ms t2c3-et-3-1-0-0.uk-lon1.eu.bt.net [166.49.211.236]

7 75 ms 76 ms 75 ms ixp1-xe-11-1-0-0.us-nyc.eu.bt.net [166.49.208.146]

8 * * * Request timed out.

9 75 ms 75 ms 75 ms 202.39.83.109

10 135 ms 135 ms 135 ms 202.39.83.106

11 134 ms 133 ms 133 ms 202.39.83.46

12 * * * Request timed out.

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.

[#9]

Yeh, I was going to report this too. Unfortunately I'm struggling to talk to synooauth.synology.com which means I am unable to backup my NAS using my preferred provider.

I was about to ask what gives but I ran the same traceroute to synooauth.synology.com and got pretty much the same results as IngeJones.

[ xmanning@pyke.lan:~ ] $ traceroute synooauth.synology.com
traceroute to synooauth.synology.com (59.124.61.228), 64 hops max, 52 byte packets
 1  dsldevice (192.168.1.254)  2.616 ms  1.761 ms  2.423 ms
 2  * * *
 3  * * *
 4  be3-3100.pcn-ir01.plus.net (195.166.143.128)  17.352 ms  17.771 ms  16.492 ms
 5  195.99.125.136 (195.99.125.136)  14.034 ms  14.127 ms  15.479 ms
 6  195.99.127.87 (195.99.127.87)  16.516 ms
    195.99.127.83 (195.99.127.83)  21.299 ms  16.631 ms
 7  t2c3-et-3-1-0-0.uk-lon1.eu.bt.net (166.49.211.236)  16.282 ms
    t2c3-et-7-1-0-0.uk-lon1.eu.bt.net (166.49.211.228)  14.885 ms  14.893 ms
 8  ixp1-xe-1-2-0-0.us-nyc.eu.bt.net (166.49.208.140)  81.943 ms
    ixp1-xe-11-3-1-0.us-nyc.eu.bt.net (166.49.208.169)  82.388 ms  83.052 ms
 9  * * *
10  202.39.83.109 (202.39.83.109)  82.305 ms  103.238 ms  80.908 ms
11  202.39.83.106 (202.39.83.106)  144.468 ms  143.994 ms  144.187 ms
12  202.39.91.26 (202.39.91.26)  368.023 ms  338.524 ms  307.128 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
^C

Bit of a dead-end route to get there.

[#10]

Sorry to hear you guys are unable to load forum.synology.com whilst on your Plusnet connection.

This is already on my list to raise with our Network team to investigate further.

[#11]

@Gandalf mine wasn't synology.com it was forums.qnap.com.  Weirdly though, both sites are forums related to NAS storage!!  I wonder why.  Like the previous poster, I can get to qnap.com fine, just the forums are timing out.

[#12]

Apologies, I missed that.

Thanks for the heads up, I'll follow up on this tomorrow.

[#13]

This is happening to me, too.  I am unable to access forum.synology.com.

That's a pain.  But what really hurts is I can't access "payment.synology.com".  This site is used by my NAS to update the package center.  I get the following error on my NAS:

2017-05-30T05:19:35+00:00  builtin-dyn-autopkgupgrade-default: pkgcurltool.cpp:440 Failed to download https://payment.synology.com/api/getPackageList.php, code=28, err=Error

This is the command that I need:

curl -v  https://payment.synology.com/api/getPackageList.php

If I try the same command on my local machine, it also fails.

I have a machine that I can SSH into that does not use plusnet.  I if try the curl command on that machine, it works with no problem.

The simple truth is that if this doesn't get fixed soon I will have to change providers.  This problem largely renders my NAS useless - I recently re-installed the NAS software, and now I can't add any packages to it because the "Package Center" can't connect.

Thanks

[#14]

I reckon someone on our IP block has been spamming or script-bombing forums or something and we've all been denied somewhere up the chain.  Maybe Synology and QNAP both subscribe to a particular forum hosting system.

[#15]

Thanks for your patience guys, much appreciated.

One of my colleagues has investigated this, and identified a possible routing problem.

He has contacted the network where the sites are hosted to investigate further. This does unfortunately mean that we don't have a time frame for a fix on this one. We'll try to keep you updated as best as we can as we receive updates.