EVE Search - CTD's today?

All Channels

EVE General Discussion

CTD's today?

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 18 .. 18 :: one page
Author	Thread Statistics \| Show CCP posts - 6 post(s)
Tyleritus	Posted - 2005.10.18 12:58:00 - [181] Tracing route to 157.157.139.10 over a maximum of 30 hops 1 * * 4431 ms ********** 2 11 ms 12 ms 11 ms leic-t2cam1-b-v104.inet.ntl.com [82.3.35.217] 3 25 ms 10 ms 11 ms leic-t2core-b-ge-220-0.inet.ntl.com [82.3.33.138 ] 4 75 ms 13 ms 12 ms nth-bb-b-so-230-0.inet.ntl.com [62.253.188.114] 5 16 ms 13 ms 15 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117] 6 29 ms 14 ms 28 ms gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98] 7 98 ms 19 ms 18 ms so-2-0-0-bcr1.tsd.cw.net [166.63.211.149] 8 39 ms 18 ms 16 ms iar2.tsd.cw.net [166.63.210.23] 9 30 ms 17 ms 19 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 10 23 ms 16 ms 23 ms 157.157.62.26 11 19 ms 44 ms 18 ms 157.157.139.252 12 21 ms 18 ms 17 ms 157.157.139.10 Trace complete. Yet again i have been disconnected, so DT didnt solve any problems, could th devs plz post a complaint procedure so I could try for some sort of compnsation this is now beyond a joke. One Family...One Goal...One Future Adeptus Gattacus The Way Forword
Sayden	Posted - 2005.10.18 14:36:00 - [182] You can add people from New York, New Jersey, and California in the United States to the list of worldwide customers effected. Sayden
Diomorph	Posted - 2005.10.18 14:39:00 - [183] Tracing route to 157.157.39.10 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.0.254 2 16 ms 16 ms 16 ms bthg312-hg1.miltonkeynes.broadband.bt.net [217.35.194.200] 3 18 ms 17 ms 17 ms 217.35.194.130 4 18 ms 19 ms 18 ms 217.35.194.238 5 44 ms 119 ms 36 ms 217.47.201.122 6 30 ms 24 ms 21 ms 217.41.219.1 7 18 ms 19 ms 18 ms 217.41.175.182 8 18 ms 18 ms 17 ms 217.41.219.34 9 19 ms 18 ms 19 ms 217.47.220.91 10 18 ms 18 ms 19 ms core2-pos14-3.bletchley.ukcore.bt.net [194.72.31.109] 11 19 ms 19 ms 19 ms core2-pos11-3.ealing.ukcore.bt.net [62.6.204.33] 12 20 ms 19 ms 18 ms transit1-pos4-0.ealing.ukcore.bt.net [194.72.9.238] 13 20 ms 18 ms 19 ms t2c1-p5-0.uk-eal.eu.bt.net [166.49.168.9] 14 20 ms 20 ms 20 ms t2c2-p8-0.uk-lon1.eu.bt.net [166.49.208.110] 15 21 ms 20 ms 20 ms t2a5-ge0-0.uk-lon1.eu.bt.net [166.49.135.123] 16 20 ms 20 ms 20 ms 166-49-214-130.eu.bt.net [166.49.214.130] 17 20 ms 20 ms 20 ms isp-linx-gw13-o.nmc-m.dtag.de [217.239.38.241] 18 20 ms 20 ms 19 ms 62.153.203.190 19 * * 168 ms 157.157.55.226 20 59 ms * * 157.157.55.226 21 * * * Request timed out. 22 * * * Request timed out. oh dear :(
Kerushi	Posted - 2005.10.18 14:47:00 - [184] Edited by: Kerushi on 18/10/2005 14:49:50 Tracing route to 157.157.139.10 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms SUN [**] 2 6 ms 6 ms 6 ms ** 3 19 ms 8 ms 8 ms iawxsrt-dc2-bb21a.wxs.nl [213.75.1.165] 4 7 ms 7 ms 7 ms asd2-rou-1011.NL.eurorings.net [134.222.97.9] 5 9 ms 9 ms 10 ms ledn-rou-1001.NL.eurorings.net [134.222.230.77] 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 16 ms 9 ms 9 ms zpr2.amt.cw.net [195.69.145.144] 10 9 ms 9 ms 9 ms so-3-0-0-bcr1.amd.cw.net [208.173.211.237] 11 10 ms 9 ms 9 ms so-1-3-0-dcr2.amd.cw.net [195.2.10.30] 12 23 ms 16 ms 15 ms so-4-0-0-dcr1.tsd.cw.net [195.2.10.146] 13 16 ms 19 ms 16 ms so-4-0-0-bcr1.tsd.cw.net [195.2.10.57] 14 16 ms 16 ms 16 ms iar2.tsd.cw.net [166.63.210.23] 15 16 ms 15 ms 16 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 16 16 ms 17 ms 16 ms 157.157.62.26 17 17 ms 16 ms 18 ms 157.157.139.252 18 17 ms 17 ms 17 ms 157.157.139.10 yet again i have no more lag then anyone else and no ctd`s (neither yesterday) traceroute from my server gives this tho: traceroute to 157.157.139.10 (157.157.139.10), 30 hops max, 38 byte packets 1 **** (**) 6.620 ms 5.619 ms 5.345 ms 2 iawxsrt-dc2-bb21a.wxs.nl (213.75.1.165) 6.863 ms 7.084 ms 7.199 ms 3 asd2-rou-1011.NL.eurorings.net (134.222.97.9) 6.722 ms 6.827 ms 7.959 ms 4 ledn-rou-1001.NL.eurorings.net (134.222.230.77) 7.856 ms 7.980 ms 8.041 ms MPLS Label=223488 CoS=0 TTL=1 S=1 5 * * 6 * * * 7 * * * 8 zpr2.amt.cw.net (195.69.145.144) 57.836 ms 7.930 ms 8.729 ms 9 so-3-0-0-bcr1.amd.cw.net (208.173.211.237) 8.754 ms 9.456 ms 9.260 ms 10 * so-1-3-0-dcr2.amd.cw.net (195.2.10.30) 8.000 ms 13.451 ms 11 so-4-0-0-dcr1.tsd.cw.net (195.2.10.146) 14.737 ms 14.804 ms 15.161 ms 12 so-4-0-0-bcr3.tsd.cw.net (195.2.10.97) 15.432 ms 15.112 ms 21.977 ms 13 iar2.tsd.cw.net (166.63.210.23) 15.861 ms 15.894 ms 15.951 ms 14 iceland-telecom1.tsd.cw.net (166.63.214.198) 15.873 ms 15.784 ms 224.828 ms 15 157.157.62.26 (157.157.62.26) 16.439 ms 16.793 ms 16.142 ms 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * steady ping tho: Reply from 157.157.139.10: bytes=32 time=16ms TTL=240 Reply from 157.157.139.10: bytes=32 time=16ms TTL=240 Reply from 157.157.139.10: bytes=32 time=16ms TTL=240 Reply from 157.157.139.10: bytes=32 time=16ms TTL=240 Ping statistics for 157.157.139.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 16ms, Average = 16ms PING 157.157.139.10 (157.157.139.10) 56(84) bytes of data. 64 bytes from 157.157.139.10: icmp_seq=0 ttl=241 time=16.9 ms 64 bytes from 157.157.139.10: icmp_seq=1 ttl=241 time=16.4 ms 64 bytes from 157.157.139.10: icmp_seq=2 ttl=241 time=16.8 ms 64 bytes from 157.157.139.10: icmp_seq=3 ttl=241 time=17.2 ms 64 bytes from 157.157.139.10: icmp_seq=4 ttl=241 time=16.2 ms 64 bytes from 157.157.139.10: icmp_seq=5 ttl=241 time=16.1 ms 64 bytes from 157.157.139.10: icmp_seq=6 ttl=241 time=17.7 ms 64 bytes from 157.157.139.10: icmp_seq=7 ttl=241 time=16.0 ms 64 bytes from 157.157.139.10: icmp_seq=8 ttl=241 time=16.4 ms 64 bytes from 157.157.139.10: icmp_seq=9 ttl=241 time=16.3 ms --- 157.157.139.10 ping statistics --- 25 packets transmitted, 25 received, 0% packet loss, time 24021ms rtt min/avg/max/mdev = 16.026/17.028/22.771/1.261 ms, pipe 2
Ikvar	Posted - 2005.10.18 14:48:00 - [185] Sucks really, if this was a problem at CCPs end (which I believe it isn't) then they probably would have fixed it by now. Originally by: Berneh You will never take me aliv coppers
Spleef	Posted - 2005.10.18 14:48:00 - [186] Tracing route to eve [157.157.139.10] over a maximum of 30 hops: 1 3 ms <1 ms <1 ms 192.168.0.1 2 15 ms 16 ms 16 ms lo1-lon3-adsl21.nildram.net [195.112.5.30] 3 16 ms 16 ms 16 ms lon3-14.nildram.net [84.12.224.25] 4 14 ms 14 ms 16 ms ldn-b3-geth5-1.telia.net [213.248.100.29] 5 15 ms 16 ms 15 ms ldn-bb1-pos6-1-0.telia.net [213.248.65.237] 6 15 ms 16 ms 15 ms ldn-b1-pos3-0.telia.net [213.248.74.6] 7 16 ms 17 ms 16 ms ge-4-0-0-zcr1.lnt.cw.net [195.66.226.20] 8 17 ms 17 ms 16 ms so-1-2-0-dcr1.tsd.cw.net [195.2.10.126] 9 18 ms 16 ms 17 ms so-4-0-0-bcr3.tsd.cw.net [195.2.10.97] 10 26 ms 18 ms 19 ms iar2.tsd.cw.net [166.63.210.23] 11 17 ms 17 ms 17 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 12 18 ms 17 ms 17 ms 157.157.62.26 13 18 ms 17 ms 18 ms 157.157.139.252 14 18 ms 17 ms 18 ms eve [157.157.139.10] Trace complete. Nildram FTW :)
Jacobus Archilles	Posted - 2005.10.18 14:57:00 - [187] Bloody Hell!! I wish I read the forums before logging on. Just lost my Raven with Arbies, E500 Nos's, nice BCS etc etc due to CTD whilst taking on 3 Dread Pith Destroyers. This just ain't on ffs!!!!!!!! Tracing route to 157.157.139.10 over a maximum of 30 hops 1 12 ms 15 ms 15 ms BigPond.bigpond [10.0.0.138] 2 31 ms 30 ms 31 ms 172.29.29.152 3 31 ms 31 ms 30 ms 172.31.173.98 4 31 ms 31 ms 31 ms CPE-61-9-243-5.wa.bigpond.net.au [61.9.243.5] 5 31 ms 18 ms 31 ms 61.9.241.8 6 240 ms 218 ms 202 ms GigabitEthernet4-1.Pie2.Perth.telstra.net [139.1 30.25.93] 7 29 ms 30 ms 31 ms GigabitEthernet5-0.pie-core1.Perth.telstra.net [ 203.50.115.193] 8 61 ms 62 ms 46 ms Pos-channel2.fli-core1.Adelaide.telstra.net [203 .50.6.181] 9 57 ms 61 ms 62 ms 10GigabitEthernet5-0.way-core4.Adelaide.telstra. net [203.50.6.10] 10 62 ms 77 ms 62 ms Pos5-0.exi-core1.Melbourne.telstra.net [203.50.6 .161] 11 78 ms 85 ms 77 ms Pos15-0.chw-core2.Sydney.telstra.net [203.50.6.3 7] 12 75 ms 77 ms 77 ms 10GigabitEthernet1-0.oxf-core1.Sydney.telstra.ne t [203.50.6.2] 13 86 ms 77 ms 77 ms 10GigabitEthernet6-0.syd-core04.Sydney.net.reach .com [203.50.13.34] 14 78 ms 77 ms 77 ms i-10-0.syd-core03.net.reach.com [202.84.221.85] 15 203 ms 200 ms 202 ms i-2-1.tok-core02.net.reach.com [202.84.249.169] 16 203 ms 187 ms 202 ms i-1-0.tok07.net.reach.com [202.84.219.58] 17 468 ms 484 ms 479 ms unknown.net.reach.com [134.159.125.82] 18 484 ms 481 ms 483 ms linx-gw13.LON.GB.net.DTAG.DE [62.154.5.38] 19 484 ms 484 ms 484 ms 62.153.203.190 20 431 ms 437 ms 423 ms 157.157.62.26 21 434 ms * 433 ms 157.157.139.252 22 437 ms 427 ms 436 ms 157.157.139.10 Trace complete.
Jacobus Archilles	Posted - 2005.10.18 14:58:00 - [188] Bloody Hell!! I wish I read the forums before logging on. Just lost my Raven with Arbies, E500 Nos's, nice BCS etc etc due to CTD whilst taking on 3 Dread Pith Destroyers. This just ain't on ffs!!!!!!!! Tracing route to 157.157.139.10 over a maximum of 30 hops 1 12 ms 15 ms 15 ms BigPond.bigpond [10.0.0.138] 2 31 ms 30 ms 31 ms 172.29.29.152 3 31 ms 31 ms 30 ms 172.31.173.98 4 31 ms 31 ms 31 ms CPE-61-9-243-5.wa.bigpond.net.au [61.9.243.5] 5 31 ms 18 ms 31 ms 61.9.241.8 6 240 ms 218 ms 202 ms GigabitEthernet4-1.Pie2.Perth.telstra.net [139.1 30.25.93] 7 29 ms 30 ms 31 ms GigabitEthernet5-0.pie-core1.Perth.telstra.net [ 203.50.115.193] 8 61 ms 62 ms 46 ms Pos-channel2.fli-core1.Adelaide.telstra.net [203 .50.6.181] 9 57 ms 61 ms 62 ms 10GigabitEthernet5-0.way-core4.Adelaide.telstra. net [203.50.6.10] 10 62 ms 77 ms 62 ms Pos5-0.exi-core1.Melbourne.telstra.net [203.50.6 .161] 11 78 ms 85 ms 77 ms Pos15-0.chw-core2.Sydney.telstra.net [203.50.6.3 7] 12 75 ms 77 ms 77 ms 10GigabitEthernet1-0.oxf-core1.Sydney.telstra.ne t [203.50.6.2] 13 86 ms 77 ms 77 ms 10GigabitEthernet6-0.syd-core04.Sydney.net.reach .com [203.50.13.34] 14 78 ms 77 ms 77 ms i-10-0.syd-core03.net.reach.com [202.84.221.85] 15 203 ms 200 ms 202 ms i-2-1.tok-core02.net.reach.com [202.84.249.169] 16 203 ms 187 ms 202 ms i-1-0.tok07.net.reach.com [202.84.219.58] 17 468 ms 484 ms 479 ms unknown.net.reach.com [134.159.125.82] 18 484 ms 481 ms 483 ms linx-gw13.LON.GB.net.DTAG.DE [62.154.5.38] 19 484 ms 484 ms 484 ms 62.153.203.190 20 431 ms 437 ms 423 ms 157.157.62.26 21 434 ms * 433 ms 157.157.139.252 22 437 ms 427 ms 436 ms 157.157.139.10 Trace complete.
spRAYed	Posted - 2005.10.18 14:59:00 - [189] Originally by: Ikvar Sucks really, if this was a problem at CCPs end (which I believe it isn't) then they probably would have fixed it by now. Ehm....i doubt it. I'm sure CCP is the best out there service wise...but i dont think they have seen all problems that could turn up yet. If this would have happend before with that many people not being able to play....it would have been sorted already. Its most likely one of the Devs that accidenlty pushed the "Crash + Cause loads of nasty troubble" button on Verone's Modified Dev Keyboards. ----------------------------------------- It can, 400x120x24000 bytes Max -Capsicum
Dale Cussler	Posted - 2005.10.18 15:00:00 - [190] That 157.157.62.26 seems to be the bottleneck where it all goes to hell and back though. ICEnet? /Dale
Strongbow	Posted - 2005.10.18 15:08:00 - [191] 12 23 ms 255 ms 271 ms 157.157.62.26 Same problem here started over the weekend and continues today really starting to get boring sitting in stations. come on CCP start jumping up and down on your transit providers to either fix the problem or reroute some traffic.
Ditchdoctor	Posted - 2005.10.18 15:18:00 - [192] Well. Its been a day and Im still crashing. Id like to petition the lose of my ship but I cant becase the damn system disconnects when I open the petition area in game.
Kerushi	Posted - 2005.10.18 15:25:00 - [193] Originally by: Dale Cussler That 157.157.62.26 seems to be the bottleneck where it all goes to hell and back though. ICEnet? looks like it but it`s rather selective at who gets screwed over PING 157.157.62.26 (157.157.62.26) 56(84) bytes of data. 64 bytes from 157.157.62.26: icmp_seq=0 ttl=241 time=29.0 ms 64 bytes from 157.157.62.26: icmp_seq=1 ttl=241 time=28.4 ms 64 bytes from 157.157.62.26: icmp_seq=2 ttl=241 time=28.4 ms 64 bytes from 157.157.62.26: icmp_seq=3 ttl=241 time=31.7 ms 64 bytes from 157.157.62.26: icmp_seq=4 ttl=241 time=29.2 ms 64 bytes from 157.157.62.26: icmp_seq=5 ttl=241 time=29.4 ms 64 bytes from 157.157.62.26: icmp_seq=6 ttl=241 time=30.9 ms 64 bytes from 157.157.62.26: icmp_seq=7 ttl=241 time=35.9 ms 64 bytes from 157.157.62.26: icmp_seq=8 ttl=241 time=29.2 ms NL planet.nl, no lag nor ctd`s better ask the owner of that machine to check if rats have been scewing on some of the cables
Saranda	Posted - 2005.10.18 15:26:00 - [194] 1 <1 ms <1 ms <1 ms localhost [192.168.1.1] 2 9 ms 9 ms 9 ms dslb-084-058-000-001.pools.arcor-ip.net [84.58.0 .1] 3 9 ms 9 ms 9 ms ffm-145-254-0-237.arcor-ip.net [145.254.0.237] 4 15 ms 15 ms 15 ms bln-145-254-18-46.arcor-ip.net [145.254.18.46] 5 15 ms 16 ms 15 ms bln-145-254-17-66.arcor-ip.net [145.254.17.66] 6 21 ms 21 ms 21 ms 62.156.139.153 7 37 ms 38 ms 38 ms linx-gw13.LON.GB.net.DTAG.DE [62.154.5.38] 8 37 ms 37 ms 37 ms 62.153.203.190 9 114 ms 258 ms 232 ms 157.157.62.26 10 39 ms 39 ms 41 ms 157.157.139.252 11 39 ms 40 ms 39 ms 157.157.139.10
Tiny Carlos	Posted - 2005.10.18 15:26:00 - [195] As I can connect fine with one account but not another I'd say there is a problem with the cluster not the connection to it, tracert is a good way to keep busy when the servers are too mashed to play on though
Tangerine	Posted - 2005.10.18 15:45:00 - [196] just ran another trace :- Tracing route to 157.157.139.10 over a maximum of 30 hops 1 3 ms <1 ms <1 ms 192.168.0.1 2 17 ms 18 ms 18 ms loopback1.ar1.he1.systems.pipex.net [xxxxxx] 3 16 ms 17 ms 16 ms ge-0-0-0.cr1.he1.systems.pipex.net [xxxxxx] 4 17 ms 19 ms 18 ms ldn-b2-geth6-0-11.telia.net [213.248.75.117] 5 18 ms 17 ms 17 ms dtag.telia.net [213.248.75.106] 6 18 ms 18 ms 17 ms linx-gw13.LON.GB.net.DTAG.DE [62.154.5.38] 7 17 ms 17 ms 17 ms 62.153.203.190 8 58 ms 221 ms 256 ms 157.157.62.26 9 19 ms 19 ms 19 ms 157.157.139.252 10 18 ms 19 ms 19 ms 157.157.139.10 Trace complete. Im getting same spikes from that ip. When i ping it 100 times i can visually see 90% of the time its fine bu then ill get a spike and then it drops back to normal like so :- Reply from 157.157.62.26: bytes=32 time=16ms TTL=240 Reply from 157.157.62.26: bytes=32 time=16ms TTL=240 Reply from 157.157.62.26: bytes=32 time=165ms TTL=240 Reply from 157.157.62.26: bytes=32 time=157ms TTL=240 Reply from 157.157.62.26: bytes=32 time=197ms TTL=240 Reply from 157.157.62.26: bytes=32 time=237ms TTL=240 Reply from 157.157.62.26: bytes=32 time=217ms TTL=240 Reply from 157.157.62.26: bytes=32 time=253ms TTL=240 Reply from 157.157.62.26: bytes=32 time=17ms TTL=240 Reply from 157.157.62.26: bytes=32 time=17ms TTL=240 Reply from 157.157.62.26: bytes=32 time=19ms TTL=240 Hope it gets sorted soon
Dale Cussler	Posted - 2005.10.18 15:58:00 - [197] Originally by: Kerushi Originally by: Dale Cussler That 157.157.62.26 seems to be the bottleneck where it all goes to hell and back though. ICEnet? looks like it but it`s rather selective at who gets screwed over PING 157.157.62.26 (157.157.62.26) 56(84) bytes of data. 64 bytes from 157.157.62.26: icmp_seq=0 ttl=241 time=29.0 ms 64 bytes from 157.157.62.26: icmp_seq=1 ttl=241 time=28.4 ms 64 bytes from 157.157.62.26: icmp_seq=2 ttl=241 time=28.4 ms 64 bytes from 157.157.62.26: icmp_seq=3 ttl=241 time=31.7 ms 64 bytes from 157.157.62.26: icmp_seq=4 ttl=241 time=29.2 ms 64 bytes from 157.157.62.26: icmp_seq=5 ttl=241 time=29.4 ms 64 bytes from 157.157.62.26: icmp_seq=6 ttl=241 time=30.9 ms 64 bytes from 157.157.62.26: icmp_seq=7 ttl=241 time=35.9 ms 64 bytes from 157.157.62.26: icmp_seq=8 ttl=241 time=29.2 ms NL planet.nl, no lag nor ctd`s better ask the owner of that machine to check if rats have been scewing on some of the cables Odd because when I do a 50 packet ping from my box in Amsterdam (I'm dutch by the way), I get wildly varying results, and from home (speedlinq.nl .. dont laugh) I get the same. Sometimes clears up for a while, then goes to the ****ter again. Just seems like it's some router that's not quite keeping up. If that's the one that's supposedly being replaced sometime this week, I figure CCP oughta call em and demand it get replaced -right the heck now- because this has basically rendered the game unplayable for many people. Either that or they can come co-locate their server cluster with me in Amsterdam Wouldn't mind being able to shop for some more sweet sweet 19" racks :D /Dale
shooting dutchman	Posted - 2005.10.18 16:03:00 - [198] the problem is atm that you can't see in eve when you connection is getting timed out, it sometimes takes 10-15 minutes before eve closes down. with tomorrow the hardware upgrade that would make it 3 days in a row I would be anubale to play the game if I would like.
Kerushi	Posted - 2005.10.18 16:07:00 - [199] finished a long ping and i guess this is the reason of the sligh lag at times but still doesn`t hinders game play or crates ctd`s 64 bytes from 157.157.62.26: icmp_seq=31 ttl=241 time=28.9 ms 64 bytes from 157.157.62.26: icmp_seq=32 ttl=241 time=28.8 ms 64 bytes from 157.157.62.26: icmp_seq=33 ttl=241 time=362 ms 64 bytes from 157.157.62.26: icmp_seq=34 ttl=241 time=254 ms 64 bytes from 157.157.62.26: icmp_seq=35 ttl=241 time=76.5 ms 64 bytes from 157.157.62.26: icmp_seq=36 ttl=241 time=131 ms 64 bytes from 157.157.62.26: icmp_seq=37 ttl=241 time=183 ms 64 bytes from 157.157.62.26: icmp_seq=38 ttl=241 time=190 ms 64 bytes from 157.157.62.26: icmp_seq=39 ttl=241 time=32.0 ms 64 bytes from 157.157.62.26: icmp_seq=40 ttl=241 time=37.1 ms 64 bytes from 157.157.62.26: icmp_seq=41 ttl=241 time=28.9 ms 64 bytes from 157.157.62.26: icmp_seq=42 ttl=241 time=28.8 ms only a few every min or so but now it`s clear where ccp stole the server hamsters from
Jenny Spitfire	Posted - 2005.10.18 16:09:00 - [200] Edited by: Jenny Spitfire on 18/10/2005 16:10:02 I am no system admin but the only times I see erratic pings are when BitTorrents are active or on a wireless connection Not sure this info helps or not. ---------------- RecruitMe@NOINT!
Broken Wings	Posted - 2005.10.18 16:12:00 - [201] the game is totally unplayable for me now, please do something about this fast or i will have to go outside
1ron V1per	Posted - 2005.10.18 16:14:00 - [202] C:\Documents and Settings\Tom>tracert 157.157.139.10 Tracing route to 157.157.139.10 over a maximum of 30 hops 1 6 ms 6 ms 5 ms 192.168.0.1 2 66 ms 71 ms 69 ms lo0-plusnet.ptn-ag2.plus.net [195.166.128.53] 3 64 ms 48 ms 59 ms ge1-0-0-204.ptn-gw2.plus.net [84.92.3.106] 4 53 ms 53 ms 57 ms ge-4-1.metro1-londencyh00.London1.Level3.net [21 2.113.11.33] 5 73 ms * 73 ms so-1-3-0.gar2.London1.Level3.net [212.113.3.29] 6 45 ms 37 ms 31 ms ge-6-0.core2.London1.Level3.net [212.187.131.46] 7 49 ms 47 ms 53 ms CABLE-WIRE.c2.Level3.net [212.73.240.170] 8 70 ms * 59 ms so-1-2-0-dcr2.tsd.cw.net [195.2.10.130] 9 * 70 ms * so-5-0-0-bcr3.tsd.cw.net [195.2.10.101] 10 * 53 ms 73 ms iar2.tsd.cw.net [166.63.210.23] 11 55 ms 54 ms 52 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 12 131 ms 55 ms 45 ms 157.157.62.26 13 49 ms 57 ms 51 ms 157.157.139.252 14 96 ms 36 ms 38 ms 157.157.139.10 Trace complete.
Ralitge boyter	Posted - 2005.10.18 16:14:00 - [203] Hi, while I don't care to much about ping times I also know that they can be useful. I guess CCP has enough of them by now Anyway just figured I'd report that the server has been having difficulty letting me access the game, I get to the message Access ing the game as: Ralitge boyter and there it sits. After 5 retries I was let back in though.
tomma	Posted - 2005.10.18 16:30:00 - [204] DÚtermination de l'itinÚraire vers 157.157.139.10 avec un maximum de 30 sauts. 1 <1 ms <1 ms <1 ms 192.168.0.254 2 30 ms 30 ms 30 ms merignac-2-82-66-27-254.fbx.proxad.net [82.66.27.254] 3 31 ms 30 ms 29 ms 213.228.9.190 4 * * * DÚlai d'attente de la demande dÚpassÚ. 5 40 ms 39 ms 38 ms if-7-0.core2.PG1-Paris.teleglobe.net [80.231.73.17] 6 40 ms 39 ms 39 ms ix-4-1.core2.PG1-Paris.teleglobe.net [80.231.73.14] 7 48 ms 48 ms 48 ms isp-linx-gw13-o.nmc-m.dtag.de [217.239.38.241] 8 48 ms 47 ms 49 ms 62.153.203.190 9 130 ms 284 ms 235 ms 157.157.62.26 10 49 ms 50 ms 49 ms 157.157.139.252 11 50 ms 50 ms 49 ms 157.157.139.10 ItinÚraire dÚterminÚ.
Krollji	Posted - 2005.10.18 16:41:00 - [205] Tracing route to 157.157.139.10 over a maximum of 30 hops 1 43 ms 42 ms 43 ms 001.164-78-65.ftth.swbr.surewest.net [65.78.164. 1] 2 42 ms 43 ms 42 ms 172.21.2.1 3 43 ms 42 ms 42 ms 172.21.0.250 4 42 ms 43 ms 43 ms 245.98-30-64.ftth.swbr.surewest.net [64.30.98.24 5] 5 43 ms 43 ms 43 ms ge-6-1-515.hsa1.Sacramento1.Level3.net [64.158.1 48.129] 6 44 ms 43 ms 43 ms so-3-0-0.mpls1.Sacremento1.Level3.net [4.68.113. 57] 7 122 ms 121 ms 183 ms as-3-0.bbr2.NewYork1.Level3.net [64.159.1.134] 8 122 ms 121 ms 121 ms ge-5-0-0-54.gar1.NewYork1.Level3.net [4.68.97.98 ] 9 122 ms 122 ms 121 ms 65.59.192.14 10 199 ms 198 ms 197 ms so-2-0-0-dcr2.tsd.cw.net [195.2.10.110] 11 199 ms 197 ms 198 ms so-5-0-0-bcr1.tsd.cw.net [195.2.10.61] 12 199 ms 198 ms 198 ms iar2.tsd.cw.net [166.63.210.23] 13 202 ms 198 ms 199 ms iceland-telecom1.tsd.cw.net [166.63.214.198] 14 199 ms 198 ms 199 ms 157.157.62.26 15 199 ms 199 ms 199 ms 157.157.139.252 16 199 ms 199 ms 199 ms 157.157.139.10 Trace complete. Pinging 157.157.139.10 with 32 bytes of data: Reply from 157.157.139.10: bytes=32 time=198ms TTL=242 Reply from 157.157.139.10: bytes=32 time=199ms TTL=242 Reply from 157.157.139.10: bytes=32 time=199ms TTL=242 Reply from 157.157.139.10: bytes=32 time=197ms TTL=242 Ping statistics for 157.157.139.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 197ms, Maximum = 199ms, Average = 198ms ------------------------------------------------------ Well, been doing tracerts and pings now for the 2nd day in a row. Above is typical. The 197 ms overall is acceptable for playability however I don't think the problem is in the networking to get to the cluster but within the cluster itself. I can get ingame but go linkdead then anywhere from two to ten minutes. It appears to me to be some type of data access problem - ie: requests for data from the cluster begin to be ignored resulting in timeouts ultimately resulting in a disconnect. Then, for some reason, when trying to log back in the character data screen just sits there "loading" necessitating numerous login attemts which finally result in getting ingame - and going linkdead (LD) after a short period of time. Also found after going LD that if I just walk away from the computer and come back around 10 to 15 minutes later that I can get right into the game. No idea why this makes a difference - some sort of character/timer reset on the CCP server side? Anyhow.. the above tracert/ping results are from California and are typical of the last two days from where I'm located. While I don't like the ms time EVE should be playable but hasn't been since the DT previous to the one last night when the software for "balancing" was put in. Just my 2 cents and input for what it's worth
Xrak	Posted - 2005.10.18 17:09:00 - [206] Tracing route to 157.157.62.26 over a maximum of 30 hops 1 20 ms 19 ms 21 ms rdsl-lond-uk02.nw.mediaways.net [62.55.96.197] 2 19 ms 18 ms 17 ms 62.55.96.24 3 17 ms 18 ms 18 ms rmwc-lond-uk02-pos-5-0.nw.mediaways.net [62.55.1 59.254] 4 18 ms 18 ms 20 ms 213.130.138.33 5 18 ms 18 ms 19 ms 213.130.138.17 6 20 ms 18 ms 18 ms ldn-b1-geth11-0-13.telia.net [213.248.75.65] 7 20 ms 19 ms 18 ms ldn-b2-pos11-0.telia.net [213.248.74.37] 8 19 ms 19 ms 19 ms dtag.telia.net [213.248.75.106] 9 18 ms 20 ms 20 ms linx-gw13.LON.GB.net.DTAG.DE [62.154.5.38] 10 19 ms 22 ms 19 ms 62.153.203.190 11 * * * Request timed out. 12 23 ms 38 ms 22 ms 157.157.62.26 Trace complete. Only been CTD'ing today, was fine yesterday. In the UK.
Adam Coyle	Posted - 2005.10.18 17:34:00 - [207] Edited by: Adam Coyle on 18/10/2005 17:58:40 I am also having this problem. What trace tool do you recommend for the logs?
Aeon	Posted - 2005.10.18 17:38:00 - [208] Edited by: Aeon on 18/10/2005 17:59:08 I set my pingplotter to ping the server on a 1 second interval so maybe that will keep my connection alive.. and haven't crashed for 15 minutes now. That must be a day's record Edit: Guess it didn't help much. My record stands for 20 minutes of continious gameplay now...
Element Rachel	Posted - 2005.10.18 17:39:00 - [209] Eve Online has now been down for three days. Tomorrow will bring another day without play, with or without the problems we've been seeing. On this third day it seems like a reasonable request to ask that this time be added for free to subscriptions. I respect CCP as a responsible company that cares about its customers, and that is why I think they would listen to and accept such a request. Money has been paid for a service which has not been provided.
spRAYed	Posted - 2005.10.18 17:40:00 - [210] Its pretty annoying...i can get ingame..but i know i'll CTD within 10 minuts. So therefor its useless to pur urself in any danger ingame. You'll loose ships due to this that you wont get back anyway. So....i guess i'll have to download WoW now Oh common, dont hate me :P was only joking.....for now. ----------------------------------------- It can, 400x120x24000 bytes Max -Capsicum

Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 18 .. 18 :: one page
First page \| Previous page \| Next page \| Last page

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.