All Systems Operational
Main Operational
90 days ago
99.75 % uptime
Today
Bot ? Operational
90 days ago
99.77 % uptime
Today
Website ? Operational
90 days ago
99.98 % uptime
Today
Cloudflare ? Operational
90 days ago
99.5 % uptime
Today
Backend Operational
90 days ago
99.87 % uptime
Today
Vanity URLs & Redirects ? Operational
90 days ago
99.79 % uptime
Today
Aether ? Operational
90 days ago
99.94 % uptime
Today
Extras Operational
90 days ago
99.99 % uptime
Today
Hastebin ? Operational
90 days ago
99.99 % uptime
Today
External ? Operational
90 days ago
99.97 % uptime
Today
GitHub API ? Operational
90 days ago
99.97 % uptime
Today
Sentry API ? Operational
90 days ago
99.95 % uptime
Today
Trello API ? Operational
90 days ago
99.95 % uptime
Today
Slack Apps/Integrations/APIs ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Gateway Latency ?
Fetching
Rest Latency ?
Fetching
Past Incidents
Feb 26, 2021

No incidents reported today.

Feb 25, 2021

No incidents reported.

Feb 24, 2021

No incidents reported.

Feb 23, 2021

No incidents reported.

Feb 22, 2021

No incidents reported.

Feb 21, 2021

No incidents reported.

Feb 20, 2021

No incidents reported.

Feb 19, 2021

No incidents reported.

Feb 18, 2021

No incidents reported.

Feb 17, 2021

No incidents reported.

Feb 16, 2021
Resolved - I had just recently been made aware of an issue with commands that use Fire's parseTime function (reminders & temp mutes/bans) not parsing times correctly if the time was at the start of the reason. This would result in the time being parsed as 0 minutes which resulted in errors while creating reminders (saying you can't set reminders for less than 2 minutes) and permanent mutes/bans rather than temporary.
This issue has been resolved as of 13:32 UTC and Fire should start parsing times correctly.

Note: If the time was NOT at the start of the reason, they were unaffected by this bug and therefore were being parsed correctly
Feb 16, 13:34 UTC
Feb 15, 2021

No incidents reported.

Feb 14, 2021

No incidents reported.

Feb 13, 2021
Completed - Just deployed some replay socket & DM slash command fixes. Everything seems good πŸ‘
Feb 13, 20:59 UTC
Verifying - I am once again verifying the status of the maintenance.

I sincerely apologise for the mess this maintenance has been but there were a few oversights in the update that caused some issues in production (mainly the lack of influx as I do not run an instance of influx when running Fire locally).

Stats are being reported correctly now and there does not seem to be any issues but I will leave this open for a while longer as the stats issue took a while to show itself.
Feb 13, 20:14 UTC
Update - I have fixed the issue with stats but I am going to need to take Aether offline for a minute or two as I'd like to clear influx to get rid of the mess that was written to it.

Slash commands, reminders, carbon and potentially more features will be affected
Feb 13, 20:08 UTC
In progress - It seems that stats tracking was broken in the process, leading to some unintended side effects. A fix is being worked on.
Feb 13, 19:32 UTC
Verifying - Verification is currently underway for the maintenance items.
Feb 13, 19:18 UTC
Update - Some issues have arisen while deploying the update to Fire. These should not affect functionality of the bot but if you do encounter any issues, it is likely these issues.

I am working on resolving them now!
Feb 13, 19:13 UTC
Update - Aether is back online, deploying the Fire update now
Feb 13, 19:11 UTC
Update - I am about to deploy the update to Aether which will involve taking Fire offline as there are breaking changes to the identify process.

Once Aether is back online, I will be able to deploy the Fire update, including the ecosystem file changes
Feb 13, 19:10 UTC
Update - Another change coming from this Aether update is the switch from gateway to rest for slash commands.

Slash commands will stop working on Fire in a moment as I switch it over and will resume functioning once the update to Aether has been deployed
Feb 13, 19:07 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 13, 19:03 UTC
Scheduled - During this time, I will be deploying an update to Aether which will remove the reliance on pm2's instance id for determining which process is which cluster. Instead, it will just assign the first available cluster id.

This has been tested locally and has worked flawlessly but as always issues may arise in production for the sole reason of it being in production so I will have an instance of Fire that doesn't connect to Aether ready to boot up if any issues occur to minimise downtime.

I will also be deploying a small change to Fire's ecosystem file (https://pm2.keymetrics.io/docs/usage/application-declaration/) that adds an exponential backoff for restarts if an error occurs and adds a max memory restart of 1GB.
Feb 13, 10:19 UTC
Feb 12, 2021

No incidents reported.