Disconnections from Destiny on PS4- Router at fault

[#1]

I have a 209.xx Ip and the latency is painfully bad, and I really don't want a static IP.

[#2]

I should have said that I play destiny on xb1

maybe they can change it to a 212 and not make it static? Best to ask the tech support if this is possible.

All I know something is interfering with destiny and elite dangerous on xb1 when trying to connect multiplayers

sorry that I couldn't help more.

[#3]

The only difference in having a static ip is that it will never change, generally your dynamic ip doesn't change, if you leave your router on all the time your ip won't change, say if you turn it of overnight it might change but generally your ip doesn't change unless your isp has to swap you onto a different range.

Best thing to do is either call or go onto live chat, live chat I find is quicker to get through, anyway just ask if they can swap you onto a different range, tell them what you have read on the forums even copy and paste the info in. Restart your router and see if it works.

I'm just a very impatient network engineer and having a static IP doesn't really bother me and solved my issue quicker then going through tech support

[#4]

I tried a wired connection between my PS4 and the router last night and the Destiny disconnections are still occurring.4 times in about 2 hours. I'm still getting error code Beetle. My PS4 is in the DMZ.

Starting to get fed up with this. All of my other Destiny friends from the UK are connecting fine and none of them are with Plusnet.

Going to try port forwarding and then raising a ticket. If this carries on I'll have to move to another ISP when my contract runs out

[#5]

I told you so.

It wont make a difference, its a routing issue to PSN.

Look at this terrible routing:

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

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

  1     6 ms     1 ms     2 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     8 ms    10 ms     8 ms  be3-3106.psb-ir02.plus.net [195.166.143.140]
  5     9 ms    11 ms     9 ms  195.99.125.138
  6    10 ms     9 ms    11 ms  peer1-xe-11-0-1.faraday.ukcore.bt.net [213.121.193.201]
  7    12 ms    24 ms     9 ms  t2c4-et-8-3-0-0.uk-lon1.eu.bt.net [166.49.211.250]
  8    10 ms    10 ms    12 ms  82.112.101.73
  9    10 ms    11 ms     9 ms  ae-6.r24.londen12.uk.bb.gin.ntt.net [129.250.4.20]
 10    82 ms    84 ms    81 ms  ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
 11   173 ms   158 ms   148 ms  ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
 12   148 ms   146 ms   146 ms  ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
 13   163 ms   166 ms   162 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
 14   170 ms   169 ms   169 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 15   163 ms   163 ms   163 ms  ae-4.r06.plalca01.us.bb.gin.ntt.net [129.250.4.118]
 16   168 ms   167 ms   167 ms  ae-1.amazon.plalca01.us.bb.gin.ntt.net [140.174.21.182]
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19   170 ms   169 ms   169 ms  72.21.222.220
 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.

PlayStation uses Amazon Web Services (AWS) EC2 servers to host there services (which isn't unusual as they host close to 22% of the internet). But on the 3rd hop, which shows as timed out we should be seeing a response from Plus Net's very own Sheffield data center however this is not happening. This mean the route our packets are taking is very long and slow, thus we are getting timed out and rejected from host servers.

There is a thread here:

https://community.plus.net/t5/Fibre-Broadband/DNS-Routing-issues-for-the-last-36-hours/td-p/1348275/...

where a lot of people are kicking off from a lack of action or dialogue from Plus net's end.

[#6]

just been on the chat line with plusnet and the person is telling me its a device issues and I should contact Sony support

Really getting narked off now

EDIT

Finally persuaded them to let me log a ticket. Done a tracert too

1 1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 17 ms 16 ms 18 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 18 ms 19 ms 16 ms core1-BE1.southbank.ukcore.bt.net [195.99.125.130]
6 17 ms * 17 ms peer1-xe-11-0-1.faraday.ukcore.bt.net [213.121.193.201]
7 16 ms 16 ms 17 ms t2c4-et-8-1-0-0.uk-lon1.eu.bt.net [166.49.211.248]
8 17 ms 17 ms 16 ms ix-ae-33-0.tcore2.LDN-London.as6453.net [80.231.20.1]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 ix-ae-33-0.tcore2.LDN-London.as6453.net [80.231.20.1] reports: Destination net unreachable.

Trace complete.

[#7]

I changed my DNS settings after signing up to Open DNS and this has fixed the issue.

So its clearly a Plusnet DNS settings issue and to think the chat staff tried to fob me off back to Sony support

[#8]

Did you change your dns setting on your PS or the router?

[#9]

on the router