That should be the public IP address assigned to your router by Viasat. When I tracert to my public IP it's 1 hop and takes 1 millisecond as I would expect it to - my computer to my router (same as if I were to use my router's private address 192.168.1.1.
Even with a tracert to your IP address I get an expected result:
From my computer to my router then 3 hops over private network addresses (routers) belonging to Viasat (there's no real need to venture outside of their private infrastructure I guess) and then on to your IP address. Not surprising it took twice the time to reach your IP - up to satellite and back down again from where I sit with two satellite round trips required ;)
It could be that your router is not configured to respond to tracert commands, I suppose but then I wouldn't be able to do it remotely I would hope.
FWIW, the actual tracert result may provide some insight. It may not be 30 hops but simply 30 retries with no response to the ICMP commands used and bumping the TTL on each attempt.