Check an outage and send a useful incident report

Start at the public status page. Check whether the component or location associated with your service has an active incident or maintenance notice. An overall green indicator does not rule out a problem affecting only your application.

Run a short check

1. Note the first failure time and your timezone.
2. Check your account service status and any unpaid invoice.
3. Open the management panel. Does it load, and is the application running?
4. Read the most recent console error without repeatedly restarting the service.
5. Test from another connection or device where practical.
6. Compare access by the service's actual address with access through your custom domain.

If the direct address works but the domain does not, investigate DNS. If the panel works but the application crashes immediately, collect the startup error. If the panel and application both fail, include both symptoms in your report.

Send support the evidence

Provide the service ID, affected address/port, error text, approximate start time, timezone and checks already performed. Say whether all users are affected or only one connection. Remove tokens, passwords and personal information from logs.

Should I reinstall during a suspected outage?

Avoid destructive changes while the cause is unclear. A reinstall can remove evidence or application data without fixing a network issue. Preserve the current state and ask support first if recovery would be destructive.

Where will maintenance updates appear?

Check website announcements and the status page. Discord updates depend on the configured community channels. Use a private ticket for account-specific details; a public announcement cannot confirm the state of every customer order.

Is every interruption an SLA claim?

Eligibility and exclusions are defined in the published service level agreement. Keep the relevant incident times and contact support for a review rather than assuming a credit applies automatically.