Public system status.

Operational model

One source of truth for launch, degradation, and maintenance.

The public site reads the same API-backed status feed Bulwrk uses for launch posture and incident communication. Local dev can still render this page safely without the API, but once the API is available the announcements come from persisted public-site records.

Coming SoonDefault pre-launch posture while access opens in controlled waves and the waitlist drives cohort rollout.

DegradedA reduced but usable posture. Personal Sync refreshes or non-critical analytics may lag while core league state remains intact.

MaintenanceCanonical public response for planned downtime, migrations, and payout-rail maintenance windows.

OperationalEverything is live, current, and healthy across the public site, command desk, and API perimeter.

Public status

Live public signal

The landing surface reflects the same launch and incident state Bulwrk publishes through the API.

Coming Soon

Loading status feed...

Environment topology

Staging and production share the same route contract.

Bulwrk uses bulwrk.gg and staging.bulwrk.gg for the public web surface. The authenticated command desk lives at /app, while the API stays isolated on the corresponding api. subdomain.

Productionproduction

Public host

https://bulwrk.gg

API host

https://api.bulwrk.gg

Landing/

Status/status

Maintenance/maintenance

Command desk/app

Stagingstaging