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. 

[DrunKev]

I have also been experiencing congestion issues resulting in ping spikes that are not visible in in-game ping indicators but can definitely be felt. This is showing up in overwatch, league of legends and fortnite. There was one server that routed through Oregon where the spikes did not occur but all routing going through Ashburn, New York seemed to be having issues. Here's an MTR.

It is occurring at all times of the day and worked with Riot providing logs and they mentioned how this is a routing issue that Bell would need to resolve specifically. This kind of congestion likes does not result in any noticeable symptoms for anything other than gaming due to the latency sensitivity and how subtle the effects are despite being consistent.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| RT-AX88U-E178 - 0 | 351 | 351 | 0 | 0 | 1 | 0 |
| 192.168.2.1 - 0 | 351 | 351 | 1 | 1 | 3 | 1 |
| [hidden] - 0 | 351 | 351 | 1 | 2 | 4 | 2 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
|tcore3-montreal01_1/9/0/2_42.net.bell.ca - 29 | 167 | 120 | 24 | 25 | 27 | 25 |
|cr01-toroon63zda_bundle-ether1.net.bell.ca - 58 | 107 | 45 | 0 | 27 | 29 | 27 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| bx6-chicagodt_0-6-0-0.net.bell.ca - 0 | 351 | 351 | 26 | 26 | 29 | 26 |
|be-220-pe03.350ecermak.il.ibone.comcast.net - 0 | 351 | 351 | 26 | 26 | 29 | 26 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[Felix]

Hey there, i'm having the same problem with valorant/league of legend. The issue appears randomly, everything was working fine 1 month ago, but not I can't even play the game correctly with all the packet-loss i'm getting. 1.5Gpbs Fibe Ethernet on a HH4000 also.

[User1233]

I am having the same issue --- tons of packet loss, regardless of what site I trace to. The technical support I've received has been beyond disappointing. I'm being asked to troubleshoot the devices in my home --- and the issue has absolutely nothing to do with that. It's beyond frustrating.

[honne]

Hi, So I ended up resolving my issue and realized it was a local user network related issue and not necessarily tied to my bell service but a function called "Repair LSR" with a program called GearUp Booster which I used and this caused my issue however I did not know because I uninstalled a while ago.

The function says to use the following in a cmd prompt however I just pressed the button from the app and it did it's thing and I uninstalled and things seem to be working again. 

netsh winsock reset

 

If anything investigate any vpn programs u may have used.

[BellNick]

Hi there @User1233 
Thank you for your post and welcome to the Community.
We wanted to check in to see if you're still experiencing this issue and if so, have you checked out what @honne suggested?
Looking forward to hearing back.

[OP05]

There was another question posted but I feel like Bell didn't answer or help whatsoever with the posters there. This wasn't an issue until today. First this is what I did on my end to solve the problem:

1) Rebooted the router (which updated the firmware)

2)Used `netsh winsock reset` in the cmd and restarded my pc

3) Tried cloudflare  and google dns server with no success

The most infuriating thing is that this wasn't a problem up until yesterday. I have 1.5gbs fibre and I'm currently getting worse ping than my neighbour running on Rogers network.

I used WinMTR and here are the logs after running it for a good 5-10 minutes:
```
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| mynetwork.home - 0 | 307 | 307 | 0 | 0 | 14 | 0 |
| 10.50.43.5 - 0 | 307 | 307 | 0 | 2 | 23 | 1 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| tcore3-toronto63_37.net.bell.ca - 56 | 96 | 43 | 0 | 71 | 74 | 71 |
|tcore3-toronto63-bundle-ether44.net.bell.ca - 0 | 307 | 307 | 2 | 6 | 14 | 10 |
| 64.230.106.101 - 4 | 270 | 260 | 61 | 69 | 89 | 70 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

```

FWIW here's the `tracert 192.207.0.1`:

```

C:\Users>tracert 192.207.0.1

Tracing route to 192.207.0.1 over a maximum of 30 hops

1 1 ms <1 ms <1 ms mynetwork.home [192.168.2.1]
2 2 ms <1 ms 2 ms 10.50.43.5
3 * * * Request timed out.
4 71 ms * * tcore3-toronto63_37.net.bell.ca [64.230.59.194]
5 5 ms 7 ms 7 ms tcore3-toronto63-bundle-ether44.net.bell.ca [142.124.127.156]
6 * 69 ms 71 ms 64.230.106.101
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.

```

[honne]

did you ever install that program I mentioned called GearUpBooster? You've gotta follow those instructions otherwise it's just gonna keep happening. 

[Tonygms2]

Hello,

I am having fluctuating ping and packetloss during online fps game like valorant or counterstrike. I am playing on wifi for a long time now but recently this issue is coming up . 

[Vanadiel]

Any other wifi traffic while this is happening? How is the wifi signal strength?

[Tonygms2]

No , wifi strength is strong. The modem is literally beside my laptop desk.

[dks]

Thanks for your question. Unfortunately ping and packet loss are often issues which occur outside of Bell’s network and are beyond Bell’s control. They can be due to congestion at ant point on the internet. If you can run a traceroute, we might be able to offer further comment. 

[fix my Ping]

Setup

• Bell Fibe 1.5 Gbps
• Wired over Ethernet (Cat6), Windows 11
• Home Hub replaced by Bell, factory reset, no Wi-Fi in use
• Games: Valorant, CoD, Apex
• Region: North Virginia. I’m in eastern Canada and normally see 20–30 ms on other ISPs.

Problem
Since switching to Bell I’m getting a 70–80 ms base ping that spikes to 150–250 ms during matches. It’s consistent across games and times of day, and it makes FPS unplayable.

What I’ve tried

• New Bell router from support
• Different Ethernet cables and ports
• Direct connection to the modem/router, no switches
• DNS set to Cloudflare and Google
• Disabled QoS and background apps
• Tried a second PC
• Speed is fine, but latency and jitter are not

What I’m looking for

• Can a Bell rep check routing/peering to AWS us-east-1 / Ashburn?
• Is there a low-latency/fastpath type profile Bell can apply?
• Happy to provide timestamps and traceroutes via DM.

Extra info I can share if useful

• PingPlotter or mtr runs to the game servers show higher latency starting a few hops out
• Evening hours are slightly worse, but the high base ping is there all day

Any guidance or a network check would be appreciated. This wasn’t an issue before switching to Bell.

[dks]

Briefly, Bell can’t provide a fix for your ping issue. I could comment further if you provide a traceroute to your gaming host. Bell has no control over any ping beyond their network. 

[Vanadiel]

Is this issue there for the same end address, or are there multiple end addresses involved? How long has this problem been an issue?

Without knowing the server IP it would be difficult to provide further insight. What I can say is that ping is not necessarily a true representation of the situation, as ICMP packets have a low priority with a router.

If the router is busy forwarding packets, your ICMP will be processed at a lower priority. That does not mean the packets are processed slow.

It could also be a Bell routing point has a temporary issue, or the network does.

If we can get the end IP we can try to see what's up.

[fix my Ping]

I’m seeing high base latency in Valorant to Riot IP 192.207.0.1.
Local and Halifax core: 1–2 ms. Bell NY 207.231.227.62: ~20 ms.
After the Bell → Telia handoff the latency jumps to 45–56 ms at 62.115.143.13, which matches my 70–80 ms in-game base with spikes into 150–250.
Please review routing/peering for 192.207.0.0/16 toward Ashburn. Is there an alternate path that avoids Telia or uses a lower-RTT peer via Montreal/Toronto to Ashburn?
Trace at 10/24/2025 12:45 PM

4 142.166.149.93 2 ms
5 207.231.227.62 21 ms (Bell NY)
8 62.115.143.13 45–56 ms (Telia)