It seems to show more of the same.....it all depends on what you normally see to google.
It is somewhat surprising you get that much latency to 8.8.8.8. Google duplicates that IP in many places and for most people it is in a large city very close....most times well under 10ms.
Unfortunately when you have so may private IP address in the path it hard to tell which ISP it is running in. My guess would be the 172.18.x.x. where you see the first large jump is your ISP.
The other nastly issue with using trace is it only shows the path to the IP the return path could be very different. ISP tend to keep the traffic on their network as long as possible. So it could your ISP international fiber to go to the site and use google international fiber to return. Not way to tell unless you can trace from the other end.
It is technically possible to get into some ISP routers and do tests if they have what is called lookglass web site.
It is somewhat surprising you get that much latency to 8.8.8.8. Google duplicates that IP in many places and for most people it is in a large city very close....most times well under 10ms.
Unfortunately when you have so may private IP address in the path it hard to tell which ISP it is running in. My guess would be the 172.18.x.x. where you see the first large jump is your ISP.
The other nastly issue with using trace is it only shows the path to the IP the return path could be very different. ISP tend to keep the traffic on their network as long as possible. So it could your ISP international fiber to go to the site and use google international fiber to return. Not way to tell unless you can trace from the other end.
It is technically possible to get into some ISP routers and do tests if they have what is called lookglass web site.