Menu
Reply
  • 1
  • 0
  • 0
TheRenton
Joining in
575 Views
Message 1 of 2
Flag for a moderator

Eve Online Routing

Been having the connection dropouts for a couple of weeks now, strangely enough after I upgraded to 150mb. However, delving into this deeper I can see issues with the routing from me to the EVE Online server on IP 82.237.38.200, hops 3 and 4 no response, see below:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 481 | 481 | 0 | 0 | 11 | 0 |
| cpc4-yead2-2-0-gw.7-1.cable.virginm.net - 0 | 481 | 481 | 6 | 10 | 213 | 14 |
|leed-core-2a-ae3-1556.network.virginmedia.net - 0 | 481 | 481 | 7 | 10 | 41 | 15 |
| No response from host - 100 | 96 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 96 | 0 | 0 | 0 | 0 | 0 |
|brhm-bb-1c-ae0-0.network.virginmedia.net - 9 | 358 | 327 | 0 | 14 | 45 | 14 |
| tcl5-ic-2-ae0-0.network.virginmedia.net - 6 | 390 | 367 | 0 | 17 | 41 | 16 |
| linx-6k-1.routers.proxad.net - 3 | 446 | 437 | 13 | 18 | 86 | 14 |
|amsterdam-6k-1-po100.intf.routers.proxad.net - 1 | 478 | 477 | 20 | 24 | 35 | 22 |
|bzn-crs16-2-be1122.intf.routers.proxad.net - 0 | 481 | 481 | 29 | 35 | 57 | 29 |
|lille-9k-1-be2001.intf.routers.proxad.net - 0 | 481 | 481 | 31 | 35 | 49 | 32 |
| asc59-1.dslg.proxad.net - 1 | 477 | 476 | 0 | 34 | 46 | 35 |
| asc59-1-82-237-38-200.fbx.proxad.net - 1 | 477 | 476 | 0 | 58 | 71 | 60 |
|________________________________________________|______|______|______|______

Must be a routing issue near Virginmedia's routes surely?

 

Chris

Tags (2)
0 Kudos
  • 14.35K
  • 640
  • 1.44K
Moderator
Moderator
76 Views
Message 2 of 2
Flag for a moderator

Re: Eve Online Routing

Hi Renton,

 

Hops 3 and 4 are a red herring. In any MTR or traceroute if some hops aren't responding but the following hops return a good latency then those hops are either set not to respond or are busy and ping requests are a low priority. 

The whole route looks healthy with no hops looking to be the cause of an issue. 

Was this performed while you were experiencing the drop out or while it was working normally?


The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos