Yes - see https://www.reddit.com/r/ipv6/comments/1nf3ytq/how_do_i_comp...

I could not escalate this inside Globe Telecom (no way to reach engineers that understand what a "peering issue" is), and Level3 (the transit provider where all failed traceroutes were going through) did not respond to emails.

Thankfully, it's mostly fixed now - Level3 is no longer the last successful hop on any of the traceroutes. The only failing link is with Evoluhost, and the problem has been traced to a routing loop involving 2001:fe0:4775:1c0::1 inside Globe (that I have no way to complain about).

Today's situation: https://i.ping.pe/j/9/img_j99kbqkn.png