Service Status
Past Incidents
LAX-Node-001
1 updateLAX-Node-001 is temporally offline to resolve a recent abuse incident.
Duration: 3 hours
This incident has been resolved.
File Saves
3 updatesWe're aware of an issue where saving files through the panel may fail with a "Request failed with status code 403" error. Investigating now.
Duration: 54 minutes
The panel file save issue has been resolved. All file edits should now save normally. If you continue to experience problems, please open a ticket.
A fix has been applied. Save attempts should now succeed; monitoring to confirm the issue does not return.
The cause has been identified, a security rule is incorrectly blocking some plugin file saves through the panel. Working on a fix.
Server Creation on Free Node
2 updatesServer Creation on Free Node is abnormal.
Duration: 1 day
This incident has been resolved.
A fix has been applied.
Login Logic
3 updatesWe have identified the issue and deployed a fix. We will continue monitoring to ensure stability, please let us know if you experience any further issues.
Duration: 2 days
This incident has been resolved.
We have deployed a fix and currently monitoring.
Our game panels worker kept erroring out at one function.
Scheduled Security Maintenance in ~1hr.
1 updateWe are scheduling a security maintenance on 04/10/26 12:00 AM CST, expect 30 mins of downtime and a 2 hour maintenance window if we run into any errors.
Duration: 1 day
This incident has been resolved.
Expired wildcard cert for *.us.dracobyte.pro
1 updateA brief incident causing some services to be inaccessible has been resolved. Root cause: The wildcard cert for *.us.dracobyte.pro expired today. It was manually placed and never set up for auto-renewal.
What was fixed:
- Issued a new cert and implemented mitigations to prevent this from happening again.
Jeremiah Kroesche | Senior System Administrator
Duration: 1 minute
This incident has been resolved.
Panel Login Degraded
3 updatesNew users cannot login to our panel.
Duration: 18 minutes
Restarted the Supervisor worker process. Queue is now processing normally and draining.
The queue worker (Supervisor) crashed due to a transient database authentication error and entered a FATAL state, preventing automatic recovery even after the DB issue resolved itself.
Our queue worker can not connect to the database, we are currently implementing a fix.
No active incidents