Unable to resolve routing details using PLUSNET default settings .

[#1]

Hi , 

I have started to have issues with routing details when using the default plusnet settings

If switch to a VPN or other provider there are no issues.   Just looking to see where I can report the issues so routing info can be updated / refreshed . 

for example :  this worked fine last week , but now never resolves . 

traceroute to mycalelle.co.uk (192.185.169.166), 64 hops max, 52 byte packets

 1  192.168.1.254 (192.168.1.254)  1.236 ms  0.534 ms  0.450 ms

 2  251.core.plus.net (195.166.130.251)  14.378 ms  12.355 ms  12.157 ms

 3  84.93.253.95 (84.93.253.95)  13.257 ms  12.788 ms  12.997 ms

 4  195.99.125.144 (195.99.125.144)  12.982 ms  12.786 ms

    core1-be1.colindale.ukcore.bt.net (195.99.125.132)  13.003 ms

 5  peer7-et-4-0-4.telehouse.ukcore.bt.net (194.72.16.128)  13.249 ms

    core5-hu0-7-0-15.faraday.ukcore.bt.net (195.99.127.36)  13.716 ms

    peer7-et-3-1-4.telehouse.ukcore.bt.net (109.159.252.168)  14.276 ms

 6  166-49-209-132.gia.bt.net (166.49.209.132)  13.591 ms

    166-49-214-194.gia.bt.net (166.49.214.194)  13.646 ms  13.406 ms

 7  * * *

 8  be2870.ccr41.lon13.atlas.cogentco.com (154.54.58.173)  13.841 ms  13.928 ms  13.619 ms

 9  be2490.ccr42.jfk02.atlas.cogentco.com (154.54.42.85)  81.628 ms

    be2317.ccr41.jfk02.atlas.cogentco.com (154.54.30.185)  82.856 ms

    be2490.ccr42.jfk02.atlas.cogentco.com (154.54.42.85)  83.567 ms

10  be2807.ccr42.dca01.atlas.cogentco.com (154.54.40.110)  86.882 ms

    be2806.ccr41.dca01.atlas.cogentco.com (154.54.40.106)  110.580 ms  109.366 ms

11  be2113.ccr42.atl01.atlas.cogentco.com (154.54.24.222)  113.530 ms

    be2112.ccr41.atl01.atlas.cogentco.com (154.54.7.158)  104.965 ms  105.384 ms

12  be2126.rcr51.b009789-2.atl01.atlas.cogentco.com (154.54.82.206)  114.311 ms  116.749 ms

    be2127.rcr51.b009789-2.atl01.atlas.cogentco.com (154.54.82.210)  114.109 ms

13  38.104.183.2 (38.104.183.2)  137.242 ms  116.004 ms  114.137 ms

14  50-6-131-0.unifiedlayer.com (50.6.131.0)  106.312 ms  103.441 ms  120.857 ms

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

thanks 

Chris 

[#2]

Sorry, we're doing some work on the site

Thank you for being patient. We are doing some work on the site and will be back shortly.

[#3]

@ChrisPender I dont think its a PN routing problem. A traceroute from my PN connection is very similar but mine does complete

 1   192.168.5.1  0.613ms  0.526ms  0.522ms
  2   195.166.130.255  7.117ms  6.449ms  6.716ms
  3   84.93.253.123  7.228ms  7.723ms  7.753ms
  4   195.99.125.142  8.151ms  7.699ms  8.146ms
  5   109.159.252.90  7.919ms  8.056ms  7.650ms
  6   166.49.214.194  7.958ms  8.182ms  7.742ms
  7   *  *  *
  8   154.54.60.5  9.687ms  9.384ms  8.867ms
  9   154.54.30.185  76.926ms  76.543ms  76.166ms
 10   154.54.40.110  80.885ms  81.407ms  80.403ms
 11   154.54.24.222  127.625ms  99.961ms  99.710ms
 12   154.54.82.206  99.355ms  98.469ms  97.752ms
 13   38.104.183.2  110.409ms  109.413ms  109.396ms
 14   50.6.131.0  108.877ms  109.873ms  109.551ms
 15   *  *  *
 16   192.185.169.166  98.235ms  97.608ms  97.539ms

However my connection is on a static IP , which will likely be a different IP range to yours. Does the site have any IP access restrictions ?

[#4]

As per my previous post, I think it is more to do with the site undergoing work.