DNS/Routing issues for the last 36 hours

[#1]

No change here even after modem and router reboot. No matter what I always seem to end up on the 51.6.xxx.xxx ip range.

 tracert xbox.com

1 <1 ms <1 ms <1 ms TL-WR841N [192.168.1.1]
2 * * * Request timed out.
3 * * 20 ms 129.hiper04.sheff.dial.plus.net.uk [195.166.143.129]
4 21 ms 21 ms 21 ms be3-3100.pcn-ir01.plus.net [195.166.143.128]
5 21 ms 21 ms 21 ms core1-BE1.colindale.ukcore.bt.net [195.99.125.132]
6 21 ms 21 ms 21 ms peer1-et-1-3-0.telehouse.ukcore.bt.net [195.99.127.19]
7 22 ms 22 ms 22 ms 195.99.126.57
8 24 ms 24 ms 24 ms ae11-0.lon04-96cbe-1b.ntwk.msn.net [207.46.44.155]
9 100 ms 102 ms 102 ms 104.44.5.28
10 102 ms 102 ms 102 ms be-4-0.ibr02.was05.ntwk.msn.net [104.44.4.28]
11 100 ms 102 ms 101 ms be-3-0.ibr02.bn1.ntwk.msn.net [104.44.4.27]
12 99 ms 100 ms 99 ms ae73-0.bn1-96c-2a.ntwk.msn.net [104.44.8.17]
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 * * * Request timed out.

[#2]

C:\Users\Jonty>tracert portal.plus.net

Tracing route to portal.plus.net [212.159.9.2]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    17 ms    17 ms    16 ms  be3-3102.pcn-ir02.plus.net [195.166.143.132]
  5    17 ms    18 ms    17 ms  gr-11-1-0.pcl-cr01.plus.net [195.166.129.173]
  6    20 ms    18 ms    18 ms  po2.pcl-gw01.plus.net [195.166.129.41]
  7    24 ms    26 ms    24 ms  84-93-224-48.plus.net [84.93.224.48]
  8    24 ms    24 ms    23 ms  reth0.ptp-elbfw.plus.net [84.92.0.109]
  9    24 ms    24 ms    25 ms  10.104.128.53
 10    28 ms    25 ms    24 ms  portal.plus.net [212.159.9.2]

Trace complete.

Tracing route to e2537.dspb.akamaiedge.net [23.198.73.73]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *       17 ms    17 ms  133.hiper04.sheff.dial.plus.net.uk [195.166.143.133]
  4    17 ms    17 ms    17 ms  be3-3102.pcn-ir02.plus.net [195.166.143.132]
  5    17 ms    17 ms    17 ms  195.99.125.140
  6    19 ms    17 ms    17 ms  peer2-et-1-1-0.redbus.ukcore.bt.net [62.172.103.47]
  7    18 ms    18 ms    18 ms  195.99.126.209
  8    17 ms    17 ms    17 ms  a23-198-73-73.deploy.static.akamaitechnologies.com [23.198.73.73]

Trace complete.

This one is Blizzards Overwatch server in Europe (I believe).   I'm getting intermittent connection issues (will sometimes connect to a game, sometimes won't).

C:\Users\Jonty>tracert 185.60.112.157

Tracing route to 185.60.112.157 over a maximum of 30 hops

  1    <1 ms     1 ms     1 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    17 ms    17 ms    17 ms  be3-3100.pcn-ir01.plus.net [195.166.143.128]
  5    17 ms    18 ms    17 ms  core1-BE1.colindale.ukcore.bt.net [195.99.125.132]
  6    18 ms    19 ms    18 ms  195.99.127.36
  7    18 ms    17 ms    17 ms  213.137.183.36
  8    24 ms    24 ms    24 ms  t2c3-xe-0-0-1-0.nl-ams2.eu.bt.net [166.49.208.214]
  9     *        *        *     Request timed out.
 10    26 ms    27 ms    28 ms  37.244.10.33
 11    25 ms    25 ms    26 ms  185.60.112.157

Tried Xbox Live on the 360 today.... Still the same... Been this way since Saturday.  It told me today that there was an MTU issue (but I think that's rubbish, as a ping -f -l 1464 works fine). If i retry it, open all the ports, turn off the firewall, put it on the DMZ, give it the public IP (i.e. anything at all) I get a failure message of one description or another.

For the record... My IP address is 51.6.something.something!

[#3]

Tracing route to star-mini.c10r.facebook.com [31.13.90.36]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 12 ms 12 ms 13 ms 137.hiper04.sheff.dial.plus.net.uk [195.166.143.137]
4 20 ms 15 ms 12 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 13 ms 12 ms 12 ms core1-BE1.southbank.ukcore.bt.net [195.99.125.130]
6 16 ms 11 ms 10 ms peer1-xe-11-0-1.faraday.ukcore.bt.net [213.121.193.201]
7 11 ms 12 ms 11 ms 109.159.253.103
8 * 12 ms 13 ms po102.psw01d.lhr3.tfbnw.net [74.119.79.155]
9 13 ms 13 ms 16 ms 173.252.67.203
10 12 ms 12 ms 12 ms edge-star-mini-shv-01-lhr3.facebook.com [31.13.90.36]

Trace complete.

Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 12 ms 12 ms 12 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 12 ms 12 ms 12 ms gr-11-1-0.ptw-cr02.plus.net [195.166.129.189]
6 10 ms 10 ms 10 ms ae2.ptw-cr01.plus.net [195.166.129.4]
7 13 ms 12 ms 13 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
8 28 ms 23 ms 25 ms gi5-1.peh-cr02.plus.net [84.93.232.61]
9 21 ms 23 ms 25 ms reth1.peh-elbfw.plus.net [84.92.0.103]
10 21 ms 20 ms 21 ms 10.104.0.53
11 20 ms 21 ms 21 ms portal.plus.net [212.159.8.2]

Trace complete.

tracert account.sonyentertainmentnetwork.com

Tracing route to e380.b.akamaiedge.net [104.82.194.93]
over a maximum of 30 hops:

1 <1 ms 2 ms 1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * 15 ms 13 ms 137.hiper04.sheff.dial.plus.net.uk [195.166.143.137]
4 14 ms 12 ms 12 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 13 ms 13 ms 12 ms core1-BE1.southbank.ukcore.bt.net [195.99.125.130]
6 10 ms 10 ms 12 ms 195.99.127.68
7 * 10 ms 10 ms peer1-et-3-3-0.faraday.ukcore.bt.net [62.6.201.165]
8 13 ms 14 ms 11 ms 195.99.126.19
9 14 ms 11 ms 13 ms a104-82-194-93.deploy.static.akamaitechnologies.com [104.82.194.93]

Trace complete.

tracert www.xbox.com

Tracing route to e2537.dspb.akamaiedge.net [23.41.183.97]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * 14 ms 14 ms 141.hiper04.sheff.dial.plus.net.uk [195.166.143.141]
4 12 ms 13 ms 12 ms be3-3106.psb-ir02.plus.net [195.166.143.140]
5 16 ms 15 ms 15 ms 195.99.125.138
6 13 ms 13 ms 12 ms peer1-xe-11-0-1.faraday.ukcore.bt.net [213.121.193.201]
7 16 ms 14 ms 13 ms t2c4-et-3-3-0-0.uk-lon1.eu.bt.net [166.49.211.246]
8 13 ms 13 ms 16 ms 82.112.101.73
9 16 ms 15 ms 15 ms ae-6.r24.londen12.uk.bb.gin.ntt.net [129.250.4.20]
10 82 ms 82 ms 81 ms ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
11 150 ms 212 ms 150 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
12 144 ms 144 ms 144 ms ae-22.r04.sttlwa01.us.bb.gin.ntt.net [129.250.2.8]
13 146 ms 149 ms 146 ms a23-41-183-97.deploy.static.akamaitechnologies.com [23.41.183.97]

Trace complete.

>tracert www.imgur.com

Tracing route to imgur.com [185.31.19.193]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * * 12 ms 141.hiper04.sheff.dial.plus.net.uk [195.166.143.141]
4 10 ms 10 ms 10 ms be3-3106.psb-ir02.plus.net [195.166.143.140]
5 13 ms 13 ms 12 ms 195.99.125.138
6 11 ms 11 ms 15 ms 195.99.127.62
7 17 ms 17 ms 20 ms core1-Te0-4-0-3.ealing.ukcore.bt.net [62.172.103.185]
8 11 ms 11 ms 12 ms host213-121-193-226.ukcore.bt.net [213.121.193.226]
9 13 ms 14 ms 13 ms 213.137.183.17
10 12 ms 12 ms 14 ms ldn-b3-link.telia.net [213.248.67.97]
11 14 ms 14 ms 14 ms ldn-bb2-link.telia.net [62.115.116.252]
12 11 ms 12 ms 14 ms ldn-b3-link.telia.net [62.115.137.95]
13 * * * Request timed out.
14 13 ms 12 ms 12 ms 185.31.19.193

Trace complete.

All sites I've noticed with unbearable loading times

[#4]

This is from a 209.xx IP

PlayStation Network

tracert vl.api.np.km.playstation.net

Tracing route to us-p1-np-regcam-2129210197.us-west-1.elb.amazonaws.com [52.8.203.59]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        7 ms  137.hiper04.sheff.dial.plus.net.uk [195.166.143.137]
  4     8 ms     9 ms     7 ms  be3-3104.psb-ir01.plus.net [195.166.143.136]
  5     8 ms     7 ms     7 ms  core1-BE1.southbank.ukcore.bt.net [195.99.125.130]
  6    33 ms    11 ms    11 ms  vhsaccess1-pos2-0.faraday.fixed.bt.net [195.99.127.5]
  7     8 ms     7 ms     8 ms  166-49-211-234.eu.bt.net [166.49.211.234]
  8     9 ms     9 ms     9 ms  82.112.101.73
  9     9 ms     8 ms    11 ms  ae-6.r24.londen12.uk.bb.gin.ntt.net [129.250.4.20]
 10    76 ms    76 ms    76 ms  ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
 11   141 ms   141 ms   141 ms  ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
 12   157 ms   142 ms   157 ms  ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
 13   158 ms   157 ms   157 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
 14   165 ms   165 ms   165 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 15   159 ms   158 ms   158 ms  ae-4.r06.plalca01.us.bb.gin.ntt.net [129.250.4.118]
 16   175 ms   163 ms   163 ms  ae-1.amazon.plalca01.us.bb.gin.ntt.net [140.174.21.182]
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19   162 ms   162 ms   163 ms  72.21.222.19
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

 portal.plus.net [212.159.8.2]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     7 ms     7 ms     7 ms  be3-3104.psb-ir01.plus.net [195.166.143.136]
  5     7 ms     8 ms     8 ms  gr-11-1-0.ptw-cr02.plus.net [195.166.129.189]
  6     7 ms     7 ms     7 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  7     8 ms     7 ms     8 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
  8    21 ms    18 ms    19 ms  gi5-1.peh-cr02.plus.net [84.93.232.61]
  9    18 ms    22 ms    18 ms  reth1.peh-elbfw.plus.net [84.92.0.103]
 10    19 ms    18 ms    17 ms  10.104.0.53
 11    18 ms    19 ms    18 ms  portal.plus.net [212.159.8.2]

Still dropping or 700ms+ pings.

[#5]

Still no difference, timing out as usual. Can't upload anything to Gyazo or Discord.

Haven't even tried my PS4 but I imagine it's just going to have difficulties. Tried playing some Overwatch to no avail, just disconnect issues and then taking an infinite amount of time to matchmake.

Getting a bit annoying now. What's the situation/status?

[#6]

So I bit the bullet and spent the £5 on a Static IP (starting in 81.)

Problem with the Xbox that's been bugging me since Saturday immediately cleared.

Going to play a few rounds of Overwatch and see if that's also fixed.

[#7]

@Jonty303 How did you do it through the member centre? does it let you choose the range you want?

[#8]

This is very interesting - I was told today I could not have a static IP assigned to me and the only way to do it was to keep rebooting the router until I got assigned a non 51.6. IP and then it would be assigned, and that if this happened given the issues I would get it for free.

I found it odd I could not be assigned one, but was told that was how it worked.....

As it goes, when I tried, every time I rebooted I still got assigned a 51.6 IP address and so they told me I couldn't get a static.

I think I am just going to ring and cancel tomorrow. Been told I can leave termination fee free. Can't be bothered with the chew on and inconsistencies. The girl helping me has been great but can only go on what she is being told and that's basically that they don't know what is causing it or how long it will take to fix.

[#9]

@B33Dee It is possible to get a static ip if your package is one of their current ones and not an old product it costs £5. I asked about it today but they say changing ip to static might not fix the problem. You can do it yourself i think by logging into members centre and then selecting addons across the top bar.

[#10]

I'm not going to pay Plusnet for a workaround to a problem Plusnet have caused, if the static IP is fixing the issue they should be offering it to all affected customers for free until this issue is fixed.

[#11]

Yeah I've just noticed it in there. I don't really want to pay for something when I shouldn't have to in order to fix a problem. 

I've only been with plusnet 8 weeks but already had more issues than I did in 2 years with BT, which given it is the parent company and are meant to have a bad rep is saying something.

I am still not convinced my speeds are right either. I got capped at 20 down when I bought the fibre extra. Upload is still capped at 10 and I am sure it is meant to be 20?

Coupled with this, and the patronising idiot I spoke to on live chat (called John) the other day, it's just pushing me back to BT to be honest.

[#12]

@nightstalk3r ive thought about paying for one just so we can actually use our sky box but not going to as agree why should we pay extra for something just to work around the problem. I must say plusnet have been pretty rubbish in dealing with this problem they haven't even put in on the network status page when it is clearly an on-going fault. The person i spoke to today said they have no timeframe while in the mean time i can't access other services im paying for.

[#13]

I agree it's bad about it not being on the status page when clearly it is a major problem.

It has taken a week for them to even admit to it being a major issue and it's been like they have been hiding away from it for all that time. I was actually told by "John" that "It's not a fault on our network "per se" ".....Hmmmmmm. I think John needs to learn how to tell the truth.

[#14]

Hate to say it..... Everything OKnow I'm on the Static.  No problems on Overwatch.  Xbox is sorted.  Etc. 

Agree that you shouldn't have to pay for your own fix.  It's a bit pony. 

[#15]

I heard on Blizzard's forums that people on iiNet were having issues with Overwatch, so I came over here to see.

I've tried rebooting my router many times and I can't seem to get off the (51) IP address.

I honestly thought it had to do with a bug in chrome with those DNS errors, since I might've touched something, but after Overwatch problems and not allowing to join teamspeak servers then it couldn't be me.