Public status

Reactor is monitored before paid server capacity turns on.

Reactor Status runs Cloudflare container previews first, then promotes paid demand to dedicated game-port capacity when direct TCP and UDP game ports are justified. This page keeps the preview funnel and health endpoints visible before server owners reserve paid capacity.

Open Cloudflare preview Open pricing calculator Contact Reactor

Reactor website

Homepage and public marketing surface

Checking

Cloudflare preview page

Paid-slot capture and preview-server explanation

Checking

Container gateway health

Cloudflare Containers gateway for HTTP/WebSocket preview sessions

Checking

Core APIhttps://api.reactor-servers.com/core/v1/health User APIhttps://api.reactor-servers.com/user/v1/health Jobs APIhttps://api.reactor-servers.com/jobs/v1/health Billing APIhttps://api.reactor-servers.com/billing/v1/health Servers APIhttps://api.reactor-servers.com/servers/v1/health Address APIhttps://api.reactor-servers.com/address/v1/health

Coverage

What this status page proves before a server owner pays.

Preview funnel

The homepage, Cloudflare preview, pricing calculator, and paid-slot capture page stay reachable while demand is tested before infrastructure spend.

Container path

The Cloudflare Containers gateway is visible separately from the website, so preview sessions can be checked without touching game-port infrastructure.

API boundary

Core, user, jobs, billing, servers, and address APIs are linked for server-side uptime probes and operator debugging.

API endpoints are linked directly because browser CORS does not need to be loosened for a public status page. Dashboard monitors and external uptime probes check those endpoints server-side. Cloudflare previews validate the web and lifecycle control path; real TCP/UDP gameplay remains a paid-demand dedicated capacity step.