All Systems Operational
2 Known Degradations

Subdomain Status

Cruise DB
96.02% uptime
90 days ago Today
Skin Browser
99.99% uptime
90 days ago Today
Gameday Analytics
99.99% uptime
90 days ago Today
Arc Raiders
99.98% uptime
90 days ago Today
FreakFeed
99.04% uptime
90 days ago Today
SCDB
99.97% uptime
90 days ago Today

Game Servers

Hytale
Type Hytale
Address games.freaklabs.dev:5520
Checked just now
Satisfactory
Type Satisfactory
Address games.freaklabs.dev:7777
Checked just now
Enshrouded
Type Enshrouded
Address games.freaklabs.dev:15638
Checked just now
Icarus
Type Icarus
Address games.freaklabs.dev:27015
Checked just now

Incident History

Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-15 00:34:03.

Resolved
Apr 15, 2026 5:32 AM → Apr 15, 5:34 AM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 17:34:04.

Resolved
Apr 14, 2026 10:30 PM → Apr 14, 10:34 PM Duration: 3m
Major Hytale — Server Offline

Hytale — Game server at games.freaklabs.dev:5520 is not responding. Resolved automatically — service recovered at 2026-04-14 16:02:06.

Resolved
Apr 14, 2026 9:00 PM → Apr 14, 9:02 PM Duration: 2m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 16:04:05.

Resolved
Apr 14, 2026 9:00 PM → Apr 14, 9:04 PM Duration: 3m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 14:04:02.

Resolved
Apr 14, 2026 7:02 PM → Apr 14, 7:04 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 13:56:03.

Resolved
Apr 14, 2026 6:54 PM → Apr 14, 6:56 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 13:46:03.

Resolved
Apr 14, 2026 6:42 PM → Apr 14, 6:46 PM Duration: 3m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 13:40:03.

Resolved
Apr 14, 2026 6:38 PM → Apr 14, 6:40 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 13:36:02.

Resolved
Apr 14, 2026 6:34 PM → Apr 14, 6:36 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 13:22:03.

Resolved
Apr 14, 2026 6:20 PM → Apr 14, 6:22 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 13:18:03.

Resolved
Apr 14, 2026 6:16 PM → Apr 14, 6:18 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5000 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 13:14:03.

Resolved
Apr 14, 2026 6:12 PM → Apr 14, 6:14 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 13:08:03.

Resolved
Apr 14, 2026 6:06 PM → Apr 14, 6:08 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 13:04:03.

Resolved
Apr 14, 2026 6:02 PM → Apr 14, 6:04 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 12:54:02.

Resolved
Apr 14, 2026 5:52 PM → Apr 14, 5:54 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5001 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 12:50:03.

Resolved
Apr 14, 2026 5:48 PM → Apr 14, 5:50 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5001 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 12:30:03.

Resolved
Apr 14, 2026 5:28 PM → Apr 14, 5:30 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 12:20:02.

Resolved
Apr 14, 2026 5:18 PM → Apr 14, 5:20 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5000 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 12:16:03.

Resolved
Apr 14, 2026 5:14 PM → Apr 14, 5:16 PM Duration: 1m
Critical FreakFeed — Outage Detected

FreakFeed — Health check failed: Operation timed out after 5002 milliseconds with 0 bytes received Resolved automatically — service recovered at 2026-04-14 12:02:03.

Resolved
Apr 14, 2026 5:00 PM → Apr 14, 5:02 PM Duration: 1m

Auto-refresh in 120s