All brazilian players from a huge ISP are having the same "Failed to connect to instance" problem
Hello
Most players that use one of the bigest ISPs in Brazil are having the "Failed to connect to instance" issue. The ISP is "VIVO". It is probably only affecting players using optical fiber. If it helps: WinMTR to br.login.pathofexile.com
Spoiler
|------------------------------------------------------------------------------------------|
| WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | mymodem - 0 | 271 | 271 | 0 | 0 | 1 | 1 | | No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 | | 187-100-40-49.dsl.telesp.net.br - 0 | 271 | 271 | 1 | 4 | 40 | 3 | | 187-100-83-188.dsl.telesp.net.br - 0 | 271 | 271 | 1 | 4 | 30 | 3 | | 187-100-34-129.dsl.telesp.net.br - 0 | 271 | 271 | 2 | 4 | 37 | 2 | |et-0-1-0-100-grtsanem4.net.telefonicaglobalsolutions.com - 0 | 271 | 271 | 2 | 5 | 75 | 3 | |te0-2-1-0-grasaoeq1.net.telefonicaglobalsolutions.com - 0 | 271 | 271 | 5 | 7 | 18 | 5 | | No response from host - 100 | 54 | 0 | 0 | 0 | 0 | 0 | | ae6.dar02.sao01.networklayer.com - 0 | 271 | 271 | 19 | 23 | 47 | 24 | | po2.fcr01b.sao01.networklayer.com - 1 | 267 | 266 | 6 | 8 | 33 | 9 | | 36.84.39a9.ip4.static.sl-reverse.com - 0 | 271 | 271 | 18 | 23 | 55 | 25 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider WinMTR to 169.57.132.54 (based on instance IP from log files)
Spoiler
Log: 2016/06/28 19:49:26 279853625 d1 [INFO Client 8708] Connecting to instance server at 169.57.132.54:6112 2016/06/28 19:49:47 279874625 11e [DEBUG Client 8708] Connect time to instance server was 21000ms WinMTR: |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | mymodem - 0 | 361 | 361 | 0 | 1 | 21 | 0 | | No response from host - 100 | 72 | 0 | 0 | 0 | 0 | 0 | | 187-100-40-49.dsl.telesp.net.br - 0 | 360 | 360 | 1 | 4 | 33 | 4 | | 187-100-83-188.dsl.telesp.net.br - 0 | 360 | 360 | 1 | 4 | 27 | 5 | | 187-100-34-129.dsl.telesp.net.br - 0 | 360 | 360 | 1 | 5 | 38 | 16 | |et-0-1-0-100-grtsanem4.net.telefonicaglobalsolutions.com - 0 | 360 | 360 | 2 | 6 | 78 | 3 | |te0-2-1-0-grasaoeq1.net.telefonicaglobalsolutions.com - 0 | 360 | 360 | 5 | 7 | 11 | 6 | | No response from host - 100 | 72 | 0 | 0 | 0 | 0 | 0 | | ae6.dar02.sao01.networklayer.com - 0 | 360 | 360 | 18 | 23 | 38 | 25 | | po2.fcr01b.sao01.networklayer.com - 3 | 333 | 326 | 6 | 8 | 33 | 10 | | 36.84.39a9.ip4.static.sl-reverse.com - 0 | 360 | 360 | 15 | 23 | 28 | 22 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider WinMTR to 169.57.132.59 (based on instance IP from log files)
Spoiler
Log: 2016/06/28 19:57:20 280327406 d1 [INFO Client 8708] Connecting to instance server at 169.57.132.59:6112 2016/06/28 19:57:41 280348421 11e [DEBUG Client 8708] Connect time to instance server was 21000ms WinMTR: |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | mymodem - 0 | 81 | 81 | 0 | 1 | 14 | 1 | | No response from host - 100 | 16 | 0 | 0 | 0 | 0 | 0 | | 187-100-84-148.dsl.telesp.net.br - 0 | 81 | 81 | 1 | 4 | 27 | 4 | | 187-100-78-221.dsl.telesp.net.br - 0 | 81 | 81 | 1 | 5 | 29 | 3 | | 187-100-34-153.dsl.telesp.net.br - 0 | 81 | 81 | 2 | 4 | 25 | 6 | |grtsanem4-et-2-1-0-100-telesp.net.telefonicaglobalsolutions.com - 0 | 81 | 81 | 3 | 5 | 14 | 6 | |te0-2-1-0-grasaoeq1.net.telefonicaglobalsolutions.com - 0 | 81 | 81 | 5 | 7 | 10 | 9 | | No response from host - 100 | 16 | 0 | 0 | 0 | 0 | 0 | | ae6.dar02.sao01.networklayer.com - 0 | 81 | 81 | 19 | 23 | 34 | 25 | | No response from host - 100 | 16 | 0 | 0 | 0 | 0 | 0 | | 3b.84.39a9.ip4.static.sl-reverse.com - 0 | 81 | 81 | 17 | 22 | 27 | 26 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider IGN: vieira Last bumped on Jul 2, 2016, 1:25:37 AM
|
|
bump.
same problem, same isp (fiber aswell). Game's been unplayable for the last 3 days. |
|
Thanks for figuring out it's limited to Vivo fiber service.
I'll leave a copy of my own info for support convenience:
Spoiler
My thread: https://www.pathofexile.com/forum/view-thread/1693493 Error: http://i.imgur.com/lqoeqcD.jpg Video footage: https://youtu.be/4XDPuHJkUJY Trace: http://pastebin.com/6nBgDxGM Log: " |
|
Its is no limited to VIVO fiber service, im from Maranhão, where we don't have VIVO, and im getting the same problem.
|
|
Its limited to Vivo (which includes former GVT users, like me), some specific route they use.
I don't know if theres a way for GGG to fix it, considering how garbage (even though its one of the largest) Vivo services are. I had it once before with another ISP and had to wait it out, took over 2 weeks. Its been almost 1 week now that I can't play because of this error. Shame. Shame. Shame.... |
|
It's not only Fiber customers that are being affected, I've speedy (line) and I'm having the same issue, and it's Vivo fault, as always.
Well, had to paid a 1 month subscription to play with WTFast and it's working perfectly now, sad to have such poor internet provider in our country... |
|
I was under the impression I've seen players from other countries complaining about the same issue, so I don't know if it is necessarily a problem with vivo.
|
|
Same problem here, vivo is fcking GARBAGE.
I am testing wtfast and it seems to be working. |
|
use the texas server instead of the sp server
be sure not to try to enter any old instances you created in sp (hideout, maps, etc), if needed just wait until they expire before logging to texas |
|
" We all know that. It's pretty obvious that if I make a thread telling about a problem in a route to the brazilian gateway, I know that if I change the gateway i won't have that issue. You are helping nothing at all. IGN: vieira
|
|