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

Xedrik
Amarr
|
Posted - 2007.06.03 11:38:00 -
[1]
Edited by: Xedrik on 03/06/2007 11:42:15 Since there has been no official statement from CCP about this I'll post everything I've gathered from the numerous threads about this to keep it in one place and hopefully tie up some loose ends for some of you guys (and girls). This problem is affecting an unknown amount of subscribers with ISP's that route their traffic through Limelight Networks. This results in the failing to reach any of CCP's servers, thus not being able to connect to either the game or the website. The only way to access the EVE-Online website and forum is to use a proxy that doesn't route through Limelight Networks, like Ninjaproxy (www.ninjaproxy.com).
Confirmed ISPs that are or may be affected by this (might be incomplete):
* Telia and other ISPs using Skanova as provider (Sweden) * Bredbandsbolaget (Sweden) * Blueyonder (UK) * Virgin (UK) * Bruce Telecom (Ontario, Canada)
Because Limelight Networks is the last link before failing I took contact with them in hope of that the problem resided in one of their routers. I've been having contact with them back and forth since yesterday (Saturday morning) and they have clearly stated that this is not a problem on their side. They also said they are working with CCP to resolve this and will inform me on any status change or progress made. As I understand it Limelight Networks want to resolve this as soon as possible since it's overloading their support.
Last reply from Limelight Networks:
Quote: I wanted to let you know that we're working with CCP. We've noticed that a few of the other users that emailed in said they'd disabled Peer Guardian and were able to get in.
Right now we're seeing the issue with CCP's routers. We're still looking into it to make sure it's not an issue on our side, though. We want to ensure that the issue is not on our side. If it's something on our side affecting a customer, it could be affecting others.
If we get more information we'll pass it on to you.
Even though there are some contradictions in that response I do trust them about the problem being with CCP's routers. At least they are replying and informing me about what's going on, and that's more then you could say about CCP. =)
As far as I know and what has been speculated in other threads, this has to do with changes that CCP did in their routing tables on Thursday evening, fixing a packet loss issue for some while introducing this connection problem to others. Since it takes some time for routing tables to update for all parts, this haven't affected all at ones. This also explains why some haven't been able to connect since Friday, and others since yesterday.
So for now, we have to wait until CCP gives us an update on the situation or that they resolve the problem. I personally hope for both!
I hope this information relieved some of your frustrations about not knowing what's going on. I'll keep you posted on any updates that becomes available from Limelight Networks and CCP.
Thanks for your time,
Xed
|

Xedrik
Amarr
|
Posted - 2007.06.03 11:39:00 -
[2]
Responses from CCP.
This problem was acknowledged by CCP Wrangler in another thread:
Originally by: CCP Wrangler I've notified the server people at least, I'll post if there's any news.
CCP John Proctor have also been posting replies in the same thread during yesterday evening/this morning where he said that they were contacting Limelight Networks to resolve it. This is his last post:
Originally by: CCP John Proctor Sorry guys, just got back from the CCP 10th year celebrations. We escalated this issue with our providers at Limelight and have determined this not to reside with our network. We have done recent route changes here at CCP by using other providers in an effort to get away from L3 that was droping players by the thousands and causing those massive packet loss issues.
Until all the BGP paths get updated on all routers globally there are going to be issues... we are hoping these issues will sort them selves with time, if we make any more changes by say enabeling the L3 link again then we may cause more issues then it would solve. Our Network Administrator has been looking into the issue and I will update this thread with information when I know more. It is 2:16 am here Sunday morning currently, we will not know more about the situation until later in the day.
|

MindDragon
Caldari The Plane Walkers
|
Posted - 2007.06.03 12:01:00 -
[3]
Edited by: MindDragon on 03/06/2007 12:02:12 Edit:Typo Just adding in the ff:
* PLDT Internet and Globe Internet (Philippines)
Problem first documented Saturday, June 2nd at about 7am GMT. A number of petitions have been filed. If you are able to read this and have this issue, you should file a petition as well so as to document your case should you need reimbursement for POS failures or other issues related to this.
The general forum thread can be found here.
A normal trace should contain the following:
10 21 ms 24 ms 23 ms tge7-2.fr3.lon.llnw.net [69.28.171.94] 11 17 ms 23 ms 22 ms ccp.ve201.fr3.lon.llnw.net [87.248.208.150] 12 21 ms 21 ms 20 ms 87.237.38.199 13 19 ms 19 ms 23 ms 87.237.38.200
People that are having the problem get the following:
14 52 ms 49 ms 50 ms tge7-2.fr3.lon.llnw.net [69.28.171.94] 15 * * *
Based on the connection problems thread, this has been starting to happen on 5/24 and some event occured recently that caused the main failure.
We are all awaiting word from CCP as to when this problem will be fixed and what actions CCP will do in the future to ensure that this never happens again and what will happen to those of us that are damaged by this.
MD ------ This space for rent. |

Xedrik
Amarr
|
Posted - 2007.06.03 16:01:00 -
[4]
Finally they've fixed it. I can't believe it took over 48h...
Originally by: CCP John Proctor The issue has been located, the issue stemmed with the return path going through another one of our providers. Limelight was correct in its assessment that they were not the cause of the problem. The problem stemmed with the return path routing through a provider other then Limelight.
We have disabled this return path and now all traffic is being routed through Limelight, until we resolve the issue with that provider.
We apologize for the inconvenience this has caused our customers.
Please update this thread if you are still experiencing any issues.
I knew this all the time. This means it was basically CCP's fault since they were the only ones who could disable the return path. They should have done so WAAAAAY sooner. I wonder when they will go out with an official statement about this.
|

Mad Maddy
|
Posted - 2007.06.03 16:03:00 -
[5]
well its not working for me
|

Xedrik
Amarr
|
Posted - 2007.06.03 16:04:00 -
[6]
Originally by: Mad Maddy well its not working for me
What happends if you do a traceroute?
|

Wills Will
|
Posted - 2007.06.03 16:07:00 -
[7]
Edited by: Wills Will on 03/06/2007 16:06:43
Originally by: Xedrik
Originally by: Mad Maddy well its not working for me
What happends if you do a traceroute?
Sorry don't know how can you do a quick explain?
This is mad maddy
|

Mad Maddy
|
Posted - 2007.06.03 16:14:00 -
[8]
traceroute to 87.237.38.200 (87.237.38.200), 30 hops max, 38 byte packets 1 alan5 (193.62.127.129) 3.496 ms 0.580 ms 0.475 ms 2 gw-fw (193.63.74.131) 0.236 ms 0.196 ms 0.214 ms 3 c-pop (193.63.74.226) 0.969 ms 0.746 ms 0.714 ms 4 193.62.116.18 (193.62.116.18) 1.121 ms 1.115 ms 1.101 ms 5 so-0-1-0.warr-sbr1.ja.net (146.97.42.169) 1.719 ms 1.718 ms 1.725 ms 6 so-0-2-0.read-sbr1.ja.net (146.97.33.109) 5.447 ms 5.458 ms 5.439 ms 7 lond-scr3.ja.net (146.97.33.142) 6.851 ms 6.858 ms 6.858 ms 8 po1-0.lond-gw-ixp2.ja.net (146.97.35.250) 7.076 ms 6.915 ms 6.878 ms 9 ge0-0-0-2.jr1.lon.llnw.net (195.66.226.133) 7.007 ms 7.291 ms 6.984 ms 10 tge7-4.fr3.lon.llnw.net (69.28.171.137) 17.722 ms 7.049 ms 7.116 ms 11 ccp.ve201.fr3.lon.llnw.net (87.248.208.150) 7.286 ms 7.287 ms 7.190 ms 12 * * * 13 * * * 14 * *
|

Xedrik
Amarr
|
Posted - 2007.06.03 16:19:00 -
[9]
Edited by: Xedrik on 03/06/2007 16:21:42
Originally by: Mad Maddy traceroute to 87.237.38.200 (87.237.38.200), 30 hops max, 38 byte packets 1 alan5 (193.62.127.129) 3.496 ms 0.580 ms 0.475 ms 2 gw-fw (193.63.74.131) 0.236 ms 0.196 ms 0.214 ms 3 c-pop (193.63.74.226) 0.969 ms 0.746 ms 0.714 ms 4 193.62.116.18 (193.62.116.18) 1.121 ms 1.115 ms 1.101 ms 5 so-0-1-0.warr-sbr1.ja.net (146.97.42.169) 1.719 ms 1.718 ms 1.725 ms 6 so-0-2-0.read-sbr1.ja.net (146.97.33.109) 5.447 ms 5.458 ms 5.439 ms 7 lond-scr3.ja.net (146.97.33.142) 6.851 ms 6.858 ms 6.858 ms 8 po1-0.lond-gw-ixp2.ja.net (146.97.35.250) 7.076 ms 6.915 ms 6.878 ms 9 ge0-0-0-2.jr1.lon.llnw.net (195.66.226.133) 7.007 ms 7.291 ms 6.984 ms 10 tge7-4.fr3.lon.llnw.net (69.28.171.137) 17.722 ms 7.049 ms 7.116 ms 11 ccp.ve201.fr3.lon.llnw.net (87.248.208.150) 7.286 ms 7.287 ms 7.190 ms 12 * * * 13 * * * 14 * *
Well, at least you're getting one more jump. It got stuck at tge7-4.fr3.lon.llnw.net before. Maybe it will take some time before it will actually resolve. Btw, you don't have PeerGuardian? If you do, it's probably blocking the IPs.
|

Tavaris Rayne
|
Posted - 2007.06.03 16:43:00 -
[10]
I've finally managed to log into eve and the forums for the first time since Friday 1st June. I couldn't even post on the forums, only look at them via www.phproxy.org! I don't know if anyone has fixed the connection, or it has somehow righted itself (for me anyway). I just hope that everyone else who has not been able to log into the game will soon be able to do so. 
|

Mad Maddy
|
Posted - 2007.06.03 18:49:00 -
[11]
Hi all
Found my problem.
Since the reroute peer garden no longer likes eve.
If you have this runing try shuting it down
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |