I recently moved and this more than likely is an issue with my ISP but i will see if there is anything else i can do to try to fix this issue
Over the last 3 months since i have moved i have been getting random transfer aborted instance not found. Leading me to think it’s a traceroute issue. But i don’t know which server it’s connecting to. this mainly happens during dungeon finder and once when i was joining a pug raid.
Things i have done
FLushed DNS
reset router and modem : factor reset router. Pushed updates and without updates. Checked fire walls and permissions
Changed DNS
Checked firewall settings
my last bet is to call my ISP but without an IP to do a trace route i’m unsure how i am going to get them to acknowledge an issue or if there is even an issue.
to sum it up… i get transfer aborted instance not found randomly when doing LFG. not every time maybe 1/3 of the time. my ping is fine and i don’t have other issues. I have followed all guides to solve this issue.
I’m having the exact same issue. I’ll join an LFG for M+ or a raid, or even sign up for LFR and accept the queue, only to be told “Transfer Aborted: instance not found.” Most of the time, I’m able to leave the group and then proceed to zone in to where we were going immediately, and I’ve also followed the troubleshooting steps and nothing seems to fix it.
The party leader determines the server you’re playing on. So if you get the server name and reference the list at WarcraftWiki, you can tell which one it is. This list incorrectly specifies Los Angeles as the West Coast server, but it’s actually located in Las Vegas these days.
To bring this back up, I was able to find a server OCE that i wasn’t able to join an instance group. I ran a trace route. jumps 17-30 return Timed out. which from my understanding can just mean the host does not allow ping times to be sent back. But the trace just ends with saying complete but does not show the final destination. Would this be a ISP issue?
Complete just means the test is over, not that data made it to the destination. Hard to say. What are the hops where it starts timing out? Does it have your ISP name on them?
To update the issue, my ISP was able to attempt the same trace route and it seems that the signal is being routed into South Korea into what they called a server thats been black listed. once it reaches that IP it dies and we get no more pings or return signal.
If they are routing you through a server they also blacklisted, then you’d need to work with them on changing the route. Never heard of this issue before.
The issue is they don’t have it black listed but the server pulls up on a list of black listed servers. but i live in a smaller town with a smaller isp so who ever handles the hand off up stream is how i’m going to change this. it’s frustrating.
Just to figure this out maybe a bit more. my trace route get’s to a 182.162.152.158 IP location korea then times out from there.