Back to overview
Maintenance

Discord Tickets Public Instance Migration and Outage Resolution

May 24 at 12:00am BST  –  May 27 at 12:34am BST
Affected services
Discord Tickets (Public)
Daily MySQL backup (de-s7)

Resolved
May 27 at 12:34am BST

The migration has now since completed and the public bot is now fully back to normal. Thanks again for your patience!

Updated
May 26 at 10:33pm BST

The migration is (mostly) complete and the bot is online as the connection issues have resolved themselves.
We'll continue working on the code changes to limit the impact of the issues in the future.

The Portal may go offline several times tonight while the migration is finalised.

Updated
May 26 at 06:03pm BST

The bot appears to be connecting to Discord again without major issues so we are just wrapping up migration and making the final touches to bring the bot back online, though we may make a couple of changes over the coming days to improve stability and performance that could require downtime. We'll announce these and give plenty of notice if they happen.

Please note it may still take another couple of days until full service restoration. Thanks again for your patience as we work to resolve this issue.

Updated
May 25 at 06:15pm BST

We are now working towards determining the exact root cause of the previously identified issues preventing our migration and full service restoration. Some progress and improvements have been made but we still expect a complete outage for several more days. We sincerely apologise for this outage and appreciate your patience.

Updated
May 24 at 06:31pm BST

Due to an unrelated incident, the scope of the maintenance has significantly increased, and the migration is currently suspended. The migration will resume after the large code changes are complete.

The problem is similar to a previous incident (https://status.eartharoid.me/incident/535756), but we feel the solution used there would not work to our satisfaction right now.

Created
May 24 at 12:00am BST

Discord Tickets' Public Bot will be moved to a new hosting provider. Downtime is required to prevent data loss. The bot will be unavailable during this period.