by Noodelzz Contributor
Contributor

Experiencing random packet loss

Hi, i've been trying to play League of Legends and from about 3-4 days ago i've been experiencing packet loss that comes randomly throughout the day, i'm connected through ethernet and my ping will stay consistently at about 25-40, i can usually play some matches without the issue however, sometimes i'll be in game and my movements will be delayed for about 3 seconds where it doesn't respond to what i am trying to do(the ping does not change), when the packet loss comes it usually stays for a while and tends to continously strike with random intervals usually around 5 -10 seconds apart. 

I've noticed when troubleshooting in the command prompt, pinging 'google.com' tends to sometimes show packet loss, here is proof: 

 

C:\WINDOWS\system32>ping -t google.com

Pinging google.com [216.58.198.238] with 32 bytes of data:
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=17ms TTL=55
Request timed out.
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=15ms TTL=55
Reply from 216.58.198.238: bytes=32 time=15ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=15ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=15ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Request timed out.
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=17ms TTL=55
Request timed out.
Request timed out.
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55
Reply from 216.58.198.238: bytes=32 time=16ms TTL=55

Ping statistics for 216.58.198.238:
Packets: Sent = 26, Received = 22, Lost = 4 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 17ms, Average = 15ms

 

 

84 REPLIES
by
EE Community Support Team

Re: Experiencing random packet loss

Hi @Noodelzz and welcome to the community.

 

This is something @XRaySpeX may be able to assist with.

 

Many thanks,

 

Lee

by Grand Master
Grand Master

Re: Experiencing random packet loss

Welcome to EE's Home Broadband Forum.

If you would like help with your speed or connection issues, please would you carry out the steps and provide the data as requested in the Need Help with Your Home Broadband Speed or Connection? sticky. This will enable us to diagnose the problem and advise you further.

 

Also please post your tracert to your game server.

 

That's not true packet loss. "Request timed out." will just occur when a site, like Google, is too busy to deal with your ping. ping is the least important transaction to be responded to.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Star" button below.
To phone EE: The local rate landline number 020 7362 0200 or Freephone 0800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
by Noodelzz Contributor
Contributor

Re: Experiencing random packet loss

DSL Status 

 https://gyazo.com/6f602d3ddf29892a39d09696992e1e56

System Uptime is:

03:19:12

 

Speed test 

https://www.thinkbroadband.com/speedtest/1497803328744740655

 

Exchange

https://availability.samknows.com/broadband/exchange/MYWEH

 

Tracert to League of Legends EUW Server #1

C:\WINDOWS\system32>tracert 185.40.65.1

Tracing route to 185.40.65.1 over a maximum of 30 hops

1 2 ms 5 ms 2 ms BRIGHTBOX2 [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 16 ms 15 ms 16 ms 213.121.98.136
5 17 ms 14 ms 15 ms 87.237.20.132
6 16 ms 17 ms 16 ms 87.237.20.36
7 * 21 ms 23 ms bundle-ether12.lontr4.london.opentransit.net [193.251.255.101]
8 24 ms 23 ms 23 ms et-4-0-2-0.pastr3.parispastourelle.opentransit.net [193.251.241.158]
9 29 ms 23 ms 24 ms hundredgige1-9-0-0.auvtr4.parisaubervilliers.opentransit.net [193.251.128.251]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
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 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

 and ahhh okay, sorry about that. Right now when performing the 'tracert', the packet loss seems to have gone away as it is completely random and unpredictable, should i wait until the problem arises again and perform/send a new one when that happens?

by stonemercy Investigator
Investigator

Re: Experiencing random packet loss

Getting the same here running WinMTR to the same IP

 

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| BrightBox.ee - 0 | 9 | 9 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| 213.121.98.136 - 0 | 9 | 9 | 17 | 19 | 37 | 17 |
| 87.237.20.132 - 0 | 9 | 9 | 17 | 17 | 18 | 18 |
| 87.237.20.36 - 0 | 9 | 9 | 18 | 18 | 19 | 18 |
|bundle-ether12.lontr4.london.opentransit.net - 0 | 9 | 9 | 20 | 22 | 26 | 20 |
|et-7-0-8-0.pastr3.parispastourelle.opentransit.net - 0 | 9 | 9 | 25 | 30 | 43 | 43 |
|hundredgige1-2-0-2.auvtr4.parisaubervilliers.opentransit.net - 0 | 9 | 9 | 26 | 30 | 34 | 30 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|

by Grand Master
Grand Master

Re: Experiencing random packet loss

That's not packet loss. That's just servers who can't be bothered to respond to pings.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Star" button below.
To phone EE: The local rate landline number 020 7362 0200 or Freephone 0800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
by Grand Master
Grand Master

Re: Experiencing random packet loss

Your BB connection is fine. There's nowt there to account for it.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Star" button below.
To phone EE: The local rate landline number 020 7362 0200 or Freephone 0800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
by stonemercy Investigator
Investigator

Re: Experiencing random packet loss

But in the games I've played (Guild Wars 2 and WoW) I get pretty bad lag spikes with no visible cause.

 

How can there not be a fault if this happens?

by Grand Master
Grand Master

Re: Experiencing random packet loss

@stonemercy: I was referring to @Noodelzz's BB. I know nowt about yours as you haven't supplied me with any data about it. Please follow my 1st reply in this thread & I will comment further on yours.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Star" button below.
To phone EE: The local rate landline number 020 7362 0200 or Freephone 0800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
by stonemercy Investigator
Investigator

Re: Experiencing random packet loss

Can't use the test socket as my master socket doesn't have a front split.

 

DSL Status

 

I think this is my Exchange

 

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| BrightBox.ee - 0 | 49 | 49 | 0 | 0 | 2 | 0 |
| No response from host - 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| 213.121.98.136 - 0 | 49 | 49 | 16 | 18 | 34 | 26 |
| 87.237.20.132 - 0 | 49 | 49 | 16 | 18 | 37 | 26 |
| 87.237.20.36 - 0 | 49 | 49 | 17 | 19 | 33 | 27 |
| 87.237.20.35 - 0 | 49 | 49 | 18 | 20 | 36 | 27 |
| 87.128.232.105 - 0 | 49 | 49 | 18 | 21 | 37 | 29 |
| 217.239.49.78 - 0 | 49 | 49 | 26 | 29 | 41 | 38 |
| 80.157.202.38 - 0 | 49 | 49 | 25 | 27 | 38 | 35 |
| 37.244.9.33 - 0 | 49 | 49 | 26 | 28 | 39 | 35 |
| 185.60.114.159 - 0 | 49 | 49 | 27 | 28 | 40 | 36 |
|________________________________________________|______|______|______|______|______|______|
Host: 185.60.114.159

by Grand Master
Grand Master

Re: Experiencing random packet loss

@stonemercy: Why does this tracert finish at 185.60.114.159 when your earlier one went bombing past parisaubervilliers, which I think this 1 is. Is 185.60.114.159 your gaming server?

 

You're confusing me with using IPs sometimes & hostnames others. Would you mind doing an ordinary tracert, which I'm familier with, to your gaming server with full hostnames?

 

I suspect you & OP are addressing same gaming server. Could it not be that that is busy?

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Star" button below.
To phone EE: The local rate landline number 020 7362 0200 or Freephone 0800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
by stonemercy Investigator
Investigator

Re: Experiencing random packet loss

I used the IP for the OP's League of Legends EUW tracert.

 

When I try to use CMD's Tracert it doesnt allow me to export to a txt so I use WinMTR instead.

 

The result I just posted was to WoW's EU Server.

 

If you have an idea on how to get past 'Access is denied' on CMD I'll be all ears.

 

Thanks

by Grand Master
Grand Master

Re: Experiencing random packet loss

Just copy & paste the CMD window as OP has. You can tracert IP & get results as hostnames by default.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Star" button below.
To phone EE: The local rate landline number 020 7362 0200 or Freephone 0800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
by stonemercy Investigator
Investigator

Re: Experiencing random packet loss

Oh, didn't think I could do that.

 

1 <1 ms 1 ms 1 ms BrightBox.ee [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 16 ms 16 ms 16 ms 213.121.98.136
5 21 ms 16 ms 16 ms 87.237.20.132
6 17 ms 17 ms 17 ms 87.237.20.36
7 18 ms 18 ms 19 ms 87.237.20.35
8 20 ms 19 ms 19 ms 87.128.232.105
9 28 ms 27 ms 27 ms 217.239.49.78
10 28 ms 26 ms 26 ms 80.157.202.38
11 26 ms 26 ms 26 ms 37.244.9.33
12 28 ms 27 ms 27 ms 185.60.114.159

 

Here's also Blizzard's own MTR, Traceroute and Ping tests:

PING:
PING 95.147.190.125 (95.147.190.125) 56(84) bytes of data.

--- 95.147.190.125 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 5003ms

 

18/06/2017 22:06:54 UTC
--------------------

TRACEROUTE:
traceroute to 95.147.190.125 (95.147.190.125), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.514 ms 0.563 ms 0.678 ms
2 * * *
3 37.244.9.102 (37.244.9.102) 0.655 ms 0.706 ms 0.754 ms
4 24.105.31.19 (24.105.31.19) 8.683 ms 11.165 ms 11.198 ms
5 37.244.11.32 (37.244.11.32) 8.395 ms 8.424 ms 8.567 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *


18/06/2017 22:06:54 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.5 0.4 0.6 0.0
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.9.102 0.0% 10 0.8 0.8 0.7 0.9 0.0
4. 24.105.31.19 0.0% 10 8.6 8.7 8.5 8.8 0.1
5. 37.244.11.32 0.0% 10 8.5 8.7 8.5 10.0 0.5
6. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0


18/06/2017 22:06:54 UTC
--------------------

 

by Grand Master
Grand Master

Re: Experiencing random packet loss

@stonemercy: Please would you do pathping 185.60.114.159 ?

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Star" button below.
To phone EE: The local rate landline number 020 7362 0200 or Freephone 0800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
by stonemercy Investigator
Investigator

Re: Experiencing random packet loss

C:\Users\Lee>pathping 185.60.114.159

Tracing route to 185.60.114.159 over a maximum of 30 hops

0 Lee-PC.default [192.168.1.232]
1 BrightBox.ee [192.168.1.1]
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Lee-PC.default [192.168.1.232]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% BrightBox.ee [192.168.1.1]

Trace complete.

 

Formatting's a bit off but here ya go

by Grand Master
Grand Master

Re: Experiencing random packet loss

@stonemercy, c.c. @Noodelzz: Duh! Your pathping has given up the ghost prematurely. It's a bit weak that way, stopping at the 1st non-responsive server.

 

Fortunately mine doesn't & I get this:

C:\>pathping 185.60.114.159

Tracing route to 185.60.114.159 over a maximum of 30 hops

  0  XRay-PC.XRayGroup [192.168.1.10]
  1  OrangeRouter [192.168.1.1]
  2  213.1.112.200
  3  213.1.117.45
  4  213.1.79.130
  5  87.237.20.136
  6  87.128.232.105
  7  217.239.49.74
  8  80.157.202.38
  9  37.244.9.33
 10  185.60.114.159

Computing statistics for 250 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           XRay-PC.XRayGroup [192.168.1.10]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  OrangeRouter [192.168.1.1]
                                0/ 100 =  0%   |
  2    8ms     0/ 100 =  0%     0/ 100 =  0%  213.1.112.200
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%   100/ 100 =100%  213.1.117.45
                                0/ 100 =  0%   |
  4    8ms     0/ 100 =  0%     0/ 100 =  0%  213.1.79.130
                                0/ 100 =  0%   |
  5   10ms     0/ 100 =  0%     0/ 100 =  0%  87.237.20.136
                                0/ 100 =  0%   |
  6   13ms     0/ 100 =  0%     0/ 100 =  0%  87.128.232.105
                                0/ 100 =  0%   |
  7   18ms     0/ 100 =  0%     0/ 100 =  0%  217.239.49.74
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%   100/ 100 =100%  80.157.202.38
                                0/ 100 =  0%   |
  9   17ms     0/ 100 =  0%     0/ 100 =  0%  37.244.9.33
                                0/ 100 =  0%   |
 10   17ms     0/ 100 =  0%     0/ 100 =  0%  185.60.114.159

Trace complete.

That means you would be losing 100% of packets at the node 80.157.202.38 (Deutsche Telekom AG). That's the problem!

 

(Ignore node 3. It's BT & is quite normal)

 

This is a matter of who EE chooses as its peering partners & so on down the line for transmitting its traffic onwards beyond its own network. It may be that EE or its peering partners have changed their peering partners or have got more busy when you started to have this issue.

 

There is nowt we can do here about this but I suggest you petition the BB Team, using the so-called "email" form that you can use for BB: https://explore.ee.co.uk/broadband/email-us , to look into this & check out what its peering partners are doing to cause this.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Star" button below.
To phone EE: The local rate landline number 020 7362 0200 or Freephone 0800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
by Noodelzz Contributor
Contributor

Re: Experiencing random packet loss

It's typical really, it was acting up all weekend but when i get frustrated enough to report it, it seems to have fixed itself xd. Thanks for you time anyway.

Highlighted
by Grand Master
Grand Master

Re: Experiencing random packet loss

You're welcome Smiley Happy! Glad I could be of assistance.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Star" button below.
To phone EE: The local rate landline number 020 7362 0200 or Freephone 0800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
by Noodelzz Contributor
Contributor

Re: Experiencing random packet loss

I spoke too soon.............the problem is back 

C:\WINDOWS\system32>tracert 162.249.72.1

Tracing route to 162.249.72.1 over a maximum of 30 hops

1 2 ms 2 ms 2 ms BRIGHTBOX2 [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 14 ms 15 ms 14 ms 213.121.98.136
5 14 ms 15 ms 14 ms 87.237.20.132
6 15 ms 14 ms 14 ms 87.237.20.36
7 20 ms 25 ms 25 ms bundle-ether12.lontr4.london.opentransit.net [193.251.255.101]
8 22 ms 22 ms 24 ms et-7-0-8-0.pastr3.parispastourelle.opentransit.net [193.251.132.164]
9 27 ms 22 ms 23 ms hundredgige2-15-0-1.auvtr4.parisaubervilliers.opentransit.net [193.251.128.249]
10 * * 31 ms riotgames-1.gw.opentransit.net [193.251.248.102]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
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 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

i have no idea if this  shows anything but i'm in-game right now and it's happening.

Let's get started

Join the EE Community to ask, answer, learn and share.