Originally by: Alexandros Balfros

---

Originally by: Captain Hexagorn

---

I have been having connection issues from the the day the big patch came out i was in a mission and got dced by the time i got back on i had 10% structure left on my raven then ...

2008.06.23 01:48:00

Victim: Captain Hexagorn
Corp: East India tea Co
Alliance: NONE
Faction: NONE
Destroyed: Raven
System: Nibainkier
Security: 0.7
Damage Taken: 58188

Involved parties:

Name: Paradise Cruise Missile / Sansha's Nation (laid the final blow)
Damage Done: 58188

Destroyed items:

Damage Control I
400mm Reinforced Nanofiber Plates I
Widowmaker Heavy Missile, Qty: 28
Infiltrator I, Qty: 2 (Drone Bay)
Salvage Tackle I
Anti-EM Screen Reinforcer I
LiF Fueled I Booster Rockets
720mm Prototype I Siege Cannon
Medium 'Accommodation' Vestment Reconstructer I
Havoc Heavy Missile, Qty: 28
Havoc Heavy Missile, Qty: 289 (Cargo)
Hornet I, Qty: 3 (Drone Bay)
Scourge Heavy Missile, Qty: 25

Dropped items:

Nuclear M, Qty: 9
Scourge Heavy Missile, Qty: 295 (Cargo)
Advanced 'Limos' Heavy Missile Bay I, Qty: 2
Widowmaker Heavy Missile, Qty: 26
Widowmaker Heavy Missile, Qty: 297 (Cargo)
Large Neutron Saturation Injector I
Large F-S9 Regolith Shield Induction, Qty: 2
XR-3200 Heavy Missile Bay, Qty: 3
Invulnerability Field I
Salvager I
Medium Subordinate Screen Stabilizer I
'Malkuth' Heavy Missile Launcher I
Nuclear M, Qty: 239 (Cargo)
Thunderbolt Heavy Missile, Qty: 366 (Cargo)
Ballistic Control System I
Cross-linked Bolt Array I
Warrior I, Qty: 4 (Drone Bay)
Thunderbolt Heavy Missile, Qty: 54
Hornet I (Drone Bay)

---

Well with that fit its hardly surprising >.>

On topic i've had no connection issues that weren't as a result of a dodgy wireless connection all been working fine here for ages :)

---

Originally by: Pr1ncess Alia

---

Originally by: AceMonter

---

Im still getting DC every 5 mins... this is my trace...

Target Name: N/A
IP: 87.237.38.200
Date/Time: 25/06/2008 14:49:11 to 25/06/2008 14:50:47

Hop Sent Err PL% Min Max Avg Host Name / [IP]
2 39 0 0.0 9 181 27 [200.3.60.24]
3 39 0 0.0 143 274 165 host237.200-117-79.telecom.net.ar [200.117.79.237]
4 39 0 0.0 13 107 30 host205.200-117-127.telecom.net.ar [200.117.127.205]
5 39 0 0.0 148 303 169 host86.200-3-81.telecom.net.ar [200.3.81.86]
6 39 0 0.0 161 380 186 mia7-telecom-argentina-2-ar.mia.seabone.net [195.22.199.113]
7 39 0 0.0 161 359 190 mai-b1-link.telia.net [80.239.193.161]
8 39 0 0.0 164 321 189 atl-bb1-link.telia.net [80.91.252.57]
9 39 0 0.0 178 313 204 ash-bb1-link.telia.net [80.91.248.138]
10 21 0 0.0 261 460 279 ldn-bb2-pos6-0-0.telia.net [213.248.65.209]
11 23 0 0.0 254 413 270 ldn-b4-link.telia.net [80.91.250.233]
12 39 0 0.0 277 412 297 ccp-ic-124901-ldn-thon-s2.c.telia.net [213.248.90.90]
13 39 0 0.0 259 468 276 [87.237.38.200]

---

call telecom and complain. send them the traceroute. nothing ccp can do

argentina to london is going to be a high trip time period, but your only passing through 2 isps so its either them or telia that can help you (if they can at all)

do an extended ping to the server (ping 87.237.38.200 -t) and see if any time out. if they do thats a bad thing, tell telecom about that too

---