canadian poe server problem

"

Drakier a écrit :

"

Ascendic a écrit :

100% loss is usually due to the host not responding to ICMP traffic (like pings) not that the host is down.

That is correct... as long as the host itself was failed to resolve properly. If you have a VALID address and still get 100% loss, then there might be a different issue... if you get 100% loss on a node and it fails to resolve, then that is likely the reason.

As a side-note, I heard there were some backbone issues affecting traffic from Canada as well as possibly the east coast of the US. Not sure how accurate that is, but I would suspect as wide-spread as the problem is, that it is likely.

Hope it gets resolved soon either way.

Good luck.

That is not true. You do not use ICMP traffic to resolve a host so the fact is resolves is irrelevant to whether or not you should be able to ping it. A host also does not have to be online to resolve properly. Many hosts in the ISP world do not respond to ICMP traffic.

As for your second note, it is also not that likely considering the host with the issue is the first hop (after the users router). This would be the users ISP gateway typically and if that was down the user would not be able to complete the route and would have no internet at all.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 561 | 561 | 0 | 0 | 10 | 0 |
| No response from host - 100 | 112 | 0 | 0 | 0 | 0 | 0 |
| 10.170.172.57 - 0 | 561 | 561 | 7 | 11 | 36 | 9 |
| 216.113.122.149 - 1 | 549 | 546 | 0 | 11 | 36 | 10 |
| 216.113.124.142 - 0 | 561 | 561 | 21 | 25 | 40 | 23 |
| te3-5.bbr01.eq01.wdc01.networklayer.com - 0 | 561 | 561 | 20 | 23 | 82 | 22 |
| ae0.bbr01.tl01.atl01.networklayer.com - 0 | 561 | 561 | 32 | 35 | 210 | 34 |
| ae13.bbr02.eq01.dal03.networklayer.com - 4 | 489 | 471 | 50 | 68 | 178 | 51 |
| ae1.dar02.sr01.dal01.networklayer.com - 4 | 493 | 476 | 50 | 69 | 166 | 51 |
| po2.fcr05.sr06.dal01.networklayer.com - 1 | 553 | 551 | 0 | 53 | 205 | 52 |
|173.192.44.22-static.reverse.softlayer.com - 4 | 489 | 471 | 0 | 67 | 168 | 53 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider




Unplayable since more than 6 hours i'd say.
Multiple reddit posts about it.

ISP is Videotron, LTÉE // Quebec, Canada.

Couldn't level my Beyond character today it seems...

I hate how I can't play the game properly because if I want to even think about leveling I need to do high level zones in beyond hardcore. With these spikes I can't safely do that because any latency spike could kill me

Getting this issue as well on the NA server; now I've started connecting to a VPN in Sweden so PoE connects me to the European server instead. Stuck playing with 200 ping, but it seems to have resolved the spiking issue =/

This is getting out of hand, people from all over the the country and world are complaining about the lag on reddit and global chat. This is a server issue and something has been changed with the new patch that is causing this game to be un-playable. I was very excited to come back to the new patch but I'm thoroughly disappointed that I cannot enjoy the new content without freezing for 10-30s every couple of minutes.

http://map.ipviking.com/

It's called China.

Downtown toronto telus internet here... just lost my beyond character at about 2:25 am because of those nonsense. Why did i even make a character on this league....

Having this issue as well. Playing from the west coast of Canada.

Issues seemed to start at about 3-4pm PDT this afternoon (Aug 22nd), and have persisted all evening.

Let's be clear about something, though: when the new "b" patch launched, there were no lag problems then. It was at least a dozen hours after the patch launched before lag started to occur. Unless there is some time sensitive fault in the patch, then it isn't likely that's the cause of this.