Fire - Notice history

All systems operational

Bot - Operational

100% - uptime
Feb 2026 · 99.91%Mar · 100.0%Apr · 100.0%
Feb 2026
Mar 2026
Apr 2026

Beta Bot - Operational

100% - uptime
Feb 2026 · 99.99%Mar · 99.99%Apr · 100.0%
Feb 2026
Mar 2026
Apr 2026

Website - Operational

100% - uptime
Feb 2026 · 99.99%Mar · 100.0%Apr · 100.0%
Feb 2026
Mar 2026
Apr 2026

Notice history

Apr 2026

No notices reported this month

Mar 2026

Discord API Issues (dsv750sj44fn)
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    Discord has implemented a fix and both error rates & latency have returned closer to expected levels. I will continue monitoring for some time to ensure things are fully resolved

  • Identified
    Identified

    Fire is currently experiencing elevated latency & error rates due to issues with Discord's API. Discord has posted about the issue on their own status page, https://discordstatus.com/incidents/

Feb 2026

Infrastructure Upgrades
  • Completed
    February 18, 2026 at 1:25 PM
    Completed
    February 18, 2026 at 1:25 PM

    Maintenance has completed successfully. There are a few issues with certain features/tooling but they're minor enough that I'm willing to let them be for now and will work on them within the next few days

  • Update
    February 18, 2026 at 12:05 PM
    Update
    February 18, 2026 at 12:05 PM

    Everything should be up and running now with all DNS records recreated with their new values. Some users may experience issues due to delays in DNS propagation and SSL certificate provisioning but these should eventually resolve themselves

    Extensive review & monitoring will be taking place for the next hour or so to ensure nothing has been missed and to do some cleanup of older resources

  • Update
    February 18, 2026 at 11:28 AM
    Update
    February 18, 2026 at 11:28 AM

    Fire is now back online and now running in Kubernetes!

    Next up will be reconfiguring DNS records which may take some time due to SSL certificate provisioning. This means that web services will still be unavailable for a while

  • In progress
    February 18, 2026 at 11:00 AM
    In progress
    February 18, 2026 at 11:00 AM
    Maintenance is now in progress
  • Planned
    February 18, 2026 at 11:00 AM
    Planned
    February 18, 2026 at 11:00 AM

    During this time, we will be performing upgrades to Fire's infrastructure, changing how the bot and related applications are deployed/managed on the machine. These upgrades have already been tested in a production-like environment by moving Fire Beta to a separate machine for testing & learning.

    The main upgrade should realistically only take 15-20 minutes with most of the time being spent replacing updating configurations for services exposed to the web as they can no longer be simply pointed to localhost & some port and even then, I don't expect this to take the entire duration of the maintenance but I'd rather schedule a larger window just in case

    For anyone interested, I am moving Fire away from running directly on the machine and being managed via PM2 to using Docker containers & Kubernetes. This move will make it much easier to keep Fire up to date as upgrading the OS or Node version is as simple as changing the image used. It also comes with a more maintainable solution for offsite backups as I've configured the Postgres cluster with automatic backups to CloudFlare R2 rather than moving them to my Mac every so often

Feb 2026 to Apr 2026

Next