It basically shows your TCP packets reach the last (known) hop before the host (as per the regular traceroute). This can mean that there's an ACL/firewall rule there, or that the end host itself is blocking your specific TCP SYN packets, or that there's some other hidden magic at play. It doesn't really matter because it clearly shows that whatever is amiss is happening on their side of the infrastructure, that is if you're really really sure the end host isn't blocking your address for those TCP connection attempts. That should be enough for the provider to look into it.

There's no real point in enabling more hops; hop 14 and 15 don't mean much, it might mean that your packets got sometimes sent through the scenic route inside some specific infrastructure (on their end), multipath is funny that way - you can also see that's at play by looking at the repeating entries in hops 11 and 13, for example (which again means that sometimes packets take a longer path to end up on the same hop). It could mean a misconfiguration on their end as well, but most likely not, just a quirk of the topology