Fire - Notice history

All systems operational

Bot - Operational

100% - uptime
Jun 2020 · 100.0%Jul · 100.0%Aug · 100.0%

Previous page

Next page

Jun 2020
Jul 2020
Aug 2020

Website - Operational

100% - uptime
Jun 2020 · 100.0%Jul · 100.0%Aug · 100.0%

Previous page

Next page

Jun 2020
Jul 2020
Aug 2020

Notice history

Aug 2020

Cloudflare/Discord Outage
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    From http://stspg.io/fbk53trwrfsz: "As the major provider that was experiencing issues has implemented a fix in their network, other global network providers have started to re-enable their peering sessions with it. We are continuing to see improved reachability and monitoring the situation."

  • Update
    Update

    Fire still seems to be unaffected by this incident. If you notice any issues feel free to drop a message in the Fire support server, https://inv.wtf/fire :) Cloudflare are continuing to engage with their partners and fixes are being implemented with other transit providers to resolve the ongoing issues. You can find more info about this incident at the following sites; https://www.cloudflarestatus.com/incidents/hptvkprkvp23 https://status.ctl.io/history/f19a0555-abbd-4038-91cb-b55a7645c1f5 https://discordstatus.com/incidents/dv69h597l1z2

  • Identified
    Identified

    It seems both Cloudflare & Discord are having issues at the moment and due to Fire's heavy reliance on these services, it may have issues too. For now everything seems fine but I'm opening this incident now so it's easier to get updates out if anything happens. Cloudflare incident: https://www.cloudflarestatus.com/incidents/hptvkprkvp23 Discord incident: https://discordstatus.com/incidents/dv69h597l1z2

Google command returning Cloudflare error
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    It seems that the command is working once again (even though I changed nothing) so I have re-enabled it. I am monitoring for errors to ensure it's actually working correctly.

  • Investigating
    Investigating

    There seems to be an issue with the "google" command where instead of the response from the Google Assistant, it is returning a 520 Cloudflare error. The command has been disabled globally while I investigate

Internal Server Error when attempting to join a Public Guild
  • Resolved
    Resolved

    Seems everything is working fine now. If you're wondering what the issue was, Centra seems to send requests with an empty User Agent if you don't set one and I recently modified my firewall to block empty User Agents due to some attacks. Once that issue was resolved, another issue appeared, specifically involving permission checking. The API checks if the guild has enabled the public feature in Fire with the "$public" command or has the DISCOVERABLE feature but this seemed to be failing. Switching from bigints to strings seems to have resolved it though.

  • Monitoring
    Monitoring

    A fix has been implemented and we are monitoring the results.

  • Investigating
    Investigating

    While attempting to apply a patch, another issue has come up and is being investigated. I should have more details soon.

  • Identified
    Identified

    The issue has been identified and a temporary fix has been put in place. A full patch is being worked on.

  • Investigating
    Investigating

    It seems there's an issue with joining public guilds through FIre's public servers page. This issue is currently being investigated.

Issues with "block" feature
  • Resolved
    Resolved

    This incident has been resolved.

  • Identified
    Identified

    I have located the cause of the issue and am working on a fix, this shouldn't take too long

  • Investigating
    Investigating

    There seems to be an issue with the "unblock" command failing with an error meaning you cannot unblock users. I am looking into the issue now

Jul 2020

No notices reported this month

Jun 2020

No notices reported this month

Jun 2020 to Aug 2020

Next