THE DETAILS MATTER

Data sources

Official feeds. Clear coverage. No guessed statuses.

Epic Games status API

Fortnite, Rocket League, Rocket League Sideswipe and Fall Guys use the public Epic status summary. Every dashboard selects its own service group, affected incidents and scheduled maintenance. Concurrent game checks share one upstream request. Responses are cached for approximately two minutes.

Official Epic Games status →

Riot Games regional notices

VALORANT reads five production regions, League of Legends reads 15 and Wild Rift reads nine. Legends of Runeterra covers Americas, Europe and Asia-Pacific; 2XKO covers Americas and Asia-Pacific only. Europe is not connected for 2XKO. Coverage is listed on each dashboard. VALORANT does not currently cover Latin America; Wild Rift does not cover mainland China; League excludes PBE. These are official service updates, not server probes. No current notice does not prove a server is reachable.

The feeds are public JSON used by Riot’s official service-status website. They are not presented as an SLA-backed developer API. Only published English notices are displayed; incomplete or invalid data cannot become a fresh report. Riot product registration and commercial-policy review are required before monetization.

Official Riot Games status →

EVE Online service reports

EVE Online reads CCP’s official public status summary and selects only the Tranquility group: game server, login and Quasar. EVE Vanguard, ESI and standalone cloud/CDN components are excluded from its headline. Incidents and maintenance must reference a selected component. Reports are cached for approximately two minutes and do not establish individual connectivity or continuous uptime.

Official EVE Online status →

Supported games only

Ten games have connected official feeds. Fourteen experimental pages provide reference links and transparent coverage limits; they are excluded from search indexing. A reference link is not an automated health check. Community reports and background history require persistent storage and remain unavailable on production until configured.

Sources by game

Technical probes and community evidence

CS2 has a configured, documented public Steam Web API probe. It tests a supporting platform API, not CS2 matchmaking or game servers. Hosted scheduled execution is not enabled until durable storage and an authenticated scheduler are configured.

Community reports are optional, aggregated and rate-limited. They do not create public report URLs and cannot alone confirm an outage. Their historical baseline must be established from actual observed windows. Evidence confidence is a quality score, not a probability.

Steam probe documentation ↗

Reuse, attribution and reliability

Sources are attributed beside data. Public access is not blanket permission to reuse artwork or ignore commercial terms. Atlassian documents the public status API; we still cache requests. Rate-limit or provider failures use a labeled last-valid response where storage is available. Publisher endpoints can change, and sampled history is not continuous uptime monitoring.

Privacy settings

Necessary storage keeps your privacy choices. Optional measurement is off until you choose it.

Cookie policy