A few thoughts.
I think we can safely rule out local (client-side) internet connections, software or hardware issues.
It is clear that this issue is repeatedly affecting some users while others are unaffected. Also, this is a new issue since the world 4 update.
Sometimes when playing I have gone for an hour or two without issue. Lately I am only able to connect for 1-5 minutes and then disconnected for 1-2 minutes.
Others in my group are totally unaffected. Sometimes if I log back in fast enough I am able to stay "in-party", usually I need to be invited to party again. They told me that my body is still sitting in the world and it appears idle.
Maybe there was some change to the server side code.
Maybe there is routing issue? Possibly higher in the network infrastructure that is outside of your control. There may be priority access due to high traffic for certain ISPs or countries.
Is it possible to switch the website to a different server? There are many free hosts to choose from. This will increase capacity, latency, and server resources regardless of this issue.
Here is my tracert during a disconnection and a solid connection.
Tracing route to moltke.seatribe.se [178.63.100.209]
over a maximum of 30 hops:
1 151 ms 144 ms 47 ms h254.s98.ts.hinet.net [168.95.98.254]
2 241 ms 67 ms 137 ms TPN2-3301.hinet.net [168.95.162.86]
3 195 ms 34 ms 56 ms TPDT-3011.hinet.net [220.128.3.122]
4 36 ms 38 ms 53 ms r4102-s2.tp.hinet.net [220.128.7.145]
5 58 ms 24 ms 17 ms 220-128-7-13.HINET-IP.hinet.net [220.128.7.13]
6 156 ms 147 ms 297 ms r02-pa.us.hinet.net [211.72.108.221]
7 242 ms 234 ms 269 ms r01-pa.us.hinet.net [202.39.83.2]
8 217 ms 399 ms 227 ms pa-c6r1.USA-PAIX.router.hinet.net [202.39.83.181
]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 ^C
C:\Users\user>tracert
www.havenandhearth.comTracing route to moltke.seatribe.se [178.63.100.209]
over a maximum of 30 hops:
1 145 ms 23 ms 21 ms h254.s98.ts.hinet.net [168.95.98.254]
2 139 ms 66 ms 24 ms TPN2-3301.hinet.net [168.95.162.86]
3 50 ms 39 ms 45 ms TPDT-3011.hinet.net [220.128.3.122]
4 87 ms 44 ms 147 ms r4102-s2.tp.hinet.net [220.128.7.145]
5 150 ms 111 ms 41 ms 220-128-7-13.HINET-IP.hinet.net [220.128.7.13]
6 148 ms 325 ms 169 ms r02-pa.us.hinet.net [211.72.108.221]
7 172 ms 148 ms 146 ms r01-pa.us.hinet.net [202.39.83.2]
8 306 ms 262 ms 246 ms pa-c6r1.USA-PAIX.router.hinet.net [202.39.83.181
]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * 299 ms r1fra1.core.init7.net [77.109.135.34]
12 317 ms 298 ms 298 ms gw-hetzner.init7.net [77.109.135.18]
13 378 ms 305 ms 308 ms hos-bb1.juniper2.fs.hetzner.de [213.239.240.243]
14 442 ms 452 ms 302 ms hos-tr4.ex3k15.rz12.hetzner.de [213.239.228.240]
15 325 ms 401 ms 308 ms moltke.seatribe.se [178.63.100.209]
Trace complete.
C:\Users\user>tracert
www.havenandhearth.comTracing route to moltke.seatribe.se [178.63.100.209]
over a maximum of 30 hops:
1 78 ms 53 ms 30 ms h254.s98.ts.hinet.net [168.95.98.254]
2 33 ms 162 ms 213 ms TPN2-3301.hinet.net [168.95.162.86]
3 19 ms 51 ms 101 ms TPDT-3011.hinet.net [220.128.3.122]
4 97 ms 30 ms 27 ms r4102-s2.tp.hinet.net [220.128.7.145]
5 27 ms 28 ms 38 ms 220-128-7-13.HINET-IP.hinet.net [220.128.7.13]
6 170 ms 183 ms 183 ms r02-pa.us.hinet.net [211.72.108.221]
7 173 ms 273 ms 145 ms r01-pa.us.hinet.net [202.39.83.2]
8 386 ms 212 ms 342 ms pa-c6r1.USA-PAIX.router.hinet.net [202.39.83.181
]
9 213 ms 367 ms 375 ms r1.nyiix.init7.net [198.32.160.103]
10 382 ms 282 ms 341 ms r1lon1.core.init7.net [77.109.140.193]
11 479 ms 298 ms 332 ms r1fra1.core.init7.net [77.109.135.34]
12 345 ms 402 ms 298 ms gw-hetzner.init7.net [77.109.135.18]
13 444 ms 454 ms 319 ms hos-bb1.juniper2.fs.hetzner.de [213.239.240.243]
14 309 ms 306 ms 351 ms hos-tr4.ex3k15.rz12.hetzner.de [213.239.228.240]
15 333 ms 302 ms 446 ms moltke.seatribe.se [178.63.100.209]
Trace complete.
Just trying to get the ball rolling. Other ideas?