Severe Packet Loss on International Routing - Need IP Lease Release or Escalation to Network Engineering

The Problem

Since March 2 night, I cannot access yuque.com (a Chinese website I use for work). The server IP is 203.107.62.20. My local network and WiFi are working fine. The problem is in Comcast's routing.

What My MTR Trace Shows

I ran an MTR trace from my PC to 203.107.62.20 (30 hops). Here is what happens:

• Hops 1-17 (Comcast internal network, Denver → Sunnyvale → Great Oaks): 0% loss, normal latency (7-50ms). Everything is fine inside Comcast's network.
• Hop 18: 100% packet loss. This is where my traffic leaves Comcast and gets handed off internationally.
• Hops 19-21 (ChinaNet backbone, 202.97.27.237 / 202.97.65.70 / 202.97.93.54): 82-94% packet loss, 717-732ms latency.
• Hops 22-29: 100% loss (No response from host).
• Hop 30 (destination, 203.107.62.20): 94% loss, 736ms average latency. Basically unreachable.

Global Tests Confirm It's Not the Server

I used ping.pe to test 203.107.62.20 from nodes around the world. Every node reaches the server successfully. Tokyo, Hong Kong, LA, Seattle, London, Singapore - all fine. The server is healthy. The problem is only on MY path to it.

I also used ping.pe to test my own public IP ([Edited: "Personal Information"]) from global nodes. Results show poor reachability from almost everywhere, not just China. This suggests my current IP assignment or routing path is problematic overall.

What I Already Tried

• Restarted my Xfinity Gateway via the Xfinity app. Public IP did not change.
• Contacted Level 1 support via live chat. They checked WiFi status (my WiFi is fine), suggested ipconfig /release (which only affects local IP, not my public IP assigned by Comcast). Issue was not resolved.
• I am using an Xfinity-provided Gateway, no third-party equipment.

What I Need

My public IP ([Edited: "Personal Information"]) appears to be stuck on a bad routing path. I need one of the following:

1. DHCP lease release on Comcast's end to assign me a new public IP (which may route through a healthier path), or
2. Escalation to the network/peering engineering team to investigate the routing from my IP block to ChinaNet (AS4134).

Screenshots

I have attached:

1. MTR trace showing the full 30-hop path with packet loss data
2. https://check-host.net/check-ping?host=www.yuque.com results for 203.107.62.20 (server reachable globally)

3. [Image Removal: "Personal Information"]

4. https://check-host.net/check-ping?host= [Edited: "Personal Information"] results for [Edited: "Personal Information"] (my IP, poor global reachability)

5. [Image Removal: "Personal Information"]

I can provide my account details, CMAC address, and full name via DM immediately upon request.

Thank you.