The TMNet Route Object is of no interest. It's the wider network block that the machine you're worried about is located in. The 203.106.85.67 is a host in the 203.106.85.0 - 203.106.85.255 network range, which itself is located in a larger network address range that TM happen to refer to as "TMnet route object". They could have called it "Purple Leaping Durian" just as meaningfully. Nobody, except maybe a few people at TM, knows what "TMnet route object" means, and maybe they've even forgotten at TM. You're looking at the wrong information. I don't why the word 'Acer' appears in the whois report, but then again, it's a free-format name, so perhaps we shouldn't have read so much into it.

On the Internet, nobody knows your local IP address. Your router 'pretends' to originate all traffic from your LAN, assigning a new port each time it gets some traffic from the LAN, and sending out network packets from that port on its WAN interface. This is Network Address Translation (NAT). When the reply comes back, it comes back to the same port on the router it left from. The router uses the port to remember which LAN host the packet originally came from and forwards the packet to that LAN host. Whatismyip can only tell you what your router's IP address is.

From your description of what's happening, it sounds like a proxy cache. Use cURL:

It's an Akamai GHost server. No need for paranoia, unless you fear Akamai.