Severe packet loss at ash-b2-link.ip.twelve99.net. Ashburn looping to DC and back. Please reroute for efficiency and drop that node/server

[redfish9]

 

1. Catastrophic Packet Loss (40.8%)

The most critical issue is the 40.8% packet loss occurring at Hop 5 (80.239.135.178), which belongs to the twelve99.net network (also known as Arelion).

• Impact: For real-time applications, anything over 2% packet loss causes noticeable LAG. A 40.8% loss means 4 out of every 10 packets of data are being dropped and must be resent. This is catastrophic.

• The Problem: Terrible LAG. This level of loss is a strong indicator of severe network congestion or a faulty peering link between Verizon/FIOS and the transit provider (Arelion/twelve99.net). This issue is completely outside of my home network's control. This is a routing problem that occurs any time my traffic is sent over this specific, unstable link.

Request: to investigate your peering agreement and re-route my traffic destined for this IP range through a more stable transit provider.

Secondly, the routing shown in my trace to 192.207.0.1 appears to involve traffic traveling past my nearest major hub (Ashburn) and then looping back, which is inefficient.

The "DC Back to Ashburn" Loop

1. My Starting Point: The first major traffic exchange to a regional hub should be the Ashburn, VA data center cluster, as that is where I live.

2. The DC/NY Hand-Off: The twelve99.net IP addresses (80.x.x.x) often represent peering points in major East Coast cities like Washington D.C. or New York/New Jersey. My traffic is being sent to one of these major city exchange points.

3. The Server Location: The server at 192.207.0.1 is located in the Ashburn/Northern VA area.

4. The Loop: My server is in Ashburn, the route is:

   • My Home -> Ashburn/FIOS Hub -> DC/NY Peer (Arelion) -> Ashburn/Server.

Request: to provide me with the most EFFICIENT route.
Please help Verizon. Hundreds of thousands of people are suffering also. This isn't the first time that faulty server is mentioned.

[Cang_Household · Accepted solution]

This is likely will not be fixed by wireline operations. There are no concrete indications that the issue lies in the AS701.

ICMP-based tools are not credible in evaluating packet loss rate. ASBRs are usually instructed to de-prioritize or drop ICMP traffic proactively to preserve bandwidth.

AS701 enforces hot-potato routing by policy choice. Your packet will be routed out of the Verizon network at the earliest possible opportunity, so Verizon does not have control over the majority of the hops that your packet goes through.

[Cang_Household · Accepted solution]

This is likely will not be fixed by wireline operations. There are no concrete indications that the issue lies in the AS701.

ICMP-based tools are not credible in evaluating packet loss rate. ASBRs are usually instructed to de-prioritize or drop ICMP traffic proactively to preserve bandwidth.

AS701 enforces hot-potato routing by policy choice. Your packet will be routed out of the Verizon network at the earliest possible opportunity, so Verizon does not have control over the majority of the hops that your packet goes through.

[Kh_Femi · Accepted solution]

Hello redfish9

Your issue has been escalated to a Verizon agent. Please check your Private Messenger Inbox for a message from a Verizon Support agent. You can find your Inbox by clicking on the envelope icon next to your avatar at the top right corner of this page. Response times may vary. Continue to check your Inbox regularly for a reply and direct all correspondence concerning your issue to the agents who will be assisting you privately.

Thank you.