Skip to content

System

System status

Live data straight from our infrastructure, no polished charts. This page refreshes automatically every 30 seconds.

All systems operational

Updated 07:10:24 · auto-refresh every 30 s

AdMonitoring supported byExample adSlot open · from €39/monthBook this placement

—

API latency

51ms

DB latency

99.81%

Avg uptime · 60 days

Surface availability

WebsiteOperationalShopOperationalPortalOperationalAdminOperationalAPIOperational

Reachability check only, we do not measure a response time for these surfaces. Measured response times are shown per component below.

Components · uptime, last 60 days

Per component: current status, measured response times and uptime over 30, 60 and 90 days. “, ” means no measurement is available for that value, not zero milliseconds.

API gatewayOperational

—

Response time now

—

24 h average

—

24 h p95

100 %

Uptime 30 days

100 %

Uptime 60 days

100 %

Uptime 90 days

No measured response time is available for this component right now.

-60dUptime 60 days 100 %today
Last checked: 17/11, 07:10from 144 checks
Server infrastructureOperational

988 ms

Response time now

1,083 ms

24 h average

1,768 ms

24 h p95

99.46 %

Uptime 30 days

99.64 %

Uptime 60 days

99.69 %

Uptime 90 days

Response time now24 h average24 h p95
-60dUptime 60 days 99.64 %today
Last checked: 17/11, 07:10from 144 checks
Game server systemOperational

72 ms

Response time now

66 ms

24 h average

117 ms

24 h p95

98.37 %

Uptime 30 days

99.19 %

Uptime 60 days

99.31 %

Uptime 90 days

Response time now24 h average24 h p95
-60dUptime 60 days 99.19 %today
Last checked: 17/11, 07:10measured since: 8 September 2026from 144 checks
Email systemOperational

112 ms

Response time now

89 ms

24 h average

127 ms

24 h p95

99.39 %

Uptime 30 days

99.68 %

Uptime 60 days

99.77 %

Uptime 90 days

Response time now24 h average24 h p95
-60dUptime 60 days 99.68 %today
Last checked: 17/11, 07:10from 144 checks
DatabaseOperational

51 ms

Response time now

66 ms

24 h average

118 ms

24 h p95

100 %

Uptime 30 days

100 %

Uptime 60 days

100 %

Uptime 90 days

Response time now24 h average24 h p95
-60dUptime 60 days 100 %today
Last checked: 17/11, 07:10from 144 checks
Tebex shopOperational

56 ms

Response time now

64 ms

24 h average

98 ms

24 h p95

100 %

Uptime 30 days

100 %

Uptime 60 days

100 %

Uptime 90 days

Response time now24 h average24 h p95
-60dUptime 60 days 100 %today
Last checked: 17/11, 07:10measured since: 8 September 2026from 144 checks
Discord botOperational

—

Response time now

—

24 h average

—

24 h p95

99.98 %

Uptime 30 days

99.99 %

Uptime 60 days

99.99 %

Uptime 90 days

The Discord bot is checked via its heartbeat, not via a request, that is why there is no response time for it.

-60dUptime 60 days 99.99 %today
Last checked: 17/11, 07:10from 144 checks
Discord communityOperational

60 ms

Response time now

118 ms

24 h average

357 ms

24 h p95

100 %

Uptime 30 days

99.99 %

Uptime 60 days

99.98 %

Uptime 90 days

Response time now24 h average24 h p95
-60dUptime 60 days 99.99 %today
Last checked: 17/11, 07:10measured since: 8 September 2026from 144 checks

Active incidents

No active incidents, all quiet.

Past incidents (30 days)

  1. Server infrastructure: automatically detected disruptionminor · resolved

    07/11, 06:30 — 07/11, 09:50

  2. Email system: automatically detected disruptionminor · resolved

    06/11, 19:50 — 07/11, 00:00

  3. Discord bot: automatically detected disruptioncritical · resolved

    29/10, 12:50 — 29/10, 13:00

  4. Server infrastructure: automatically detected disruptionminor · resolved

    26/10, 03:40 — 26/10, 03:50

  5. Precautionary PHP security maintenance completedmaintenance · resolved

    21/10, 19:07 — 23/10, 16:12

  6. Game server system: automatically detected disruptioncritical · resolved

    21/10, 19:30 — 22/10, 07:00

Show all 8 incidents
  1. Server infrastructure: automatically detected disruptionminor · resolved

    21/10, 17:50 — 21/10, 18:00

  2. Server infrastructure: automatically detected disruptionminor · resolved

    19/10, 14:50 — 19/10, 15:00