Platform
Service Status
Publish measured NightCrew platform availability, incidents, maintenance, and uptime history.
Getting started
Open the public page
Use /status to review the dashboard, main bot, custom bots, database, scheduled content, social notifications, and developer webhooks.
Understand automatic health
Bot states use fresh presence heartbeats; database health uses a live query; automation and webhook states react to recent failures.
Publish an incident
From Server Health Center, choose severity and affected components, then post the first Investigating update.
Keep users informed
Add Identified and Monitoring updates as work progresses, then resolve the incident when service is stable.
Schedule maintenance
Publish the UTC start, end, expected impact, and affected components before planned work.
Integrate
Use /api/status for JSON monitoring or /status/feed.xml for RSS incident updates.
Settings reference
Use this reference when you need to check what a setting does.
Measured state calculated from current heartbeats, storage access, and recent delivery failures.
Operator-selected component state that temporarily replaces automatic health.
Minor maps to degradation, major to partial outage, and critical to major outage.
Timestamped Investigating, Identified, Monitoring, or Resolved message.
UTC period with affected components and expected impact.
Availability calculated from sanitized component checks; planned maintenance is not counted as failure.
How it works
Here’s what happens once you’ve finished setup.
- 1Monitor
Requests /api/status or the public page and records component checks.
- 2Detection
Automatic signals or an administrator confirm an issue.
- 3Communication
Incident updates appear on the public timeline and RSS feed.
- 4Recovery
The incident is resolved and automatic component health resumes.
Example
Open one major incident, select Social Notifications, publish Investigating, add Identified when the provider confirms trouble, Monitoring after recovery, then Resolve.
Permissions
- NightCrew platform administrator access for incident and maintenance controls
Tips
Component overrides should only be used for confirmed platform-wide issues, not one server's configuration problem.
Things to know
Do not publish customer server names, tokens, private logs, or exploit details in public incident updates.
Troubleshooting
No main-bot heartbeat has been recorded yet; wait for the running bot to synchronize presence.
A previously recorded custom-bot worker has not refreshed its heartbeat in five minutes.
Return the component override to Automatic after the incident is resolved.