API Methods - Server Status
The server status API allows more in-depth data on server status than the EVE API server status API permits. It achieves this by polling the EVE server via TCP. This is not recommended for large-user applications, and is officially not supported by CCP. This API lets you get the same level of information with none of the hassle.
The API format is simple- Tranquility, Singularity and the TQ API server are tracked. The API server shows 'up' for responsiveness and 'open' as database access, as these are often independently controlled. Other variable except last_update are omitted.
Example Output - /api/server_status.xml
<?xml version='1.0' encoding='utf-8' ?>
<evemetrics api_version='2.0'>
<!--
EVE Metrics Server Status API
Documentation is available at the same URI with a .html extension.
-->
<server>
<name>Tranquility</name>
<up>true</up>
<version>6.14</version>
<open>true</open>
<machonet>219</machonet>
<players>26212</players>
<build>101786</build>
<last_update>2009-12-01 01:12:48 UTC</last_update>
</server>
<server>
<name>Singularity</name>
<up>true</up>
<version>6.2</version>
<open>true</open>
<machonet>231</machonet>
<players>120</players>
<build>117956</build>
<last_update>2009-12-01 01:12:48 UTC</last_update>
</server>
<server>
<name>Tranquility API</name>
<up>true</up>
<version></version>
<open>true</open>
<machonet></machonet>
<players></players>
<build></build>
<last_update>2009-10-28 17:15:20 UTC</last_update>
</server>
</evemetrics>
The techinical details behind this API are simple- a request to the server is made and the returned status packet is decoded, as the client does on the login screen. The servers are polled once a minute. CCP frowns upon apps that use this method where the user base is hundreds or thousands, meaning increased load on the servers providing the status packets. This XML API lets you get all the same information while keeping load on CCP to a minimum, and without needing to rely on the EVE Online API for server status, which lags behind and is generally considered less useful, especially post-patch where the API server may be offline.