These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE General Discussion

 
  • Topic is locked indefinitely.
 

Trouble logging into eve

First post
Author
Previous Topic Next Topic
Vincenzaa
Perkone
Caldari State
#121 - 2012-08-27 14:05:07 UTC
As of about 5-10 minutes ago issues seems to have been fixed at least on my network. Had problems since morning and couldn't even connect forums/website before that.
Lady Ayeipsia
BlueWaffe
#122 - 2012-08-27 14:10:56 UTC
Vincenzaa wrote:
As of about 5-10 minutes ago issues seems to have been fixed at least on my network. Had problems since morning and couldn't even connect forums/website before that.


Just curious who your ISP is.
avicomo
Deep Core Mining Inc.
Caldari State
#123 - 2012-08-27 14:43:05 UTC
14:56:27: Rumors are surfacing via BE IRC visitors and via o2 telephone support of a "submarine hitting a cable", which I expect it means that a "submarine cable has been hit" and it's been Chinese whispered into hilarity.



http://www.beusergroup.co.uk/?id=886
Fearless M0F0
Incursion PWNAGE Asc
#124 - 2012-08-27 16:01:39 UTC
My ISP is Charter in Fort Worth, TX. Can't connect to any eve server at all from there. Just got to the office and I can connect just fine from here. My colo server in Dallas can also ping www.eveonline.com just fine.

Traceroute from home:

$ traceroute www.eveonline.com
traceroute to www.eveonline.com (87.237.39.180), 30 hops max, 60 byte packets
2 10.110.128.1 (10.110.128.1) 11.978 ms 12.827 ms 13.040 ms
3 acr21ftwotx-gbe-9-2.ftwo.tx.charter.com (96.34.113.96) 13.022 ms 13.220 ms 13.207 ms
4 acr01nrictx-vln-55.nric.tx.charter.com (96.34.113.49) 13.167 ms 13.158 ms 15.749 ms
5 acr01kllrtx-vln-54.kllr.tx.charter.com (96.34.113.47) 13.107 ms 15.914 ms 15.897 ms
6 acr31ftwotx-tge-2-3.ftwo.tx.charter.com (96.34.113.62) 15.876 ms 7.840 ms 13.021 ms
7 crr01ftwotx-tge-0-3-0-0.ftwo.tx.charter.com (96.34.113.98) 22.045 ms 23.337 ms crr01ftwotx-tge-0-3-0-1.ftwo.tx.charter.com (96.34.113.82) 23.288 ms
8 bbr01ftwotx-bue-2.ftwo.tx.charter.com (96.34.2.32) 15.881 ms 15.994 ms 16.006 ms
9 bbr02ftwotx-tge-0-2-0-4.ftwo.tx.charter.com (96.34.0.125) 17.453 ms 17.410 ms 17.406 ms
10 dal-edge-18.inet.qwest.net (63.234.57.169) 14.639 ms 15.635 ms 15.626 ms
11 * * *
12 xe-8-1-0.edge2.dallas3.level3.net (4.68.63.49) 10.926 ms 11.732 ms 15.452 ms
13 vlan70.csw2.Dallas1.Level3.net (4.69.145.126) 16.625 ms vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 22.062 ms vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 18.084 ms
14 ae-73-73.ebr3.Dallas1.Level3.net (4.69.151.146) 16.454 ms ae-92-92.ebr2.Dallas1.Level3.net (4.69.151.166) 15.008 ms 15.063 ms
15 ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 33.164 ms ae-3-3.ebr2.NewYork1.Level3.net (4.69.137.122) 51.619 ms 54.625 ms
16 ae-63-63.ebr1.Atlanta2.Level3.net (4.69.148.242) 35.987 ms ae-82-82.csw3.NewYork1.Level3.net (4.69.148.42) 57.669 ms ae-63-63.ebr1.Atlanta2.Level3.net (4.69.148.242) 34.893 ms
17 ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 51.820 ms ae-6-6.ebr1.Washington12.Level3.net (4.69.148.106) 42.450 ms 48.316 ms
18 ae-1-100.ebr2.Washington12.Level3.net (4.69.143.214) 48.264 ms 47.187 ms ae-42-42.ebr2.London1.Level3.net (4.69.137.69) 129.373 ms
19 ae-57-222.csw2.London1.Level3.net (4.69.153.134) 133.800 ms ae-58-223.csw2.London1.Level3.net (4.69.153.138) 132.242 ms 139.373 ms
20 ae-41-41.ebr2.London1.Level3.net (4.69.137.65) 133.623 ms 132.922 ms ae-25-52.car5.London1.Level3.net (4.69.139.102) 128.548 ms
21 * * ae-58-223.csw2.London1.Level3.net (4.69.153.138) 136.543 ms
22 ae-25-52.car5.London1.Level3.net (4.69.139.102) 135.434 ms 135.400 ms *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Traceroute from colo server:
$ traceroute www.eveonline.com
traceroute to www.eveonline.com (87.237.39.180), 30 hops max, 60 byte packets
3 64.182.161.1 (64.182.161.1) 2.479 ms 2.821 ms 2.863 ms
4 64.182.161.73 (64.182.161.73) 3.215 ms 3.259 ms 3.288 ms
5 ae5-840.edge9.Dallas1.Level3.net (4.30.73.57) 5.270 ms 5.118 ms 5.042 ms
6 vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 15.058 ms vlan70.csw2.Dallas1.Level3.net (4.69.145.126) 11.634 ms vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 2.994 ms
7 ae-63-63.ebr3.Dallas1.Level3.net (4.69.151.134) 4.812 ms ae-62-62.ebr2.Dallas1.Level3.net (4.69.151.130) 4.038 ms 4.074 ms
8 ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 22.279 ms ae-3-3.ebr2.NewYork1.Level3.net (4.69.137.122) 37.203 ms ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 24.302 ms
9 * ae-63-63.ebr1.Atlanta2.Level3.net (4.69.148.242) 28.694 ms ae-82-82.csw3.NewYork1.Level3.net (4.69.148.42) 49.143 ms
10 ae-6-6.ebr1.Washington12.Level3.net (4.69.148.106) 46.038 ms ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77) 39.891 ms ae-6-6.ebr1.Washington12.Level3.net (4.69.148.106) 45.915 ms
11 ae-41-41.ebr2.London1.Level3.net (4.69.137.65) 107.019 ms ae-43-43.ebr2.London1.Level3.net (4.69.137.73) 108.868 ms ae-1-100.ebr2.Washington12.Level3.net (4.69.143.214) 40.487 ms
12 ae-59-224.csw2.London1.Level3.net (4.69.153.142) 116.695 ms 4.69.148.49 (4.69.148.49) 39.048 ms 39.473 ms
13 ae-42-42.ebr2.London1.Level3.net (4.69.137.69) 107.451 ms ae-43-43.ebr2.London1.Level3.net (4.69.137.73) 108.126 ms ae-44-44.ebr2.London1.Level3.net (4.69.137.77) 105.611 ms
14 ae-56-221.csw2.London1.Level3.net (4.69.153.130) 106.228 ms PACKET-EXCH.car5.London1.Level3.net (212.187.160.62) 107.212 ms ae-57-222.csw2.London1.Level3.net (4.69.153.134) 111.729 ms
15 ae-25-52.car5.London1.Level3.net (4.69.139.102) 112.299 ms 112.726 ms 112.622 ms
16 PACKET-EXCH.car5.London1.Level3.net (212.187.160.62) 115.487 ms 115.681 ms *
17 * srv248-e.ccp.cc (87.237.36.248) 115.575 ms 115.479 ms
Pierced Brosmen
The Scope
Gallente Federation
#125 - 2012-08-27 16:27:43 UTC
Same issue still here. And like Fearless M0F0, I reach eveonline.com from the office network (it was down for some hours earlier today, but got back online aroud 14:00 UTC), but not from home.
CCP Phantom
C C P
C C P Alliance
#126 - 2012-08-27 17:18:31 UTC
We receive information that TeliaSonera had issues and since they carry a good amount of internet traffic at least some of the recent connection troubles can be explained. Since our servers are not the reason for these issues and because TeliaSonera handles a lot of traffic, our options to fix this issue are unfortunately quite limited at this moment.

CCP Phantom - Senior Community Developer
Jommis
Brothers of Tyr
Goonswarm Federation
#127 - 2012-08-27 17:39:13 UTC
CCP Phantom wrote:
We receive information that TeliaSonera had issues and since they carry a good amount of internet traffic at least some of the recent connection troubles can be explained.


Pierced Brosmen wrote:
I reach eveonline.com from the office network .



I know Pierced in RL.
He works for Telia Sonera.
Let's kick his ass!
Pierced Brosmen
The Scope
Gallente Federation
#128 - 2012-08-27 17:54:15 UTC
Jommis wrote:

I know Pierced in RL.
He works for Telia Sonera.
Let's kick his ass!

Right... you work there too, so you might want to cover your ass as well Twisted
Fearless M0F0
Incursion PWNAGE Asc
#129 - 2012-08-27 18:01:07 UTC
CCP Phantom wrote:
We receive information that TeliaSonera had issues and since they carry a good amount of internet traffic at least some of the recent connection troubles can be explained. Since our servers are not the reason for these issues and because TeliaSonera handles a lot of traffic, our options to fix this issue are unfortunately quite limited at this moment.


Well, in my case all 3 routes go through Level3:

Home (Dallas) -> Charter -> Level3 NY -> Level 3 London -> FAIL
Colo (Dallas) -> Level3 NY -> Level 3 London -> WIN
Office (Dallas) -> NAP Madrid -> Level3 Paris -> Level3 London -> WIN

Both home and colo routes to eve servers hit 4.69.139.102 in London but from home it doesn't know where to go after that.
Chribba
Otherworld Enterprises
Otherworld Empire
#130 - 2012-08-27 18:37:54 UTC
Actually what would be interesting is seeing the routes FROM CCP's datacenter to us.

Like in my example.
IP-ONLY->GLBX = FAIL
ServerConnect->IP-ONLY->GLBX = WIN

What would be interesting to see is if CCP's trace to me takes the same route back or if they are different, in wihch case I think we're a bit closer to why some routes work and some not.

/c

★★★ Secure 3rd party service ★★★

Visit my in-game channel 'Holy Veldspar'

Twitter @ChribbaVeldspar
Lady Ayeipsia
BlueWaffe
#131 - 2012-08-27 18:51:46 UTC
So does anyone know a good work-around/proxy for those of us impacted by this?
Heimdallofasgard
Ministry of Furious Retribution
Fraternity.
#132 - 2012-08-27 19:40:46 UTC
I love how one of the side effects of eve online is that it's conjured a massive internet diagnostic tool. through its players
Fearless M0F0
Incursion PWNAGE Asc
#133 - 2012-08-27 20:35:26 UTC
Just checked and I still can't connect to any eve server from home, no web, no forums, no tranquility Cry

Time to finally figure out how to setup a vpn tunnel to my colo server Bear
Dr Agropoly
Viziam
Amarr Empire
#134 - 2012-08-27 20:51:34 UTC  |  Edited by: Dr Agropoly
Using http://www.hotspotshield.com/ works for most people or just figuring out how to get a new ip address.
For me the launcher freezes when using hotspotshield but forum and site access is no problem.

Edit: After a while I got the option to start client, then everything works fine.
Creeper de Monn
Kite Co. Space Trucking
#135 - 2012-08-27 22:23:19 UTC
Dr Agropoly wrote:
Using http://www.hotspotshield.com/ works for most people or just figuring out how to get a new ip address.
For me the launcher freezes when using hotspotshield but forum and site access is no problem.

Edit: After a while I got the option to start client, then everything works fine.


I used HotSpotShield, as well, earlier today and was able to connect without issue. Now, as of 10.20pm EVE Time, I'm able to connect without the VPN.
Spc One
The Chodak
Void Alliance
#136 - 2012-08-27 22:24:33 UTC  |  Edited by: Spc One
I have some serious problems.
My ISP can't route to eveonline, i am currently on cellular network writing this.

here's my traceroute..

1 0 ms 0 ms 0 ms SERVER [192.168.0.1]
2 7 ms 11 ms 9 ms 10.147.0.1
3 9 ms 11 ms 6 ms ve-3.ruby.ip.triera.net [213.161.2.81]
4 8 ms 13 ms 6 ms cartman-ve-1.ip.triera.net [213.161.2.3]
5 10 ms 19 ms 10 ms 10ge-e5-1.vie.ip.triera.net [213.161.2.222]
6 10 ms 13 ms 14 ms peer-AS31042.sbb.rs [82.117.193.217]
7 29 ms 27 ms 32 ms bg-du-r-1-te0-0-0-1.sbb.rs [89.216.5.33]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

All of eve servers are offline, no server is pingable for 3 days now.
Ugh

CCP Phantom wrote:
We receive information that TeliaSonera had issues and since they carry a good amount of internet traffic at least some of the recent connection troubles can be explained.

Why is ccp using telia for peering and routing ? we all know that telia is very very bad in peering.
PAPULA
The Chodak
Void Alliance
#137 - 2012-08-27 22:50:47 UTC
Same problems here, 4 days of ping timeout to all eve's ip servers.
Seems like routing problem with telia
Pierced Brosmen
The Scope
Gallente Federation
#138 - 2012-08-27 23:08:11 UTC
Works for me now, finaly
heretick Thelema
Imperial Academy
Amarr Empire
#139 - 2012-08-27 23:35:39 UTC
works for me as of about 1 hour ago... After 2 days of darkness!
Spc One
The Chodak
Void Alliance
#140 - 2012-08-28 00:23:23 UTC
heretick Thelema wrote:
works for me as of about 1 hour ago... After 2 days of darkness!

Confirming, finally works, question is for how long.

Traceroute:

1 <1 ms <1 ms <1 ms SERVER [192.168.0.1]
2 7 ms 9 ms 12 ms 10.147.0.1
3 7 ms 8 ms 5 ms ve-3.ruby.ip.triera.net [213.161.2.81]
4 12 ms 7 ms 5 ms cartman-ve-1.ip.triera.net [213.161.2.3]
5 12 ms 12 ms 13 ms 10ge-e5-1.vie.ip.triera.net [213.161.2.222]
6 15 ms 12 ms 12 ms peer-AS31042.sbb.rs [82.117.193.217]
7 28 ms 27 ms 27 ms bg-du-r-1-te0-0-0-1.sbb.rs [89.216.5.33]
8 70 ms 49 ms 48 ms TenGigabitEthernet6-1.ar1.FRA4.gblx.net [64.211.83.57]
9 108 ms 102 ms 53 ms 204.245.39.38
10 56 ms 56 ms 56 ms srv248-e.ccp.cc [87.237.36.248]
11 56 ms 55 ms 54 ms srv180-h.ccp.cc [87.237.39.180]