Fire - Notice history

All systems operational

Bot - Operational

100% - uptime
Mar 2024 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2024
Apr 2024
May 2024

Website - Operational

100% - uptime
Mar 2024 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2024
Apr 2024
May 2024

Notice history

May 2024

No notices reported this month

Apr 2024

Google Command Unavailable
  • Resolved
    Resolved

    Google has approved Fire's application and after resolving an issue that occurred once approved & monitoring to ensure that it continued to work, it is now ready for release! It will be released next week after an upcoming maintenance to upgrade things that were previously blocked by the Google command

  • Monitoring
    Monitoring

    The command is now available again but without the full update as that will remain locked away until Google approves it You may notice some smaller changes to the responses though and there's a hidden trick it can do :)

  • Identified
    Identified

    As part of ongoing work to upgrade the /google command, it seems that the credentials got cycled which has broken the command in production I am working very hard on a big update to it which will resolve the issue but until this is released, the command will be unavailable

Mar 2024

Minecraft log scanning not working for Forge logs
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    The website appears to be back up and running so FIre should respond almost instantly to uploaded Forge logs. I'll keep this incident open for a while just in case it goes down again

  • Update
    Update

    An update is currently being deployed that should resolve it not responding at all, though it'll still be slow while it waits for the requests to time out

  • Identified
    Identified

    Fire's log scanning feature is currently unable to provide solutions or recommendations for Forge logs. It appears that Forge's website is currently timing out which results in the bot not being able to fetch version data

Hetzner Outage
  • Resolved
    Resolved

    Fire was offline during from 1:04 PM UTC to 1:45 PM UTC due to a Hetzner outage.

Potential Discord outage
  • Resolved
    Resolved

    Discord has implemented a fix and Fire hasn't disconnected in a while so it's probably fixed. I'm about to watch Dune: Part Two though so I can't monitor it 😅

  • Update
    Update

    Discord has now posted about it on their status page https://discordstatus.com/incidents/w4ddkglpbz0x

  • Identified
    Identified

    Discord is aware of the issues so they will hopefully be resolved soon

  • Investigating
    Investigating

    Both Fire & my own client are currently getting disconnected from Discord frequently I've heard reports of others experiencing the same or similar issues so it seems that Discord may be having some issues at the moment If you see Fire go offline, it should come back shortly afterwards as I have set up alerts to monitor this and will use them to identify disconnected shards and restart them so they come back sooner

Mar 2024 to May 2024

Next