Problem with Capsuleer server on June 18th from 2:00pm – 4:00pm EST

Posted on June 18, 2009
Filed Under Support | 2 Comments

On June 18th between 2:00pm EST and 4:00pm EST there was a problem with the Capsuleer server that caused the server status of both Tranquility and Singularity to be incorrectly reported as offline.

The problem occurred when I made a change to the firewall to protect a new service that we’ll be bringing online in the future for Capsuleer. I incorrectly blocked access to the EVE servers and the batch processes were unable to connect to the servers to perform a status check. Because of the inability to connect the processes assumed that the servers were offline.

Service is now restored and the servers should have their status correctly updated.

I apologize for this mistake and will do everything I can to prevent a similar one in the future.

chris.

Comments

2 Responses to “Problem with Capsuleer server on June 18th from 2:00pm – 4:00pm EST”

  1. Verite Rendition on June 20th, 2009 8:12 am

    I actually didn’t realize this app pulled data from any servers besides CCP’s API server. Since CCP offers the server status via API too, is there any specific reason that the app is polling your server instead? And does anything else besides the server status go through your server?

  2. pyjamasam on July 2nd, 2009 8:50 pm

    @Verite Rendition:

    Sorry I didn’t notice your comment until now. I spend all my time refreshing the forums and some times forget about the blog.

    The server status available through the API is subject to the API being active. If the API goes down (which it does from time to time) the server status is unavailable. Also in the instances after a patch from CCP the API is usually down for at least a day, and during which the server would be marked as “down”.

    Another thing that goes through our server are headlines (the main reason that they refresh so fast now is that the server is doing all the heavy parsing of the XML feeds and only delivering the new content to the phone).

    Images are also served up from our server. For character portraits we just act as a pass through cache (though we do have some redundancy setup to fetch images from an alternate source if CCPs server is down). Corp logos are also served from our server as well. But those are a different case. We generate them from all the little bits that are used in-game since there is no way to get a pre-rendered image from CCP.

    The ad system that Capsuleer uses as well is managed by the server. It keeps tracks of views and clicks so that we can provide our advertisers with statistics for their ads. All information stored for the purposes of the ads are anonymous in much the same way that something like google analytics is.

    With the 2.1 update thats currently in development the server will also manage the push notifications. In that case it will store your character id, character name, your devices app specific token and the end date of your skill queue.

    I hope this clears up what parts our server supports for Capsuleer.

    Your comment does make me realize though that we need a privacy policy posted on our site. I apologize for not having one right now and I’ll get one up as soon as possible.

    Rest assured though that no personal data is stored. We have no desire to have to manage any of that kind of data (thats one of the reasons the push implementation only stores the bare minimum to get a message to the phone).

    chris.

Find It