Connection problems with World of Warcraft

[#1]

---

@F1D wrote:

I really do think someone from PlusNet needs to respond to this chain, I can't see anything already...

I strongly suspect it's part of this problem.

---

[#2]

bobpullen most of the thread your pointing to is written in technical jargon, could you possibly summarize the issue here for those of us who would prefer their technology to just work?

[#3]

@bobpullen

Hmmm... I had a quick read through of the most recent pages in that thread I'm not sure there is any mention of a solution aside from the fact a static IP seems to fix everything - is PlusNet investigating from that angle do we know? Surely whatever is potentially causing things to be great that way should give a hint. I'm so tempted to spend the money to get one just so I can play WoW without the constant timing out/instance errors but don't see that I should spend the extra fiver a month for that, especially when PlusNet were before so so great at fixing issues.

Not sure how long the other thread has been going on (I'd imagine a while because of all the pages), I've been having issues with WoW for at least the last month.

[#4]

@F1D the £5 for a static IP address is a one-off charge, not monthly.

[#5]

@Browni Oh is it... didn't know that. Maybe it might be worth it then to see if that helps things.

[#6]

NO ONE should be forced to pay Extra   to fix a problem PN should fix it or put everyone on fixed IP free

[#7]

---

@rongtw wrote:

NO ONE should be forced to pay Extra   to fix a problem PN should fix it or put everyone on fixed IP free

---

exactly, their response doesn't fill me with hope... and since some users have reported issues even after paying for a static IP, it can be said that it isn't a fix that works for everyone

still seeing problems with WoW today, endless loading screens, transfer aborted, the usual...

[#8]

Same sort of issue here as well guys with WoW.

Do we really need to have a static ip for a cure ?? It's been fine all summer.

[#9]

---

@30FTTC06 wrote:

Same sort of issue here as well guys with WoW.

Do we really need to have a static ip for a cure ?? It's been fine all summer.

---

works for some, not for others, you decide if you're willing to drop a fiver for something plusnet should do for free

the problem is with their new network, it's not playing nice with wow traffic... no other ISP has this problem

[#10]

@KS25 I would not be happy with a static ip in all honesty, never mind a fiver for a fix!

[#11]

Plusnet's migration to a new network is not going well. I've noticed packet loss and severe latency problems over the last 3 or 4 weeks, and these get worse during periods of heavy traffic, particularly around late afternoon/evening. I'm not surprised gamers are frustrated - it's bad enough just browsing and attempting to download mail. I've identified a router on PN's network, which is routinely droping 75% of routed packets. All of my traffic goes through this router, so I'm stuffed, but I suspect there are a number of other routers all doing the same thing - hence the numbers complaining. Take a look at the image attached. Plusnet, please fix this quickly or your customers will start to leave in droves!

[#12]

That router dropping packets is not a problem. It's intentional.

We think the WoW issues are due to the problem being discussed in the lengthy thread I linked to in my last post. It's being investigated as a priority.

Sorry it's causing so much pain ☹️

[#13]

more frustration than pain, but eh

do you have some sort of progress update? this has been going on for weeks and plusnet only started investigating it a short while ago... quite a shoddy response so far

Moderator's note by Dick (Strat): Full quote of preceding post removed as per Forum rules

[#14]

Seems fair to me now I've changed over to a static ip.

 1  192.168.0.254                                            0.942 ms  0.539 ms  0.528 ms
 2  lo0.10.central10.ptw-bng01.plus.net (195.166.128.170)    8.431 ms  8.701 ms  9.343 ms
 3  irb.10.PTW-CR01.plus.net (84.93.249.1)                   8.498 ms  11.250 ms  8.688 ms
 4  195.99.126.138                                           8.561 ms  8.872 ms  8.377 ms
 5  core3-te0-0-0-14.faraday.ukcore.bt.net (213.121.193.160) 9.574 ms  9.778 ms  8.625 ms
 6  213.137.183.36                                           9.394 ms  8.712 ms  9.216 ms
 7  t2c3-xe-0-0-1-0.nl-ams2.eu.bt.net (166.49.208.214)      15.640 ms  15.607 ms  15.899 ms
 8  * * *
 9  37.244.10.35                                            18.670 ms  18.291 ms  17.419 ms
10  37.244.10.103                                           17.993 ms  17.378 ms  17.980 ms
11  185.60.114.153                                          16.797 ms  16.963 ms  16.714 ms
12  185.60.112.157                                          16.815 ms  17.156 ms  17.243 ms

I think in light of this issue being caused by plusnet, the very least plusnet can do is refund the £5 and re-put me back to a dynamic ip ASAP.

[#15]

Why would the dropping of packets be intentional?!