by Arcziii Valued Contributor
Valued Contributor

Loosing connection to gaming servers

Hello, i'm experiencing connection drops on gaming servers using UDP protocol connection only. In-game statistics show me 10-50% packetloss. I've turned off all firewalls, and didnot help at all. Checked the servers on mobile internet and works fine.

C:\Users\Artur>tracert net4game.com

Tracing route to net4game.com [151.80.108.72]
over a maximum of 30 hops:

  1     1 ms     1 ms     2 ms  eehub.home [xxx]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     8 ms     7 ms     8 ms  a213-1-121-13.imsnet3.btopenworld.com [213.1.121.13]
  5    40 ms    35 ms    31 ms  213.121.98.10
  6    19 ms    18 ms    18 ms  87.237.20.128
  7     *        *        *     Request timed out.
  8    26 ms    24 ms    46 ms  be100-1042.rbx-g2-nc5.fr.eu [213.251.130.102]
  9    35 ms    34 ms    35 ms  be100-1047.fra-5-a9.de.eu [94.23.122.241]
 10    41 ms    38 ms    38 ms  be101.sbg-g2-nc5.fr.eu [91.121.215.196]
 11     *        *        *     Request timed out.
 12    43 ms    44 ms    59 ms  be50-7.sbg-4b-a9.fr.eu [188.165.9.76]
 13    38 ms    37 ms    39 ms  net4game.com [151.80.108.72]

Trace complete.

C:\Users\Artur>ping net4game.com -n 20

Pinging net4game.com [151.80.108.72] with 32 bytes of data:
Reply from 151.80.108.72: bytes=32 time=39ms TTL=51
Reply from 151.80.108.72: bytes=32 time=39ms TTL=51
Reply from 151.80.108.72: bytes=32 time=38ms TTL=51
Reply from 151.80.108.72: bytes=32 time=38ms TTL=51
Reply from 151.80.108.72: bytes=32 time=39ms TTL=51
Reply from 151.80.108.72: bytes=32 time=38ms TTL=51
Reply from 151.80.108.72: bytes=32 time=38ms TTL=51
Reply from 151.80.108.72: bytes=32 time=44ms TTL=51
Reply from 151.80.108.72: bytes=32 time=38ms TTL=51
Reply from 151.80.108.72: bytes=32 time=39ms TTL=51
Reply from 151.80.108.72: bytes=32 time=39ms TTL=51
Reply from 151.80.108.72: bytes=32 time=39ms TTL=51
Reply from 151.80.108.72: bytes=32 time=39ms TTL=51
Reply from 151.80.108.72: bytes=32 time=39ms TTL=51
Reply from 151.80.108.72: bytes=32 time=40ms TTL=51
Reply from 151.80.108.72: bytes=32 time=38ms TTL=51
Reply from 151.80.108.72: bytes=32 time=39ms TTL=51
Reply from 151.80.108.72: bytes=32 time=38ms TTL=51
Reply from 151.80.108.72: bytes=32 time=38ms TTL=51
Reply from 151.80.108.72: bytes=32 time=42ms TTL=51

Ping statistics for 151.80.108.72:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 38ms, Maximum = 44ms, Average = 39ms

C:\Users\Artur>pathping net4game.com

Tracing route to net4game.com [151.80.108.72]
over a maximum of 30 hops:
  0  Artur-PC.home [xxx]
  1  eehub.home [xxx]
  2     *        *        *
Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Artur-PC.home [xxx]
                                0/ 100 =  0%   |
  1    6ms     0/ 100 =  0%     0/ 100 =  0%  eehub.home [xxx]

Trace complete.

Thats all for one of the servers i'm trying to connect and winmtr logs:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              eehub.home -    0 |   26 |   26 |    1 |    3 |   25 |    3 |
|                   No response from host -  100 |    5 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    5 |    0 |    0 |    0 |    0 |    0 |
|   a213-1-121-13.imsnet3.btopenworld.com -    0 |   26 |   26 |    7 |    9 |   22 |    7 |
|                           213.121.98.10 -    0 |   26 |   26 |   17 |   20 |   47 |   20 |
|                           87.237.20.128 -    0 |   26 |   26 |   17 |   20 |   45 |   17 |
|                   No response from host -  100 |    5 |    0 |    0 |    0 |    0 |    0 |
|             be100-1042.rbx-g2-nc5.fr.eu -    0 |   26 |   26 |   22 |   36 |  124 |   25 |
|               be100-1047.fra-5-a9.de.eu -    0 |   26 |   26 |   33 |   36 |   49 |   34 |
|                  be101.sbg-g2-nc5.fr.eu -    0 |   26 |   26 |   36 |   39 |   54 |   36 |
|                   No response from host -  100 |    5 |    0 |    0 |    0 |    0 |    0 |
|                  be50-7.sbg-4b-a9.fr.eu -    0 |   26 |   26 |   35 |   38 |   52 |   38 |
|                            net4game.com -    0 |   26 |   26 |   37 |   40 |   55 |   38 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

And for bbc.co.uk:

C:\Users\Artur>tracert bbc.co.uk

Tracing route to bbc.co.uk [151.101.64.81]
over a maximum of 30 hops:

  1     7 ms     1 ms     1 ms  eehub.home [xxx]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    52 ms     8 ms     8 ms  a213-1-121-13.imsnet3.btopenworld.com [213.1.121.13]
  5    22 ms    20 ms    25 ms  213.1.78.58
  6    36 ms    18 ms    18 ms  87.237.20.128
  7    19 ms    20 ms    19 ms  lag-107.ear1.London1.Level3.net [212.187.166.145]
  8    21 ms    22 ms    21 ms  ae-1-3112.edge6.London1.Level3.net [4.69.141.246]
  9    53 ms    71 ms    64 ms  FASTLY-INC.edge6.London1.Level3.net [212.113.9.202]
 10    22 ms    21 ms    21 ms  151.101.64.81

Trace complete.

C:\Users\Artur>ping bbc.co.uk -n 20

Pinging bbc.co.uk [151.101.64.81] with 32 bytes of data:
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=24ms TTL=56
Reply from 151.101.64.81: bytes=32 time=25ms TTL=56
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=23ms TTL=56
Reply from 151.101.64.81: bytes=32 time=23ms TTL=56
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=30ms TTL=56
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=21ms TTL=56
Reply from 151.101.64.81: bytes=32 time=40ms TTL=56
Reply from 151.101.64.81: bytes=32 time=23ms TTL=56
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=22ms TTL=56
Reply from 151.101.64.81: bytes=32 time=27ms TTL=56

Ping statistics for 151.101.64.81:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 40ms, Average = 23ms

C:\Users\Artur>pathping bbc.co.uk

Tracing route to bbc.co.uk [151.101.64.81]
over a maximum of 30 hops:
  0  Artur-PC.home [xxx]
  1  eehub.home [xxx]
  2     *        *        *
Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Artur-PC.home [xxx]
                                0/ 100 =  0%   |
  1    8ms     0/ 100 =  0%     0/ 100 =  0%  eehub.home [xxx]

Trace complete.
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              eehub.home -    0 |   26 |   26 |    1 |    2 |   11 |    2 |
|                   No response from host -  100 |    5 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    5 |    0 |    0 |    0 |    0 |    0 |
|   a213-1-121-13.imsnet3.btopenworld.com -    0 |   26 |   26 |    7 |   10 |   54 |   54 |
|                             213.1.78.58 -    0 |   26 |   26 |   19 |   20 |   33 |   20 |
|                           87.237.20.128 -    0 |   26 |   26 |   18 |   23 |   39 |   24 |
|         lag-107.ear1.London1.Level3.net -    0 |   26 |   26 |   18 |   20 |   35 |   19 |
|      ae-1-3112.edge6.London1.Level3.net -    0 |   26 |   26 |   18 |   20 |   36 |   20 |
|     FASTLY-INC.edge6.London1.Level3.net -    0 |   26 |   26 |   19 |   21 |   33 |   20 |
|                           151.101.64.81 -    0 |   26 |   26 |   21 |   22 |   36 |   22 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

And winmtr for google.co.uk 

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              eehub.home -    0 |   26 |   26 |    1 |    4 |   28 |    1 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|   a213-1-121-13.imsnet3.btopenworld.com -    0 |   26 |   26 |    7 |   12 |   32 |    9 |
|                             213.1.78.58 -    0 |   26 |   26 |   19 |   24 |   63 |   21 |
|                           87.237.20.128 -    0 |   26 |   26 |   18 |   27 |   60 |   19 |
|                           74.125.52.216 -    0 |   26 |   26 |   19 |   26 |   71 |   19 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                           216.239.46.12 -    0 |   26 |   26 |   21 |   28 |   73 |   22 |
|                         108.170.246.143 -    0 |   26 |   26 |   20 |   26 |   72 |   21 |
|                          216.239.57.237 -    0 |   26 |   26 |   20 |   27 |   63 |   30 |
|                            72.14.237.52 -    0 |   26 |   26 |   20 |   25 |   62 |   20 |
|                           74.125.242.97 -    0 |   26 |   26 |   20 |   26 |   64 |   20 |
|                          209.85.249.219 -    0 |   26 |   26 |   19 |   25 |   64 |   21 |
|                lhr35s07-in-f3.1e100.net -    0 |   26 |   26 |   18 |   25 |   71 |   19 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Is no response from so many hosts normal?

28 REPLIES 28
by
EE Community Support Team

Re: Loosing connection to gaming servers

Hi @Arcziii.

 

Welcome to the community. 

 

How long have you been experiencing this?

 

Have you spoke with our Home Broadband technical team?

 

Speak soon, Katie 🙂

by Arcziii Valued Contributor
Valued Contributor

Re: Loosing connection to gaming servers

I've not been using any application operating udp protocols. I started using it last week and thats when the problem appeared. Phoned EE, they said that they send a message to BT, to fix the problem. But i'm not really sure, that BT will do anything.

by
EE Community Support Team

Re: Loosing connection to gaming servers

Thanks for coming back to me @Arcziii

 

Did they provide any further steps or any time scales?

 

Katie 🙂

by Arcziii Valued Contributor
Valued Contributor

Re: Loosing connection to gaming servers

They said that someone from BT will contact me this week. Hope someone will come in tomorrow, as i will not be available during their work hours for another two weeks Smiley LOL .

Do you know what might be the problem?

by
EE Community Support Team

Re: Loosing connection to gaming servers

Unfortunately not @Arcziii

 

You definitely have done the right thing by speaking with that department, fingers crossed they are in touch soon. 

 

Keep us updated 🙂

 

Katie

by Grand Master
Grand Master

Re: Loosing connection to gaming servers

It's nowt to do with BT. It'll be entirely down to EE's and its peering partners' routing. I'll take a dekko at it when I get back from my meal. 

__________________________________________________________________________________________
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
by Arcziii Valued Contributor
Valued Contributor

Re: Loosing connection to gaming servers

I've seen that problem so many times on this forum. Do they never check peering parners? Suppose that check of peering partners would not be very expensive-thats my 5th internet provider in uk, and i never had any problems like this.

by Grand Master
Grand Master

Re: Loosing connection to gaming servers


@Arcziii wrote:

Is no response from so many hosts normal?


For a few hosts, not many, it is quite normal. Some servers have far better things to do than responding to your probes, like providing their normal service. A few of these will just de-prioritise their response. Others will just ignore your probes. The latter are the ones you see as "Request timed out" with 100% packet loss. That doesn't mean they are losing packets on the way with your communication to your final target; just that the probes to themselves are lost.

 

  • Steps 2-5 of your trace is within the BTw backhaul & are nowt to worry about. Altho' I am surprised that step 4 is to btopenworld.com ; mine doesn't.
  • Step 6 is where BTw hands off to the EE network.
  • Step 7 is also probably EE.
  • Steps 8-12 is the route within France to your final target.

BTW: bbc.co.uk is not the real BBC for some reason. It is a site in San Francesco belonging to Fastly.com . The real BBC is bbc.com.

__________________________________________________________________________________________
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
by Arcziii Valued Contributor
Valued Contributor

Re: Loosing connection to gaming servers

Looks like worst customer experience ever. No one has contacted me yet. Problem has not been solved, so i will have to phone them on monday again.

by
EE Community Support Team

Re: Loosing connection to gaming servers

Hi @Arcziii

 

Thanks for coming back to us.

 

I am very sorry to hear no one has contacted you.

 

Our broadband team are open until 9pm tonight and 8am-8pm over the weekend to get this looked into.

 

Thanks, Leanne.

by Arcziii Valued Contributor
Valued Contributor

Re: Loosing connection to gaming servers

I just spoke to them again. They said that everything has been checked and is working fine. so my 50% loosing packets comes from nowhere Smiley LOL . I felt like the person i speak to have no idea what am i talking about. He was completely clueless. If it's a well-knows problem at EE with peering partners why do they never know what to do?

Phoning them again hope someone else will pick up this time.

by Grand Master
Grand Master

Re: Loosing connection to gaming servers

Trouble is I don't see the usual suspect Deutsche Telekom peering partner node in your route.

 

You could try & get round this issue by switching the DNS in the router away from EE's ones to Manual with 1 of these public DNS:

OpenDNS   :	208.67.222.222 & 208.67.220.220
Google DNS:	8.8.8.8 & 8.8.4.4 
Cloudflare DNS 1.1.1.1 & 1.0.0.1 Norton DNS: 198.153.192.40 & 198.153.194.40

This has worked for other users experiencing gaming lagging & discons. I guess it may take a diff route to your gaming server, avoiding the culprit.

__________________________________________________________________________________________
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
by Arcziii Valued Contributor
Valued Contributor

Re: Loosing connection to gaming servers

Tried every each one of them-No difference. Stays on 50% packetloss, and then connection with the server drops. I've been told that they can book me an engineer, but if he will not find any fault at my home, they will charge me 50 pounds. How can they tell me if i have a connection problem? If i have it i can see it, right?

by Arcziii Valued Contributor
Valued Contributor

Re: Loosing connection to gaming servers

Okay, after two weeks of having this problem i plugged it into lan socket, and now it showed 0% packetloss. And still have 50% packetloss over wifi. Last week when i tried to connect internet over cable it didnot make any difference. My modem is in kitchen, 1 meter away from electric hob and 3 meters away from the fridge. Wifi extender doesnot make any difference again. Also no difference in connection with distance from the router.

by Arcziii Valued Contributor
Valued Contributor

Re: Loosing connection to gaming servers

Update: Tried to move the modem to living room, didnot make any difference. Works well over a lan cable, doesnot work on wifi. Tried different wireless modes, different channel and the problem is still there. And again on mobile broadband works fine over wifi. Is it faulty modem?

by
EE Community Support Team

Re: Loosing connection to gaming servers

Hi @Arcziii,

 

It's a possibility @Arcziii. Please get in touch with customer services so we can run through some diagnostics with you.

 

Thanks

 

James

by Grand Master
Grand Master

Re: Loosing connection to gaming servers

Do you mean a modem or a combined modem/router (the usual router supplied by ISPs)? Which one?

__________________________________________________________________________________________
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
by Arcziii Valued Contributor
Valued Contributor

Re: Loosing connection to gaming servers

It's the newest EE smart hub(combined modem/router). Is it possible to connect a sky hub someway? I've found out that my old sky hub does have backup settings that i can edit manually in notepad++, but i can see there is only username and no password for internet connection, and the username says default-username, so i'm not 100% sure if i can do it there.

by Grand Master
Grand Master

Re: Loosing connection to gaming servers

If it has no BB pwd slot it's useless for EE BB. You could try & use it as a WAP connected to the EE SH.

__________________________________________________________________________________________
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.