bump bump bump
bump bump bump
Received a response from noc@Level3, sadly no solution:
Here's some technical speak so you know what he means.Hi,
If the traces continue to the destination and there isn't end to end loss or latency that can't be attributed to return path, then it's more likely that it's control plane ICMP rate limiting. The forwarding plane will have a much different experience than the control plane.
Regards
Which is why all my trace routes are done with ICMP, TCP, and UDP packets. Guess what, same results with 3 different protocols. Regardless, Verizon is now harassing them as well as its not just XIV affected. Its any service routed via level 3 NY, Chicago, and Montreal unless said service bought allotted bandwidth.Received a response from noc@Level3, sadly no solution:
Here's some technical speak so you know what he means.
To add: I get packet loss at the destination as well. Aka Excalibur Server. This isn't some insane hop/distance for me. It's 300 miles and 12 hops, 3 companies: Ormuco <> Level 3 <> Verizon
Last edited by ReplicaX; 02-06-2014 at 10:48 PM. Reason: addition
so here is a long tracet from my Verizon fios ISP at my house all the way to Hyperion data center. IF you look you can see at level3 in New York and at level3 in Montreal there is consistent packet loss. The unexpected packet loss is also happening directly at the SE server for Hyperion. This is unacceptable
Same routing as me, as we both are off Boston FiOS. Every week I submit a new ticket to Verizon, they are well aware of Level 3's issues. However, it is still Level 3's lines and not Verizon. Ormuco and every other ISP affected should be hammering down on Level 3. Unless someone isn't paying for additional Bandwidth and that is why Level 3 is dropping packets.so here is a long tracet from my Verizon fios ISP at my house all the way to Hyperion data center. IF you look you can see at level3 in New York and at level3 in Montreal there is consistent packet loss. The unexpected packet loss is also happening directly at the SE server for Hyperion. This is unacceptable
As I've stated since Day #1, 12/24/13. SE, how about a statement and some help with your customers to work through this. Stop remaining silent as this continues to be an issue, it makes you look ignorant.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.