Fire - Notice history

All systems operational

Bot - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 99.94%
Dec 2024
Jan 2025
Feb 2025

Website - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 99.94%
Dec 2024
Jan 2025
Feb 2025

Notice history

Jan 2025

Migration to rewrite of Vanity URLs & Redirects
  • Completed
    January 30, 2025 at 4:43 PM
    Completed
    January 30, 2025 at 4:43 PM

    Everything is working as expected. If you encounter any issues, please report them in the Fire Discord (https://discord.gg/firebot)

  • Update
    January 30, 2025 at 4:28 PM
    In progress
    January 30, 2025 at 4:28 PM

    The issue regarding redirects has been fixed and they are now fully operational. I'll be monitoring it for the next 10 or so minutes to ensure no other issues appear

  • Update
    January 30, 2025 at 4:25 PM
    In progress
    January 30, 2025 at 4:25 PM

    Fire has now been updated, however, an issue has been found regarding redirects. At the moment, it seems all redirects are leading to an error page, rather than the intended destination

    This issue is currently being investigated and a fix will be made and deployed as soon as the cause is found

  • Update
    January 30, 2025 at 4:07 PM
    In progress
    January 30, 2025 at 4:07 PM

    After a slight mishap with the switchover (I forgot to add a trailing slash in the configurations), inv.wtf is now pointing to Aether instead of the standalone service.

    The old service has now been shut down so if you encounter any issues with 502 errors, please let me know in the Fire Discord server (https://discord.gg/firebot)

    Next up is updating the bot. First, the update will be deployed to Fire Beta just for final testing and then it will be deployed to the main bot

  • Update
    January 30, 2025 at 4:02 PM
    In progress
    January 30, 2025 at 4:02 PM

    I have restarted Aether before moving the domains over to ensure it has the latest data (since the bot doesn't currently send the request to refresh to it)

    The Vanity URL & Redirect modules have been disabled on the bot now and the switchover will occur within the next minute or so

  • In progress
    January 30, 2025 at 4:00 PM
    In progress
    January 30, 2025 at 4:00 PM
    Maintenance is now in progress
  • Planned
    January 30, 2025 at 4:00 PM
    Planned
    January 30, 2025 at 4:00 PM

    The current service handling Vanity URLs & Redirects was the first project I worked on in TypeScript which means it's very old, horribly written and a pain to work with, which is why I spent the last few days rewriting parts of it and merging them into Aether since the service already relied on it for some features so why not just combine 'em!

    The switch from the separate service to Aether should be mostly instant & seamless. Everything should pretty much be the same except for response times which will be quicker due to changes in caching & click vs. link behavior. The only thing that will not be instant & seamless is updating the bot.

    Fire currently sends a HTTP request to the original service whenever a vanity/redirect is created, updated or deleted and this results in all data being reloaded, rather than just the specific item that changed. For the new merged version, it'll send a request over the existing websocket connection and that will either reload the server's vanities or reload the specific redirect, not everything.

    Because it is moving away from HTTP, it can't be as seamless as everything else since there is no endpoint to reload data in Aether for it to use once the switch has taken place. This will however only impact creating/updating/deleting vanities & redirects for a few minutes while the bot updates and these features will be disabled shortly before the switch takes place and will return as soon as the bot has restarted

Deploying various updates
  • Completed
    January 23, 2025 at 12:10 AM
    Completed
    January 23, 2025 at 12:10 AM

    👍

  • Update
    January 22, 2025 at 11:45 PM
    In progress
    January 22, 2025 at 11:45 PM

    Fire & Aether are now back online with everything deployed. I'll be keeping a close eye on things for roughly 15 minutes before I mark this as complete

  • Update
    January 22, 2025 at 11:41 PM
    In progress
    January 22, 2025 at 11:41 PM

    After some small reminder related bugs (mainly related to edits) discovered after the staging deploy, it is now ready to go to production. The main Fire bot & Aether instance will now go offline

  • In progress
    January 22, 2025 at 11:17 PM
    In progress
    January 22, 2025 at 11:17 PM

    Staging instances of Fire & Aether will soon go offline to deploy the updates there for a final check before being deployed to production

  • Planned
    January 22, 2025 at 11:16 PM
    Planned
    January 22, 2025 at 11:16 PM

    At this time, I will be deploying changes to both Fire & Aether which need to be done simultaneously, meaning both need to be taken offline temporarily

    These changes are primarily related to new reminders code but also contain some changes which should help with internal monitoring falsely claiming that a cluster has been disconnected, resulting in alerts being sent to me and this page updated.

    These changes were not intended to go out just yet but with the changes to fix monitoring issues, it has moved all changes up. The reminder changes have been tested thoroughly but there may be some edge cases that I missed in testing so if you encounter any issues related to reminders, please let me know in the Fire Discord (discord.gg/firebot)

Dec 2024

No notices reported this month

Dec 2024 to Feb 2025

Next