cancel
Showing results for 
Search instead for 
Did you mean: 

Internet packet loss and latency issues

tharris05
I'm here a lot

I am having intermittent issues with packet loss and latency issues. Laptop is wired directly to the modem. A technician has been out twice to my house and the issue keeps coming up. 

 

Ping statistics for 2607:f8b0:400b:804::2004:
Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 22ms, Average = 17ms

 

Tracing route to www.google.com [2607:f8b0:400b:804::2004]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 2607:fea8:5cdb:ee00:e6bf:faff:fe88:5866
2 15 ms 14 ms 14 ms 2607:f798:804:13::1
3 15 ms 20 ms 24 ms 2607:f798:10:881f:0:690:6324:3045
4 19 ms 16 ms 22 ms 2607:f798:10:23e:0:2091:4822:7221
5 15 ms 18 ms 18 ms 2607:f798:10:35b:0:2091:4823:5218
6 15 ms 16 ms 21 ms 2607:f798:14:83::2
7 17 ms * * 2001:4860::1c:4000:e8cb
8 18 ms 18 ms 17 ms 2001:4860:0:1::5c81
9 15 ms 16 ms 16 ms yyz10s20-in-x04.1e100.net [2607:f8b0:400b:804::2004]

Trace complete.

 

Tracing route to www.google.com [2607:f8b0:400b:802::2004]
over a maximum of 30 hops:

1 22 ms 1 ms 1 ms 2607:fea8:5cdb:ee00:e6bf:faff:fe88:5866
2 14 ms 14 ms 13 ms 2607:f798:804:13::1
3 18 ms 12 ms 13 ms 2607:f798:10:881f:0:690:6324:3045
4 16 ms 17 ms 16 ms 2607:f798:10:23e:0:2091:4822:7221
5 14 ms 18 ms 14 ms 2607:f798:10:35b:0:2091:4823:5218
6 16 ms 15 ms 14 ms 2607:f798:14:83::2
7 17 ms 16 ms 17 ms 2001:4860:0:17::1
8 19 ms 17 ms 18 ms 2001:4860:0:1::1591
9 17 ms 18 ms 18 ms yyz12s06-in-x04.1e100.net [2607:f8b0:400b:802::2004]

Trace complete.

 

I have been told that this is an issue with your internet service provider's way they are routing to the Fortnite servers and that I need to reach out for help. I speak with people on the phone and they cannot help. 

 

Please help!

 

*Added Labels*

8 REPLIES 8

Re: Internet packet loss and latency issues

RogersTony
Moderator
Moderator

Hello, @tharris05

 

Welcome to the Rogers Community Forums!

 

Thank you for posting your concern to the Community. We know how much of a challenge it can be to game online when you are experiencing latency. Can you please traceroute and ping test the Canadian server address for Fortnite? Here is the address you can use: qosping-aws-us-west-1.ol.epicgames.com.

 

Please post the results of the ping test and trace route to the community. 

 

We look forward to reviewing your results.

 

RogersTony

 

 

Re: Internet packet loss and latency issues

Hi RogersTony, 

 

Here is what I get today:


Tracing route to qosping-aws-us-east-1.ol.epicgames.com [34.194.116.183]
over a maximum of 30 hops:

1 41 ms 1 ms 1 ms 10.0.0.1
2 14 ms 13 ms 12 ms 99.255.192.1
3 16 ms 15 ms 15 ms 66.185.90.45
4 22 ms 16 ms 14 ms 9002-cgw01.ym.rmgt.net.rogers.com [209.148.227.221]
5 18 ms 23 ms 18 ms 209.148.235.218
6 * * * Request timed out.
7 19 ms 19 ms 19 ms 52.93.3.40
8 15 ms 16 ms 24 ms 52.93.3.47
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 35 ms 33 ms 34 ms 52.93.29.34
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 36 ms 33 ms 34 ms ec2-34-194-116-183.compute-1.amazonaws.com [34.194.116.183]

Trace complete.

 

Tracing route to qosping-aws-us-west-1.ol.epicgames.com [13.56.62.131]
over a maximum of 30 hops:

1 49 ms 1 ms 1 ms 10.0.0.1
2 12 ms 13 ms 14 ms 99.255.192.1
3 14 ms 17 ms 13 ms 66.185.90.41
4 15 ms 16 ms 16 ms 9002-cgw01.mtnk.asr9k.rmgt.net.rogers.com [209.148.227.217]
5 49 ms 50 ms 50 ms 209.148.238.42
6 62 ms 61 ms 62 ms 209.148.238.46
7 64 ms 63 ms 64 ms 69.63.250.241
8 62 ms 63 ms 67 ms 99.83.93.108
9 69 ms 85 ms 70 ms 52.93.75.36
10 65 ms 67 ms 68 ms 52.93.75.49
11 * * * Request timed out.
12 * * * Request timed out.
13 80 ms 82 ms 81 ms 52.93.47.50
14 89 ms 89 ms 86 ms 52.93.47.245
15 88 ms 90 ms 87 ms 54.240.242.163
16 87 ms 86 ms 86 ms 52.93.47.98
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 88 ms 86 ms 87 ms ec2-13-56-62-131.us-west-1.compute.amazonaws.com [13.56.62.131]

Trace complete.

 

 

Re: Internet packet loss and latency issues

Hello, @tharris05

 

Thank you for those results, I have passed them along to our support team to review.

 

Can you also send us the results of a Ping test to that address? A timestamp of when the tests were run will also be useful.

 

We look forward to reviewing your results.

 

RogersTony

Re: Internet packet loss and latency issues

Hi RogersTony, 

 

Here is the updated info you requested.

 

Timestamp: 10:30am EST 2023-01-31

 

C:\>ping qosping-aws-us-west-1.ol.epicgames.com.

Pinging qosping-aws-us-west-1.ol.epicgames.com [13.56.62.131] with 32 bytes of data:
Reply from 13.56.62.131: bytes=32 time=84ms TTL=42
Reply from 13.56.62.131: bytes=32 time=84ms TTL=42
Reply from 13.56.62.131: bytes=32 time=89ms TTL=42
Reply from 13.56.62.131: bytes=32 time=85ms TTL=42

Ping statistics for 13.56.62.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 89ms, Average = 85ms

C:\>ping qosping-aws-us-east-1.ol.epicgames.com

Pinging qosping-aws-us-east-1.ol.epicgames.com [52.203.3.55] with 32 bytes of data:
Reply from 52.203.3.55: bytes=32 time=72ms TTL=45
Reply from 52.203.3.55: bytes=32 time=33ms TTL=45
Reply from 52.203.3.55: bytes=32 time=34ms TTL=45
Reply from 52.203.3.55: bytes=32 time=33ms TTL=45

Ping statistics for 52.203.3.55:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 72ms, Average = 43ms

 

C:\>tracert qosping-aws-us-west-1.ol.epicgames.com.

Tracing route to qosping-aws-us-west-1.ol.epicgames.com [13.56.62.131]
over a maximum of 30 hops:

1 42 ms 1 ms 1 ms 10.0.0.1
2 21 ms 16 ms 14 ms 99.255.192.1
3 13 ms 14 ms 15 ms 66.185.90.41
4 15 ms 14 ms 13 ms 9002-cgw01.mtnk.asr9k.rmgt.net.rogers.com [209.148.227.217]
5 50 ms 50 ms 50 ms 209.148.238.42
6 62 ms 62 ms 62 ms 209.148.238.46
7 63 ms 62 ms 61 ms 69.63.250.241
8 62 ms 64 ms 62 ms 99.83.93.108
9 63 ms 64 ms 67 ms 52.93.75.84
10 64 ms 70 ms 74 ms 52.93.75.97
11 * * * Request timed out.
12 83 ms 85 ms 85 ms 150.222.30.60
13 87 ms 83 ms 82 ms 150.222.30.201
14 98 ms 88 ms 87 ms 150.222.31.100
15 85 ms 84 ms 86 ms 150.222.31.113
16 84 ms 86 ms 88 ms 15.230.36.124
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 85 ms 91 ms 89 ms ec2-13-56-62-131.us-west-1.compute.amazonaws.com [13.56.62.131]

Trace complete.

C:\>tracert qosping-aws-us-east-1.ol.epicgames.com

Tracing route to qosping-aws-us-east-1.ol.epicgames.com [52.203.3.55]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 10.0.0.1
2 15 ms 12 ms 14 ms 99.255.192.1
3 16 ms 15 ms 14 ms 66.185.90.45
4 15 ms 16 ms 15 ms 9002-cgw01.ym.rmgt.net.rogers.com [209.148.227.221]
5 14 ms 16 ms 17 ms 209.148.235.218
6 * * * Request timed out.
7 17 ms 17 ms 17 ms 52.93.3.136
8 18 ms 19 ms 17 ms 52.93.3.143
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 48 ms 34 ms 34 ms 52.93.29.26
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 33 ms 32 ms 33 ms ec2-52-203-3-55.compute-1.amazonaws.com [52.203.3.55]

Trace complete.

 

 

Re: Internet packet loss and latency issues

Thank you @tharris05!

 

The tracert results look fine for the east coast server but there's quite a rise in ping times for the west coast server. I would highly recommend that you change your matchmaking settings to ensure that you always match with players on only the east coast.

 

Gaming on a west coast server if you live in the east is never going to be ideal simply due to the raw distance between your location and the servers location. You'll always be at a disadvantage when compared to players that live closer to the server. The matchmaking settings are likely defaulted to auto, so please try changing them to NA-East and let us know if that improves your experience.

 

See here for more help: How do I change my matchmaking region in Fortnite? - Fortnite Support (epicgames.com)

 

Regards,

RogersCorey

Re: Internet packet loss and latency issues

I have always been on the NA East server. I only pinged the west server as that is the server that was recommended to do the tracer on in the previous post.

Re: Internet packet loss and latency issues

My apologies… replied to the incorrect post


I have always been on the NA East server. I only pinged the west server as that is the server that was recommended to do the tracer on in the previous post.

Re: Internet packet loss and latency issues

Hello, @tharris05 

 

Thank you for providing us with those details.

 

It appears that most of the issues you are facing are occurring outside of the Rogers network. Everything after hop 6 on the traceroute is outside the Rogers network which is where the majority of the time out errors are occurring. We are limited in our ability to address issues that are occurring outside of our network.

 

I know this is not the answer you were hoping to hear. 😞

 

RogersTony

 

Topic Stats
  • 8 replies
  • 2074 views
  • 1 Like
  • 3 in conversation