Packet loss due to bad routing to Valorant servers

[Ghill]

Hello, I have 1.5Gpbs Fibe Ethernet on a HH4000 and for months now I've been experiencing heavy packet loss to a game called Valorant. 

There seems to be known issues with connections to these AWS servers from Bell's end, but no-one from support has been able to even talk to me directly about routing. I've been through three replacement HH4000's, checking ports, and the issue definitely seems to be IP routing.

Is anyone else here experiencing the same issues? I have lots of trace route tests to show evidence of this. I know I saw a reddit thread on /r/bell as well as some threads on twitter about people having the similar issues. 

[Vanadiel]

Shaw (Rogers) has direct peering. Does not sound like Bell does, but I will do a traceroute later on Bell to see what the path is.

If you have a VPN service it might provide better results by using a different path.

Tracing route to 192.207.0.0 over a maximum of 30 hops

1 1 ms <1 ms 1 ms 192.168.0.1
2 13 ms 14 ms 12 ms 70.76.32.1
3 13 ms 12 ms 13 ms rd4he-be101-1.su.shawcable.net [24.244.8.141]
4 21 ms 23 ms 20 ms rc2fs-be2.mt.shawcable.net [66.163.75.170]
5 34 ms 31 ms 35 ms rc3ec-be10.il.shawcable.net [66.163.65.6]
6 33 ms 32 ms 32 ms rc4ec-be6-1.il.shawcable.net [66.163.65.70]
7 32 ms 33 ms 33 ms 192.207.0.0

Trace complete.

[Vanadiel]

This is the trace route from a Bell fibre connection:

Tracing route to 192.207.0.0 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms unifi.localdomain [192.168.1.1]
2 <1 ms <1 ms <1 ms 192.168.88.1
3 1 ms 1 ms 1 ms 10.11.4.89
4 * * * Request timed out.
5 16 ms 15 ms 15 ms 64.230.100.60
6 15 ms 15 ms 15 ms 142.124.127.146
7 17 ms 15 ms 15 ms 142.124.127.156
8 15 ms 14 ms 16 ms 64.230.106.101
9 26 ms 25 ms 25 ms 192.207.0.0

Trace complete.

Are you by any chance using a VPN or other gaming services? Bell Canada seems to also have a routing agreement as 64.230.106.101 is the last bell hop and from there it goes directly to 192.207.0.0

[dks]

As I said, once a packer leaves Bell’s network, your ping is at the mercy of the internet. The internet itself figures out the best path to the destination host. The routing can’t be controlled. 

[dks]

Yes, a VPN might work, but some gaming servers kick for a VPN. 

[fix my Ping]

It is unusable at this point - cod won't load, I somehow get random better ping in illinois then N. Virginia. This is messed up. I ran multiple tests and when I use Rogers wireless I get a better ping somehow.

[fix my Ping]

Exactly, this is unusable now.

[Vanadiel]

Can you do a complete traceroute to 8.8.8.8 and post it here?

I want to see the route it's taking, because when I do a tracert to 192.207.0.0 it never goes through Telia or any other hop. It goes directly from Bell to the destination.

1 <1 ms <1 ms <1 ms unifi.localdomain [192.168.1.1]
2 <1 ms <1 ms <1 ms 192.168.88.1
3 1 ms 1 ms 1 ms 10.11.4.89
4 * * * Request timed out.
5 16 ms 15 ms 15 ms 64.230.100.60
6 15 ms 15 ms 15 ms 142.124.127.146
7 17 ms 15 ms 15 ms 142.124.127.156
8 15 ms 14 ms 16 ms 64.230.106.101
9 26 ms 25 ms 25 ms 192.207.0.0

[dks]

You get a better ping because Rogers uses different peering and path to your server. This has been an issue since the public internet began. Providers have no control over your packets once they leave their system. This is the nature of the internet.