Platform status
const url = 'https://api.gampeon.com/v1/status';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.gampeon.com/v1/statusWhat the status page in the portal shows: the state of the website, portal, web API, developer docs and MCP server, checked every minute from the GAMPEON server, with 90 days of daily history, incidents of the last 7 days and the community game servers that are online.
The checks run on the same server as the services. When that whole server is down, there is no data for that time, except for the web API, where missing minutes count as down. Answers are cached for 15 seconds.
Rate limit: 120 per minute per IP.
Responses
Section titled “Responses”Current status
object
Summary over all services
false: this API instance does not run checks (local development), services is empty
How often the services are checked
object
Page for people
unknown: no check in the last 3 minutes. A single failed check shows as degraded, two in a row as down.
object
90 days, oldest first. All zero: no data that day.
object
UTC day YYYY-MM-DD
Minutes up
Minutes degraded
Minutes down
object
Community game servers online (heartbeat in the last 90 seconds)
Players on those servers
Up to 5 servers with the most players
object
Last 24 hours
object
Start of the 15-minute step
Most players in that step
Disruptions of 2 minutes or longer in the last 7 days, newest first (up to 20)
Example
{ "status": "operational", "services": [ { "id": "website", "state": "up" } ], "incidents": [ { "state": "degraded" } ]}Limit: 120 per minute per IP. Error codes: rate_limited
object
Machine-readable error code, for example not_found or rate_limited.
Human-readable detail. Only present for some errors.
Example generated
{ "error": "example", "message": "example"}