Pages: [1] 2 :: one page |
Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Wizzkidy
|
Posted - 2005.09.02 17:13:00 -
[1]
Hiya all,
I hope this is ok to post but I feel I need to get this of my chest...
I logged a "issue" through the EVE website for the horrible packet loss I am getting on the 23rd of last month.
I was asked to provide "pingplotter traces" which I done for the GM's which showed horrible packet loss 3 hops and down to the EVE server and I was also getting major time outs (and still am to 157.157.139.10)
After providing this information to the GM's I was asked to provide a DXdiag as well (fair enough I thought but how does that help you investigate my packet loss? ) but I done it anyway and provided this.
I was then asked to run the "log server" while I play and send them that which I done also.
At this point I was told it could well be my ISP (even though the packet loss starts 3 hops away from the main server) but fair enough I gave NTL a ring but as far as they could see it was not there issue and I advised the GM's of this.
I was then asked AGAIN to provide MORE ping plotter information which I have done and I also made them aware of the thread running on the forum about packet loss (now fallen a couple of pages down)
Thats as far as it got and its now been sitting as "updated" for 2 days!?!
Now is it just me who thinks this is a little silly? Surly they can investigate this issue and packet loss from there end? I have had no responce back saying they are.
At some point I don't think my account wil stay active because this lag is annoying....
Ahh feel much better now :) got that of me chest - I'm not that miffed but jesus it feels like im going round and round all thet time! :D
/rant over.
W.
|

Braaage
|
Posted - 2005.09.02 17:19:00 -
[2]
Logically speaking it's more likely your end or ISP since we'd all be experiencing packet loss if it was a problem at EVE servers end. ___________________________________________ http://www.eve-tutor.com
Picture based tutorial site for EVE-Online *New - Building an Outpost |

Wizzkidy
|
Posted - 2005.09.02 17:20:00 -
[3]
I dont understand how it can be
look here I'm no expert but does this look like an ISP issue considering its hopping all the way through NTL (my ISP) without an issue?
|

Al Giordino
|
Posted - 2005.09.02 17:23:00 -
[4]
Edited by: Al Giordino on 02/09/2005 17:23:06 Just fougnt a company for two days about a dyfunctional t1....
only took 2 days to pound it in their head that it wasnt the frame-relay t1. it was the ppp t1. Incompetence ftw!
:D
just start smoking and drinking now. It helps.
|

Braaage
|
Posted - 2005.09.02 17:24:00 -
[5]
Well I'm on a different ISP so the route is different but out of 5 tracerts I got the same results:
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms RobCop.RobSheff [192.168.1.1] 2 8 ms 8 ms 9 ms 10.165.0.1 3 8 ms 13 ms 11 ms gsr01-sh.blueyonder.co.uk [62.30.241.65] 4 17 ms 16 ms 14 ms 172.18.16.57 5 58 ms 19 ms 17 ms 172.18.16.34 6 24 ms 37 ms 19 ms 194.117.136.169 7 16 ms 26 ms 20 ms 194.117.136.166 8 16 ms 17 ms 16 ms tele2-usgw.telewest.net [194.117.136.197] 9 17 ms 15 ms 41 ms LINX-gw12.LON.GB.NET.DTAG.DE [62.159.199.41] 10 106 ms 82 ms 83 ms 62.156.131.157 11 148 ms 146 ms 147 ms 212.184.27.102 12 101 ms 105 ms 105 ms ls-bb-gw2.isholf.is [157.157.173.253] 13 109 ms 105 ms 106 ms 157.157.139.10
Trace complete.
/me wonders what/where 62.156.131.157 is..... ___________________________________________ http://www.eve-tutor.com
Picture based tutorial site for EVE-Online *New - Building an Outpost |

Wizzkidy
|
Posted - 2005.09.02 17:24:00 -
[6]
Understandable that they might be busy and I can understand that but this is so not a problem my ISP end imo.
|

Wizzkidy
|
Posted - 2005.09.02 17:27:00 -
[7]
Originally by: Braaage snip
Braaage,
Yes same here but I want to get to the bottom of this and with no responce from the GM's for awhile I'm starting to wonder if they have just ignored my update :/
W.
|

Al Giordino
|
Posted - 2005.09.02 17:30:00 -
[8]
Edited by: Al Giordino on 02/09/2005 17:32:45 hop 10 10 106 ms 82 ms 83 ms 62.156.131.157 OrgName: RIPE Network Coordination Centre OrgID: RIPE City: Amsterdam Country: NL
hop 9 9 17 ms 15 ms 41 ms LINX-gw12.LON.GB.NET.DTAG.DE [62.159.199.41] OrgName: RIPE Network Coordination Centre OrgID: RIPE City: Amsterdam Country: NL
Braage. That answers that question.
|

Thnikkaman
|
Posted - 2005.09.02 17:38:00 -
[9]
If there's anyone reading this outside of the UK, could you use this program and post your results?
Thanks. _____________________________________________/ *Here comes the Thnikkaman!*
Yeah! Shut up kid! |

Wizzkidy
|
Posted - 2005.09.02 17:48:00 -
[10]
Originally by: Thnikkaman If there's anyone reading this outside of the UK, could you use this program and post your results?
Thanks.
Yes please do as it would be good to see a different route and to see if the problem exisits from there.
|

Seth Killbain
|
Posted - 2005.09.02 18:33:00 -
[11]
Edited by: Seth Killbain on 02/09/2005 18:33:25 Its not your isp, its also most prob not EVE. It is most prob BT. I give up.
2 20 ms 20 ms 19 ms thus2-hg2.ealing.broadband.bt.net [217.32.137.20 1] 3 21 ms 19 ms 22 ms 217.32.137.130 4 26 ms 22 ms 20 ms 217.32.137.234 5 21 ms 20 ms 20 ms park-inside-1-g5-1-0-s193.router.demon.net [194. 159.246.66] 6 23 ms 22 ms 23 ms tele-border-1-g4-0-0.router.demon.net [194.70.98 .190] 7 23 ms 24 ms 22 ms ldn-b1-geth11-1-15.telia.net [213.248.100.161] 8 27 ms 22 ms 23 ms ldn-bb1-pos6-1-0.telia.net [213.248.65.237] 9 27 ms 22 ms 23 ms ldn-b1-pos3-0.telia.net [213.248.74.6] 10 22 ms 23 ms 23 ms ge-4-0-0-zcr1.lnt.cw.net [195.66.226.20] 11 23 ms 22 ms 23 ms so-1-2-0-dcr1.tsd.cw.net [195.2.10.126] 12 24 ms 22 ms 23 ms so-4-0-0-bcr3.tsd.cw.net [195.2.10.97] 13 23 ms 24 ms 25 ms iar2.tsd.cw.net [166.63.210.23] 14 23 ms 23 ms 22 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 15 23 ms 23 ms 23 ms 157.157.62.26 16 25 ms 27 ms 28 ms 157.157.139.10
|

The Hanz
|
Posted - 2005.09.02 18:38:00 -
[12]
Don't worry. I've had an exploit petetion evaluated by a regular GM and has now been waiting for a Senior GM repsonse for about a week now. And that's for an exploit.
|

Kylania
|
Posted - 2005.09.02 19:07:00 -
[13]
Gah, this scares me since my cable modem routes through those ridicliously bad Cable and Wireless trans-atlantic routers too. :(
Hope I can play this weekend. :)
-- Lil Miner |

Dark Shikari
|
Posted - 2005.09.02 19:10:00 -
[14]
You should try checking for packetloss instead of ping. -- Proud member of the [23].
Selling Capital Cargo Bays and Kernite Mining Crystal IIs, cheaper than anyone else. |

Messerschmitt facility
|
Posted - 2005.09.02 19:13:00 -
[15]
Edited by: Messerschmitt facility on 02/09/2005 19:18:10 Edited by: Messerschmitt facility on 02/09/2005 19:17:31 Edited by: Messerschmitt facility on 02/09/2005 19:17:11 Omg people have 25ms with the server... no wonder they wtfpwn in 1v1 frig class fights... Or they scramble people before they even see themself in the warping process...
Btw like mine?
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 8 ms 9 ms 8 ms 10.95.56.1 2 8 ms 15 ms 6 ms gw03-vlan201.wlfdle.phub.net.cable.rogers.com [6 6.185.90.161] 3 14 ms 7 ms 7 ms gw01.wlfdle.phub.net.cable.rogers.com [66.185.93 .65] 4 8 ms 8 ms 8 ms gw02.bloor.phub.net.cable.rogers.com [66.185.80. 142] 5 8 ms 8 ms 13 ms gw01.ym.phub.net.cable.rogers.com [66.185.83 ] 6 31 ms 29 ms 29 ms igw01.ny8th.phub.net.cable.rogers.com [66.185.81 .13] 7 * * * Request timed out. 8 110 ms 105 ms 106 ms so-2-0-0-dcr2.tsd.cw.net [195.2.10.110] 9 110 ms 107 ms 105 ms so-5-0-0-bcr3.tsd.cw.net [195.2.10.101] 10 106 ms * 105 ms iar2.tsd.cw.net [166.63.210.23] 11 105 ms 114 ms 105 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 12 108 ms 105 ms 107 ms 157.157.62.26 13 106 ms 105 ms 109 ms 157.157.139.10
Trace complete.
_________________________________
A conclusion is the place where you got tired of thinking...
|

Wizzkidy
|
Posted - 2005.09.02 19:46:00 -
[16]
The pingplotter above was from a few days ago and here is another
Here
:(
|

Magnum VII
|
Posted - 2005.09.02 20:11:00 -
[17]
All I can say is that I was tech support once (4 years) for another company of course and thatĘs how it is every ware in the world with any person in tech support E-Mail or Phone or whatever.
And yes it is silly and all the above.
It's just how it works out, they all start off easy on customers when the business 1st starts up & then get more and more tight until it get ridicules.
I promises you the people on the phone wish they did not have to put you through the ringer.
The best you could do is do everything they say as fast as you can.
Sometimes as ridicules as it is, somehow the problem gets fixed.
And sometimes you just go crazy & never deal with them again.
If it does not get fixed then reinstall everything and call me back tomorrow when I'm not working, thank you for calling...
|

Amazoph
|
Posted - 2005.09.02 20:31:00 -
[18]
look at mine.. really slow ping time at hop 21
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 * * * Request timed out. 2 11 ms 11 ms 11 ms esr7.edinburgh5.broadband.bt.net [217.32.78.146]
3 11 ms 11 ms 12 ms 217.32.78.13 4 11 ms 11 ms 17 ms 217.41.218.1 5 12 ms 13 ms 13 ms 217.41.174.122 6 11 ms 11 ms 11 ms 217.41.218.34 7 12 ms 12 ms 12 ms 217.32.78.59 8 12 ms 11 ms 11 ms core1-pos8-0.edinburgh.ukcore.bt.net [194.72.17. 157] 9 19 ms 19 ms 18 ms core1-pos15-2.birmingham.ukcore.bt.net [194.74.1 6.241] 10 21 ms 20 ms 21 ms core1-pos13-2.reading.ukcore.bt.net [62.6.196.10 6] 11 22 ms 22 ms 23 ms core1-pos14-0.ilford.ukcore.bt.net [62.6.204.17]
12 22 ms 22 ms 22 ms transit2-pos3-0.ilford.ukcore.bt.net [194.72.20. 250] 13 23 ms 23 ms 23 ms t2c2-p1-0.uk-ilf.eu.bt.net [166.49.168.101] 14 23 ms 22 ms 22 ms t2c1-p8-0.uk-lon1.eu.bt.net [166.49.208.2] 15 22 ms 23 ms 23 ms t2a4-ge0-0.uk-lon1.eu.bt.net [166.49.135.98] 16 23 ms 23 ms 23 ms 166-49-211-18.eu.bt.net [166.49.211.18] 17 24 ms 24 ms 24 ms so-1-2-0-dcr1.tsd.cw.net [195.2.10.126] 18 24 ms 23 ms 23 ms so-4-0-0-bcr1.tsd.cw.net [195.2.10.57] 19 24 ms 24 ms 23 ms iar2.tsd.cw.net [166.63.210.23] 20 24 ms 23 ms 23 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 21 177 ms 268 ms 218 ms 157.157.62.26 22 24 ms 24 ms 25 ms 157.157.139.10
|

Moominer
|
Posted - 2005.09.02 21:01:00 -
[19]
From those shots it is pretty clear the problem is past NTL's peerage with C&W.
Contacting both your ISP and EVE support should result in this being fixed *eventually* - your ISP can and should get in touch with C&W to get the routers sorted.
You may wake up one day and find it all sorted anyway, these things do tend to get fixed after a while.
Anyway, I would recommend downloading and using WinMTR [winmtr.sourceforge.net] instead of pingplotter. It provides continuous better output of both ping and packetless for the whole route.
|

Emeline Cabernet
|
Posted - 2005.09.02 21:07:00 -
[20]
i read the headline and thought about a gymsock.. dunno why..
|

Wizzkidy
|
Posted - 2005.09.02 23:04:00 -
[21]
Originally by: Moominer snip
My thoughts exactly but the only reason I used ping plotter is because they asked me too. I know this is not a problem with my ISP but all I want is a responce saying "We know and are trying to sort it out" or "Ok this isn't a problem with your ISP but its not a problem our end"
I pay monthly for this game and I expect to be given a decent service not random time outs here there and everywhere
My account wont last unless its resolved asap tbh.
|

Joshua Foiritain
|
Posted - 2005.09.02 23:26:00 -
[22]
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 * * * Request timed out. 2 7 ms 9 ms 9 ms 10.105.128.1 3 13 ms 13 ms 13 ms atm11-0.ah00rt03.brain.upc.nl [212.142.23.65] 4 24 ms 14 ms 14 ms 213.46.183.57 5 14 ms 13 ms 13 ms 213.46.183.102 6 15 ms 15 ms 15 ms 213.46.183.78 7 15 ms 19 ms 16 ms zpr2.amt.cw.net [195.69.145.144] 8 17 ms 15 ms 16 ms so-3-0-0-bcr1.amd.cw.net [208.173.211.237] 9 16 ms 15 ms 17 ms so-1-3-0-dcr2.amd.cw.net [195.2.10.30] 10 21 ms 24 ms 23 ms so-4-0-0-dcr1.tsd.cw.net [195.2.10.146] 11 36 ms 31 ms 31 ms so-4-0-0-bcr3.tsd.cw.net [195.2.10.97] 12 23 ms 23 ms 23 ms iar2.tsd.cw.net [166.63.210.23] 13 23 ms 23 ms 37 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 14 25 ms 24 ms 24 ms 157.157.62.26 15 22 ms 24 ms 24 ms 157.157.139.10
Trace complete.
Located in The Netherlands, Chello is my ISP. ------------------
[Coreli Corporation Mainframe] |

Aitrus
|
Posted - 2005.09.02 23:41:00 -
[23]
Edited by: Aitrus on 02/09/2005 23:41:51
Quote: Tracing route to 157.157.139.10 over a maximum of 30 hops
1 9 ms 2 ms 2 ms 192.168.0.1 2 12 ms 12 ms 12 ms 65.14.252.21 3 14 ms 13 ms 13 ms 65.14.252.137 4 14 ms 14 ms 13 ms adsl-156-253-29.bct.bellsouth.net [66.156.253.29] 5 13 ms 16 ms 12 ms AXR01BCT-0-1-3.bellsouth.net [65.83.237.102] 6 32 ms 31 ms 31 ms axr00asm-0-3-0.bellsouth.net [65.83.236.12] 7 33 ms 33 ms 33 ms pxr00asm-0-0-0.bellsouth.net [65.83.236.0] 8 33 ms 32 ms 33 ms so-7-0-0-0.gar1.Atlanta1.Level3.net [67.72.8.41] 9 33 ms 34 ms 33 ms ae-1-51.bbr1.Atlanta1.Level3.net [4.68.103.1] 10 49 ms 48 ms 48 ms as-1-0.bbr1.Washington1.Level3.net [4.68.128.201] 11 48 ms 49 ms 45 ms ge-7-2.hsa2.Washington1.Level3.net [4.68.121.138] 12 50 ms 49 ms 70 ms ALLINSON-COM.hsa2.Level3.net [63.215.131.22] 13 53 ms 55 ms 52 ms so-7-0-0-dcr1.nyk.cw.net [195.2.3.2] 14 127 ms 125 ms 126 ms so-2-0-0-dcr2.tsd.cw.net [195.2.10.110] 15 129 ms 128 ms 127 ms so-5-0-0-bcr3.tsd.cw.net [195.2.10.101] 16 130 ms 129 ms 129 ms iar2.tsd.cw.net [166.63.210.23] 17 129 ms 129 ms 128 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 18 130 ms 129 ms 128 ms 157.157.62.26 19 129 ms 128 ms 128 ms 157.157.139.10
Trace complete.
More than likely it is not your ISP. Also, more than likely it is not Eve. More than likely it is somewhere in between. Thats why it's nasty. Many companies own the various pieces of equiment you route through. If it isn't owned by your ISP, there is very little they can do besides complain and hope. Same from CCP's end.
It sucks, but that is the nature of the internet.
|

Alerce
|
Posted - 2005.09.02 23:50:00 -
[24]
C:\WINDOWS\system32>tracert 157.157.139.10
Bezig met het traceren van de route naar 157.157.139.10 via maximaal 30 hops
1 9 ms 1 ms 1 ms ****** 2 6 ms 5 ms 6 ms ****** 3 8 ms 8 ms 8 ms ****** 4 8 ms 8 ms 8 ms 217.149.47.113 5 8 ms 9 ms 9 ms sl-bb21-ams-8-0.sprintlink.net [217.149.32.41] 6 16 ms 16 ms 16 ms sl-bb23-lon-4-0.sprintlink.net [213.206.129.143]
7 16 ms 16 ms 15 ms sl-gw23-lon-15-0.sprintlink.net [213.206.128.63]
8 16 ms 16 ms 16 ms sle-cwa-1-0.sprintlink.net [82.195.191.162] 9 16 ms 16 ms 19 ms so-1-2-0-dcr2.tsd.cw.net [195.2.10.130] 10 16 ms 16 ms 16 ms so-5-0-0-bcr1.tsd.cw.net [195.2.10.61] 11 17 ms 16 ms 17 ms iar2.tsd.cw.net [166.63.210.23] 12 17 ms 17 ms 16 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 13 17 ms 16 ms 16 ms 157.157.62.26 14 17 ms 17 ms 17 ms 157.157.139.10
De trace is voltooid.
This is from spot in the netherlands.
|

Zed Nash
|
Posted - 2005.09.03 01:00:00 -
[25]
Ping Plotter shows problems in cw.net, Cable and Wireless, based on of the UK. Tracert from the States goes through the same servers, so this is likely the backbone provider for CCP's service provider. The 157 IPs are Iceland Telecom, direct provider to CCP.
If packet loss is occuring at hop 8, it will continue on the rest of the hops until the destination. The problem is not with CCP or their provider, but with Cable and Wireless, CCP's provider's provider.
Causes can be anything from overutilization of a backbone switch, to regional issues requiring a reroute of customers through that regional server, to anything really.
If it's something affecting all their user's, they will be fixing it. If it's affecting only a small number of users during peaks hours, they probably won't.
Unfortunately, CCP's hands are tied. I work for a telcom myself, and getting your backbone provider to resolve single-customer issues is an exercise in futility. Backbone providers have thousands, if not millions, of customers. Only large-scale issues are considered problems.
|

Zed Nash
|
Posted - 2005.09.03 01:17:00 -
[26]
Also, please keep in mind that pings and tracerts are poor measures of actual packet loss and/or latency. ICMP is low-priority traffic, and their packets are frequently dropped in favor of actual data traffic.
|

Spleef
|
Posted - 2005.09.03 03:02:00 -
[27]
Tracing route to eve [157.157.139.10] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1 2 18 ms 15 ms 15 ms lo1-lon3-adsl21.nildram.net [195.112.5.30] 3 14 ms 14 ms 14 ms lon3-14.nildram.net [84.12.224.25] 4 14 ms 14 ms 15 ms ldn-b3-geth5-1.telia.net [213.248.100.29] 5 14 ms 15 ms 14 ms ldn-bb1-pos6-1-0.telia.net [213.248.65.237] 6 15 ms 14 ms 14 ms ldn-b1-pos3-0.telia.net [213.248.74.6] 7 47 ms 14 ms 14 ms ge-4-0-0-zcr1.lnt.cw.net [195.66.226.20] 8 14 ms 15 ms 13 ms so-1-2-0-dcr1.tsd.cw.net [195.2.10.126] 9 15 ms 14 ms 14 ms so-4-0-0-bcr1.tsd.cw.net [195.2.10.57] 10 14 ms 15 ms 15 ms iar2.tsd.cw.net [166.63.210.23] 11 15 ms 15 ms 15 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 12 15 ms 15 ms 14 ms 157.157.62.26 13 15 ms 15 ms 14 ms eve [157.157.139.10]
Trace complete.
Using high speed ADSL in UK...
|

Kahlan Savage
|
Posted - 2005.09.03 03:38:00 -
[28]
Aren't the servers in new york?
|

Spy4Hire
|
Posted - 2005.09.03 03:44:00 -
[29]
I would do a tracert, but I only know how to do that via the dos prompt that shuts off as soon as the trace is complete.
But I watched it until the window closed, and was getting 175ms steady for the final 12 or so hops.
|

Sumica
|
Posted - 2005.09.03 04:17:00 -
[30]
So like what program, are you useing to find all this out?
Kind of hard to test the results if eery one uses difrent ways to test them.
Your not stupid just misinformed Ö
|
|
|
Pages: [1] 2 :: one page |
First page | Previous page | Next page | Last page |