Trade servers are undergoing maintenance. Some features will be unavailable.
Path of Exile 2: Failed to connect to instance (With MTR)
|
I've been having this issue all day whenever I choose a character and try to load into an area. After following the entirety of the Greneral Troubleshooting Guide, (https://www.pathofexile.com/forum/view-thread/3072628) and finding no solutions, I tried using MTR to test the network. There seems to be a large amount a packet loss at the 3rd hop from the provided URL, but may just be ICMP deprioritization. There's 1% packet loss at 10.8.129.1 which have something to do with my ISP, but there doesn't seem to be any in any area I have direct control over, so I don't know if there's anything I can do to fix it. I guess I'll try calling my ISP tomorrow.
MTR logs: https://pastebin.com/9WgA26YA Last bumped on Dec 31, 2024, 9:39:25 PM
|
|
|
Ah, a fellow Linux user. Howdy!
The only issue I’m seeing is ~0.6% packet loss beginning on hop 6. Who’s your ISP? Wisprenn / Cogent? Roughly what proportion of instance transitions throw you that error message? "VPs are not required to change their posting style. They are still welcome to express their opinions and take part in any discussions they wish. Their only responsibility is to continue doing what they have always done - posting in a friendly and constructive manner."
-GGG, 2015 |
|
" Correct, it's Wisprenn. " Between 75% and 90%. I get this error both when attempting to load the map I was in previously and whenever I try to leave it, such as with a portal or waypoint. |
|
|
ISP tech support can't really do anything about the issue. They can't see any problems on their end. Gonna try proton VPN later to see if that helps anything. If anyone has any other suggestions, I'll give them a try.
|
|
|
I use Proton & like them a lot.
If you’ll forgive a silly question - have you tried changing gateway? As the issue is on-route, changing destination may well result in changing route & therefore no longer having the issue. The slight increase in latency caused by connecting to a data centre that’s further away would likely be a good trade off - particularly as any VPN is likely to itself worsen your latency. "VPs are not required to change their posting style. They are still welcome to express their opinions and take part in any discussions they wish. Their only responsibility is to continue doing what they have always done - posting in a friendly and constructive manner."
-GGG, 2015 |
|
" I've tried California, Texas, Washington. They all had the same issue. pacman is running pretty slow right now, so I've yet to try the VPN. |
|
|
Update: I tried proton VPN over the last few days and it did get around the "Failed to connect to instance" error. Today I tried playing without Proton VPN and it was working fine, so good for me I guess. No idea why it was having problems a few days ago but it's apparently working now.
|
|
