Exactly as I suspected…. When the route goes through Switzerland to China, then it bounces through the United States, the connection works just fine...
When the route tries to run through the 3bb platform most of the way, it seems it chokes.... This confirms what I suspected, and actually makes me think that the technician doesn't know what they're doing :lolp:
What I find interesting is this part of the one traceroute where it does not work
8 34 ms 37 ms 33 ms mx-ll-110.164.1-6.static.3bb.co.th [110.164.1.6]
9 226 ms 226 ms 226 ms 192.168.255.250
The interesting part is to see if the internal LAN IP that you're reaching where the ping suddenly spikes is on 3bb's end, or if this is an obscure private link between 3bb and nForce that isn't working correctly. Based on the sudden spike in the ping between the two, I'm willing to put money down that says that this is where the connection drops when it fails. If this internal hop is between 3bb and nForce, this may explain why 3bb is saying that the problem is with GT.ru because they're only looking at the packets as they pass through the 3bb network. This definitely does confirm my theory that it's an aggregated network that uses dynamic routing. If they were smart, what they would do is to pull the dynamic route that runs primarily through their platform, since there's obviously a disconnect somewhere between 3bb and nForce when they route traffic this way. 
So… It's possible that the packet leaves the 3bb network successfully, but chokes between 3bb and nForce, in which case it would only make sense that 3bb is scratching their heads, because they're completely overlooking a major routing issue. The internal 192.168.x.x IP address is also of some concern as generally speaking, you're not supposed to have private network addresses along a route, unless the route is accessible through your network directly. This is to ensure that you're able to successfully ping and route through that gateway, which leads me to believe that the problem is in fact within 3bb's network, namely in one of their exit nodes that passes traffic out to one of their internet exchanges. If this is the case, then the problem is on 3bb's end because it's one of their own internal exit nodes that is failing. This will no doubt create major routing issues for more than just GT.ru. Come to think of it, it's likely that this internal link is indeed a 3bb link, in which case they're just full of shit and don't want to fix their own platform. I know that latency will vary slightly from one hop to the next, but with a difference in latency like that (spiking from 34 to 226 ms) is generally an indication that either there is a hardware issue with the link, or that said link may be over-saturated with network traffic, in which case, their load balancing is not properly configured.
I'd be inclined to start asking questions about that route myself as the sudden spike in latency is definitely something that shouldn't be happening. Since the problem seems to be with one of the dynamic routes that they're taking, this would explain why a VPN makes it work, as this forces traffic to take a different route, thus bypassing the particular gateway (or node) in the 3bb network that links into the internet exchange to hop over from Thailand to the Netherlands. While the traceroute may be able to make its way through to nForce, I kind of wonder if the larger packets such as would be used for HTTP traffic are too large to be able to pass through, due to whatever is causing the latency to spike at that point in the connection. The other thing that I find interesting is that on two separate routes, there's a ping timeout when the connection routes through China, which leads me to believe that there may be an intermittent problem on that end of the platform when it runs through the Nine network. One thing that I can say for sure though is that there is definitely dynamic routing in place here, which explains why it works sometimes with 3bb, but not others, depending on whether or not it takes the route through the faulty link at the end of 3bb's platform.