Highlighted
by Contributor
Contributor

Gaming Lag - New to EE

Hi,

 

I have only been with EE BB for one week and Im already regretting it moving from Sky.

 

Playing games like CS:GO (Average ping, but some sort of in game lag) and World of warcraft (High Ms score/ping).

 

Could someone please advise what I am to do to improve this, I did not have these issues with Sky so I know its not a hardware issue from my end.

 

Thanks

22 REPLIES 22
Highlighted
by Grand Master
Grand Master

Re: Gaming Lag - New to EE

Do you know the IP or URL of 1 of your gaming servers? Please post a tracert to it.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE: The local rate landline number +44 207 362 0200 or Freephone +44 800 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 => 2014: EE 20 Meg WBC
Highlighted
by
EE Community Support Team

Re: Gaming Lag - New to EE

Good morning @Rainbo911

 

Thank you for coming to see us in the EE community 🙂

 

When you get a chance to post the information @XRaySpeX has asked for, then he can potentially help you further.

 

I hope you start enjoying your games again.

 

Cheers

 

Richard

 

🙂

Highlighted
by Contributor
Contributor

Re: Gaming Lag - New to EE

Hi Richard + Technical Support Master! 

 

I will post the results later on today when I am home. I will run the tracert during non-peak hours and peak hours to see if there are differenes and post the results. I can however say it generally "seems" to be worse around peak hours after 6pm, but I havnt had a chance to try and play my games during non-peak hours as yet so we will see.

 

I have to say that I am impressed with the response time to my message! I didnt expect such a quick reply. So thanks for that and hopefully we can fix the issue.

 

Cheers

Adam

Highlighted
by
EE Community Support Team

Re: Gaming Lag - New to EE

Hi @Rainbo911

 

Thank you for taking the time to reply 🙂

 

We do try and help as quick as we can and @XRaySpeX is one of our community stars.

 

I think those comparisons will be great for him to see, and I've no doubt you are in the best hands.

 

Let's see what happens and hopefully some suggestions or advice can help you.

 

Have a great day.

 

Richard

 

🙂

Highlighted
by Grand Master
Grand Master

Re: Gaming Lag - New to EE

Thanks, Adam

 

You might as well also post your following BB characteristics:

 

1. Post your full router stats. For a BrightBox: login and go to Advanced Settings/ System/ DSL Status. Also post 'System Uptime' from top of System Log page. Full router stats are key to any speed & connection issues.

2. Try a wired speedtest here http://www.thinkbroadband.com/speedtest.html and copy to here just the "Link to this result:" link.

3. What exchange are you connected to? If you don't know use: http://www.samknows.com/broadband/exchange_search and post the URL of your exchange page.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE: The local rate landline number +44 207 362 0200 or Freephone +44 800 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 => 2014: EE 20 Meg WBC
Highlighted
by Contributor
Contributor

Re: Gaming Lag - New to EE

Hi,

 

1. Tracert for CS:GO

 

C:\Users\Adam>tracert 155.133.242.183

Tracing route to 155.133.242.183 over a maximum of 30 hops

1 2 ms 2 ms 3 ms BrightBox.ee [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 14 ms 16 ms 14 ms 213.1.128.237
5 20 ms 20 ms 20 ms 213.1.67.58
6 21 ms 20 ms 22 ms 87.237.20.128
7 21 ms 20 ms 21 ms 80.150.169.13
8 35 ms 40 ms 34 ms 62.157.249.202
9 40 ms 42 ms 32 ms ldn-bb3-link.telia.net [213.155.136.60]
10 110 ms 86 ms 36 ms hbg-bb1-link.telia.net [80.91.249.11]
11 54 ms 54 ms 54 ms s-bb3-link.telia.net [213.155.136.142]
12 51 ms 54 ms 52 ms s-b5-link.telia.net [62.115.141.203]
13 53 ms 51 ms 51 ms valve-ic-314988-s-b5.c.telia.net [62.115.62.226]
14 * * * Request timed out.
15 52 ms 51 ms 51 ms 155.133.242.183

Trace complete.

C:\Users\Adam>

 

2. Tracert for WoW

 

C:\Users\Adam>tracert 80.239.179.95

Tracing route to 80-239-179-95.customer.teliacarrier.com [80.239.179.95]
over a maximum of 30 hops:

1 2 ms 3 ms 1 ms BrightBox.ee [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 15 ms 14 ms 13 ms 213.1.128.237
5 21 ms 19 ms 20 ms 213.1.78.34
6 19 ms 19 ms 18 ms 87.237.20.128
7 20 ms 20 ms 20 ms 80.150.169.13
8 33 ms 36 ms 36 ms 62.157.249.202
9 33 ms 41 ms 33 ms ldn-bb3-link.telia.net [62.115.138.150]
10 37 ms 42 ms 40 ms adm-bb3-link.telia.net [213.155.136.99]
11 38 ms 37 ms 41 ms adm-b5-link.telia.net [62.115.140.115]
12 35 ms 35 ms 36 ms 80-239-205-133.customer.teliacarrier.com [80.239.205.133]
13 36 ms 38 ms 36 ms 80-239-205-133.customer.teliacarrier.com [80.239.205.133]
14 38 ms 36 ms 39 ms a23-36-230-1.deploy.static.akamaitechnologies.com [23.36.230.1]
15 * * * Request timed out.
16 * * * Request timed out.
17 39 ms 43 ms 39 ms be1299.agr21.ams03.atlas.cogentco.com [130.117.14.101]
18 40 ms 42 ms 39 ms be2434.ccr41.ams03.atlas.cogentco.com [130.117.2.242]
19 53 ms 55 ms 54 ms be2182.ccr21.lpl01.atlas.cogentco.com [154.54.77.246]
20 122 ms 122 ms 122 ms be3042.ccr21.ymq01.atlas.cogentco.com [154.54.44.162]
21 138 ms 139 ms 141 ms be3259.ccr31.yyz02.atlas.cogentco.com [154.54.41.205]
22 137 ms 139 ms 138 ms be2993.ccr21.cle04.atlas.cogentco.com [154.54.31.225]
23 140 ms 138 ms 139 ms be2717.ccr41.ord01.atlas.cogentco.com [154.54.6.221]
24 166 ms 159 ms 156 ms be2831.ccr21.mci01.atlas.cogentco.com [154.54.42.165]
25 161 ms 161 ms 163 ms be3035.ccr21.den01.atlas.cogentco.com [154.54.5.89]
26 174 ms 174 ms 250 ms be3037.ccr21.slc01.atlas.cogentco.com [154.54.41.145]
27 191 ms 191 ms 191 ms be3109.ccr21.sfo01.atlas.cogentco.com [154.54.44.137]
28 193 ms 192 ms 192 ms be2015.ccr31.sjc04.atlas.cogentco.com [154.54.7.174]
29 250 ms 255 ms 241 ms 38.104.140.134
30 363 ms 341 ms 345 ms 112.174.87.13

Trace complete.

 

3. DSL status 

 

DSL STATUS
This page shows information about your DSL connection. If you are using Fibre/Ethernet Broadband then this page is not applicable.
STATUS
Configured Current
Line Status -- UP
Link Type -- Fast Path
Operation Mode Automatic G.992.5 (ADSL2+)
DATA RATE INFORMATION
Upstream 992 (Kbps)
Downstream 19292 (Kbps)
DEFECT/FAILURE INDICATION
Operation Data Upstream Downstream
Noise Margin 5.9 (dB) 3.3 (dB)
Line Attenuation 7.4 (dB) 16.0 (dB)

Indicator Name Near End Indicator Far End Indicator
Output Power 11.9 (dBm) 20.8 (dBm)
Fast Path FEC Correction 0 0
Interleaved Path FEC Correction -- --
Fast Path CRC Error 0 0
Interleaved Path CRC Error -- --
Loss Of Signal Defect 1 0
Fast Path HEC Error STR 708 7185
Interleaved Path HEC Error -- --
Error Seconds 6728 1676
STATISTICS
Received Data 19586763 (Kbits)
Transmitted Data 3274058 (Kbits)

 

4. System log

 

10:19:54, 09 Jan. Time is synced to NTP server
09:19:36, 09 Jan. Time is synced to NTP server
08:19:19, 09 Jan. Time is synced to NTP server
07:19:01, 09 Jan. Time is synced to NTP server
06:18:44, 09 Jan. Time is synced to NTP server
05:18:26, 09 Jan. Time is synced to NTP server
04:17:59, 09 Jan. Time is synced to NTP server
03:17:42, 09 Jan. Time is synced to NTP server
02:17:24, 09 Jan. Time is synced to NTP server
01:17:07, 09 Jan. Time is synced to NTP server
00:16:50, 09 Jan. Time is synced to NTP server
23:16:32, 08 Jan. Time is synced to NTP server
22:16:14, 08 Jan. Time is synced to NTP server
21:15:46, 08 Jan. Time is synced to NTP server
21:15:14, 08 Jan. admin login success from 192.168.1.109
21:02:41, 08 Jan. Device connected: 192.168.1.207, 54:e4:3a:32:58:18, Tinas, lease time is 172800 seconds
20:15:29, 08 Jan. Time is synced to NTP server
19:44:20, 08 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
19:34:56, 08 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
19:34:11, 08 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
19:20:51, 08 Jan. Device connected: 192.168.1.109, 64:6e:69:95:ee:e1, DESKTOP-7B5LP92, lease time is 172800 seconds
19:15:11, 08 Jan. Time is synced to NTP server
19:05:03, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
19:01:41, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:58:18, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:54:53, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:51:28, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:48:06, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:32:02, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:28:38, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:24:31, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:21:08, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:17:42, 08 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:14:53, 08 Jan. Time is synced to NTP server
17:53:47, 08 Jan. Device connected: 192.168.1.207, 54:e4:3a:32:58:18, Tinas, lease time is 172800 seconds
17:14:36, 08 Jan. Time is synced to NTP server
16:14:18, 08 Jan. Time is synced to NTP server
15:14:01, 08 Jan. Time is synced to NTP server
14:13:43, 08 Jan. Time is synced to NTP server
13:13:26, 08 Jan. Time is synced to NTP server
12:13:08, 08 Jan. Time is synced to NTP server
11:12:51, 08 Jan. Time is synced to NTP server
10:12:33, 08 Jan. Time is synced to NTP server
09:55:31, 08 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
09:12:16, 08 Jan. Time is synced to NTP server
08:24:43, 08 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
08:11:58, 08 Jan. Time is synced to NTP server
07:11:41, 08 Jan. Time is synced to NTP server
06:11:24, 08 Jan. Time is synced to NTP server
05:11:06, 08 Jan. Time is synced to NTP server
04:10:49, 08 Jan. Time is synced to NTP server
03:56:34, 08 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
03:10:31, 08 Jan. Time is synced to NTP server
02:10:14, 08 Jan. Time is synced to NTP server
01:09:56, 08 Jan. Time is synced to NTP server
00:38:38, 08 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
00:09:39, 08 Jan. Time is synced to NTP server
23:09:21, 07 Jan. Time is synced to NTP server
22:09:03, 07 Jan. Time is synced to NTP server
21:08:46, 07 Jan. Time is synced to NTP server
20:08:28, 07 Jan. Time is synced to NTP server
19:09:43, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
19:08:11, 07 Jan. Time is synced to NTP server
19:06:19, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
19:02:55, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:59:33, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:56:08, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:52:43, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:48:40, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:17:07, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:13:45, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:10:21, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:07:53, 07 Jan. Time is synced to NTP server
18:06:59, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:03:35, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
18:02:47, 07 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
18:01:23, 07 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
18:00:13, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
17:31:31, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
17:27:53, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
17:24:31, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
17:21:07, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
17:17:42, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
17:14:18, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
17:10:56, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
17:07:36, 07 Jan. Time is synced to NTP server
16:39:33, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
16:36:29, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
16:33:04, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
16:29:39, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
16:26:17, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
16:22:53, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
16:22:07, 07 Jan. Device connected: 192.168.1.109, 64:6e:69:95:ee:e1, DESKTOP-7B5LP92, lease time is 172800 seconds
16:19:29, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
16:16:07, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
16:07:18, 07 Jan. Time is synced to NTP server
16:06:44, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
15:56:41, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
15:51:56, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
15:48:30, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
15:45:05, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
15:41:05, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
15:41:03, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
15:33:55, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
15:07:00, 07 Jan. Time is synced to NTP server
15:03:50, 07 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
14:23:28, 07 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
14:06:43, 07 Jan. Time is synced to NTP server
13:56:07, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
13:53:42, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
13:50:18, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
13:46:56, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
13:43:33, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
13:40:09, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
13:36:44, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
13:20:21, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
13:08:18, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
13:06:26, 07 Jan. Time is synced to NTP server
13:04:54, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
13:01:31, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
12:58:10, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
12:54:45, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
12:44:23, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
12:41:00, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
12:37:38, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
12:34:14, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
12:08:10, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
12:06:08, 07 Jan. Time is synced to NTP server
12:05:53, 07 Jan. PPP connection up (ADSL)
12:05:52, 07 Jan. PPP: IPCP up
12:05:51, 07 Jan. PPP: CHAP authentication succeeded
12:05:51, 07 Jan. PPP: LCP up
12:05:47, 07 Jan. PPP: Starting PPP daemon
12:05:46, 07 Jan. WAN link up (ADSL)
12:05:40, 07 Jan. WAN link down (ADSL)
12:05:38, 07 Jan. PPP connection down (ADSL)
12:05:27, 07 Jan. PPP: Stopped PPP daemon(0,1,5)
12:05:21, 07 Jan. PPP: IPCP down
12:05:21, 07 Jan. PPP: LCP down
11:58:48, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
11:53:03, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
11:39:09, 07 Jan. Time is synced to NTP server
11:27:19, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
11:23:54, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
11:20:47, 07 Jan. Device connected: 192.168.1.223, 0c:47:c9:35:7c:12, amazon-4c8132f06, lease time is 172800 seconds
10:38:51, 07 Jan. Time is synced to NTP server
09:38:34, 07 Jan. Time is synced to NTP server
08:38:17, 07 Jan. Time is synced to NTP server
07:37:59, 07 Jan. Time is synced to NTP server
06:37:42, 07 Jan. Time is synced to NTP server
05:37:24, 07 Jan. Time is synced to NTP server
04:37:07, 07 Jan. Time is synced to NTP server
03:36:50, 07 Jan. Time is synced to NTP server
02:42:27, 07 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
02:36:22, 07 Jan. Time is synced to NTP server
02:20:10, 07 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
01:36:04, 07 Jan. Time is synced to NTP server
00:35:47, 07 Jan. Time is synced to NTP server
23:35:57, 06 Jan. Device connected: 192.168.1.109, 64:6e:69:95:ee:e1, DESKTOP-7B5LP92, lease time is 172800 seconds
23:35:30, 06 Jan. Time is synced to NTP server
23:35:14, 06 Jan. PPP connection up (ADSL)
23:35:14, 06 Jan. PPP: IPCP up
23:35:12, 06 Jan. PPP: CHAP authentication succeeded
23:35:12, 06 Jan. PPP: LCP up
23:35:08, 06 Jan. Device connected: 192.168.1.142, 34:a3:95:3b:9d:84, Ipad-liverpool, lease time is 172800 seconds
23:35:07, 06 Jan. PPP: Starting PPP daemon
23:35:02, 06 Jan. System up, firmware version: v0.00.14.0001-OT (Wed Jun 24 19:52:22 2015)
23:35:02, 06 Jan. WAN link up (ADSL)
23:34:03, 06 Jan. System start

 

5. Wired speed test (all other results based on wifi) 

 

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

 

6. Exchange 

 

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

 

Notes - 

 

I logged in WoW at 12.47pm and had 873ms (home) and 873ms (world) making the game unplayable.

Then when I did the tracert at 12.54 I re-logged into WoW afterwards and had 34ms (home) and 33ms (world)

 

CS:GO was showing no signs of in game lag and was working faultless.

 

Any Ideas?

 

Will repeat tests this evening during peak hours.

 

Thanks

 

Highlighted
by Contributor
Contributor

Re: Gaming Lag - New to EE

Quickley re-logged into WoW to see if it was still lagging at 13.22pm and it was! so i did another tracert whilst it was like this .

 

Microsoft Windows [Version 10.0.16299.192]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\Adam>tracert 80.239.179.95

Tracing route to 80-239-179-95.customer.teliacarrier.com [80.239.179.95]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms BrightBox.ee [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 60 ms 13 ms 15 ms 213.1.128.237
5 525 ms 1003 ms 920 ms 213.1.78.34
6 197 ms 273 ms 988 ms 87.237.20.128
7 1014 ms 21 ms 19 ms 80.150.169.13
8 33 ms 33 ms 33 ms 62.157.249.202
9 35 ms 32 ms 32 ms ldn-bb3-link.telia.net [62.115.138.150]
10 37 ms 36 ms 36 ms adm-bb3-link.telia.net [213.155.136.99]
11 38 ms 38 ms 38 ms adm-b5-link.telia.net [62.115.140.115]
12 36 ms 35 ms 36 ms 80-239-205-133.customer.teliacarrier.com [80.239.205.133]
13 36 ms 37 ms 36 ms 80-239-205-133.customer.teliacarrier.com [80.239.205.133]
14 38 ms 44 ms 37 ms a23-36-230-1.deploy.static.akamaitechnologies.com [23.36.230.1]
15 * * * Request timed out.
16 * * * Request timed out.
17 40 ms 39 ms 39 ms be1299.agr21.ams03.atlas.cogentco.com [130.117.14.101]
18 40 ms 38 ms 38 ms be2440.ccr42.ams03.atlas.cogentco.com [130.117.50.5]
19 52 ms 50 ms 50 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58.69]
20 121 ms 122 ms 121 ms be3043.ccr22.ymq01.atlas.cogentco.com [154.54.44.166]
21 139 ms 138 ms 138 ms be3260.ccr32.yyz02.atlas.cogentco.com [154.54.42.89]
22 139 ms 140 ms 139 ms be2994.ccr22.cle04.atlas.cogentco.com [154.54.31.233]
23 143 ms 140 ms 140 ms be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129]
24 156 ms 157 ms 156 ms be2832.ccr22.mci01.atlas.cogentco.com [154.54.44.169]
25 165 ms 163 ms 163 ms be3036.ccr22.den01.atlas.cogentco.com [154.54.31.89]
26 174 ms 174 ms 173 ms be3038.ccr21.slc01.atlas.cogentco.com [154.54.42.97]
27 193 ms 193 ms 192 ms be3109.ccr21.sfo01.atlas.cogentco.com [154.54.44.137]
28 192 ms 192 ms 191 ms be2015.ccr31.sjc04.atlas.cogentco.com [154.54.7.174]
29 237 ms 238 ms 239 ms 38.104.140.134
30 344 ms 360 ms 354 ms 112.174.87.13

Trace complete.

C:\Users\Adam>

 

 

Thanks

Highlighted
by Grand Master
Grand Master

Re: Gaming Lag - New to EE

Please now try pathping to both those sites, but I suspect they will terminate too early to tell us anything.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE: The local rate landline number +44 207 362 0200 or Freephone +44 800 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 => 2014: EE 20 Meg WBC
Highlighted
by Contributor
Contributor

Re: Gaming Lag - New to EE

1. WoW pathping 

 

C:\Users\Adam>pathping 80.239.179.95

Tracing route to 80-239-179-95.customer.teliacarrier.com [80.239.179.95]
over a maximum of 30 hops:
0 DESKTOP-7B5LP92.default [192.168.1.109]
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 DESKTOP-7B5LP92.default [192.168.1.109]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% BrightBox.ee [192.168.1.1]

Trace complete.

C:\Users\Adam>

 

2. CSGO pathping 

 

C:\Users\Adam>pathping 155.133.242.183

Tracing route to 155.133.242.183 over a maximum of 30 hops

0 DESKTOP-7B5LP92.default [192.168.1.109]
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 DESKTOP-7B5LP92.default [192.168.1.109]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% BrightBox.ee [192.168.1.1]

Trace complete.

C:\Users\Adam>

 

 

Thanks 

Adam

 

 

 

Highlighted
by Grand Master
Grand Master

Re: Gaming Lag - New to EE

As I suspected they terminate prematurely to tell us anything. Fortunately mine goes much further:

C:\>pathping 155.133.242.183

Tracing route to 155.133.242.183 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.58
  5  87.237.20.136
  6  87.237.20.32
  7  80.150.169.13
  8  62.157.249.202
  9  ldn-bb3-link.telia.net [213.155.136.60]
 10  hbg-bb1-link.telia.net [80.91.249.11]
 11  s-bb3-link.telia.net [80.91.249.9]
 12  s-b5-link.telia.net [62.115.141.203]
 13  valve-ic-314988-s-b5.c.telia.net [62.115.62.226]
 14     *        *        *
Computing statistics for 325 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    7ms     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   10ms     0/ 100 =  0%     0/ 100 =  0%  213.1.79.58
                                0/ 100 =  0%   |
  5   11ms     0/ 100 =  0%     0/ 100 =  0%  87.237.20.136
                                0/ 100 =  0%   |
  6   11ms     0/ 100 =  0%     0/ 100 =  0%  87.237.20.32
                                0/ 100 =  0%   |
  7   10ms     0/ 100 =  0%     0/ 100 =  0%  80.150.169.13
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%   100/ 100 =100%  62.157.249.202
                                0/ 100 =  0%   |
  9   26ms     0/ 100 =  0%     0/ 100 =  0%  ldn-bb3-link.telia.net [213.155.136.60]
                                0/ 100 =  0%   |
 10   43ms     0/ 100 =  0%     0/ 100 =  0%  hbg-bb1-link.telia.net [80.91.249.11]
                                0/ 100 =  0%   |
 11   47ms     0/ 100 =  0%     0/ 100 =  0%  s-bb3-link.telia.net [80.91.249.9]
                                0/ 100 =  0%   |
 12   43ms     0/ 100 =  0%     0/ 100 =  0%  s-b5-link.telia.net [62.115.141.203]
                                0/ 100 =  0%   |
 13   45ms     0/ 100 =  0%     0/ 100 =  0%  valve-ic-314988-s-b5.c.telia.net [62.115.62.226]

Trace complete.

WoW does the same at the same node.

 

This is similar to issues we have had before with delays to gaming sites. At the Deutsche Telekom node, 62.157.249.202, you are experiencing 100% packet loss. This will be 1 of EE's peering partners with whom they have an agreement to pass on Net traffic from EE.

 

All you can do is report it to EE. There is a so-called "email" form that you can use for BB: https://explore.ee.co.uk/broadband/email-us . Also see below in my sig.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE: The local rate landline number +44 207 362 0200 or Freephone +44 800 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 => 2014: EE 20 Meg WBC
Highlighted
by Contributor
Contributor

Re: Gaming Lag - New to EE

Thanks very much xrayspecx,

 

So is this just something I will encounter on and off all the time at random intervals?

 

Also would changing ISP help me to achieve a stable connection again?

 

I doubt emailing EE sayng about my packet loss will make them change their peering partners, as this seems like the sort of thing they will just shun off.

 

Thanks

Adam

Highlighted
by Grand Master
Grand Master

Re: Gaming Lag - New to EE

From past experience it doesn't go away until EE and/or DT do something about it, which they did after many complaints from here. The last instance between June & Nov. 2017 was Experiencing random packet loss . Even now 1 of those affected, @Noodelzz, has come back to say it's reoccurring.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE: The local rate landline number +44 207 362 0200 or Freephone +44 800 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 => 2014: EE 20 Meg WBC
Highlighted
by Contributor
Contributor

Re: Gaming Lag - New to EE

Thanks,

 

Well I have an EE engineer coming out on thursday to my home to see if he can fix the issue, but now I know what it is I may cancel that visit and cancel my contract with EE and move elsewhere as I am still in the cooling off period thankfully.

 

Thanks again

Adam

Highlighted
by
EE Community Support Team

Re: Gaming Lag - New to EE

Hi @Rainbo911

 

Thank you for coming here again 🙂

 

Let's see what the engineer visit brings and we can go from there.

 

Please keep us updated.

 

Richard

 

🙂

Highlighted
by Contributor
Contributor

Re: Gaming Lag - New to EE

Hi Richard,

 

Thank you for your reply,

 

Ok Ill see what the engineer says but im not confident he can fix the issue as its an EE infastructure issue with their peering partners by the sounds of it, and an engineer isnt going to have the ability to change that ;).

 

Strangely last night I didnt have any issues during peak hours, which is ironic since I have been active on this forum the issue has gone and come back less frequently but looking at previous posts it seems this issue comes and goes and I will not feel comfortable sitting on an 18 month contract knowing this issue could come back at any time.

 

Thanks 

Adam

 

 

Highlighted
by
EE Community Support Team

Re: Gaming Lag - New to EE

Hi @Rainbo911

 

Thanks for coming back 🙂

 

Monitor it and hopefully it's on an upward curve, I do know how annoying it is when a game runs slow.

 

I was playing football online and before I knew it, I was a goal behind as my screen froze as my player Lionel Messi was passing the ball.

 

The game caught up and that cheeky Cristiano Ronaldo had scored against me.

 

Keep me posted as to how you get on.

 

Hope you stay with us.

 

Thanks

 

Richard

 

🙂

 

 

Highlighted
by Investigator
Investigator

Re: Gaming Lag - New to EE

Hi would like to add I’m experiencing the exact same issue happened in November too but got fixed for a while, ping is always stable but get packet loss which make most games unplayable. Explaining this issue over the phone to them does not help when most of them are out of ideas when you say your on a wired connection and also emailing the tech team they told me it was issue with me and the game server I was trying to play on(when it was happening on every game And every server I tried) I’ll be switching my connection if this doesn’t get fixed soon been on EE/orange/Wanadoo/Freeserve for The duration I’ve had internet and when I’m not getting this packet loss I’m completly satisfied with my connection.

Highlighted
by Contributor
Contributor

Re: Gaming Lag - New to EE

Hi dfly,

 

The issue is so frustrating isnt it, my connection has been fine for the last 2 days, however I am worried of being stuck in an 18 month contract and this happenning again, as you have already pointed out it was fixed before but now is reoccuring. 

 

Yes I dont think anyone we can get in contact with at EE can help us as its a deal they have made with peering partners so no engineer or technical advisor can help with that.

 

Also yes explaining this issue over phone is pretty much useless as they can only do their over the phone tests which will not detect packet loss or high latency.

 

I have an engineer coming this morning (Doubt he can do much) as its that douchbag telicom node causing the packet loss. However I will feedback what he says later on :). 

 

Thanks 

Highlighted
by Grand Master
Grand Master

Re: Gaming Lag - New to EE

Peering partners and hosts is a very specialised area and needs escalating to probably a single specialist within EE. Hence my suggestion that you all set the ball rolling by bombarding the BB Team using the BB 'email' form. It worked before.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE: The local rate landline number +44 207 362 0200 or Freephone +44 800 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 => 2014: EE 20 Meg WBC

Can't find what you're looking for?

One of these options may help you find the answers you need.

Let's get started

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