Fire - Notice history

The issue seems to have stemmed from Fire being stuck in a loop, constantly making requests to edit a channel, which resulted in it getting ratelimited. As far as I can tell, the edits were part of the permission role feature, so I've made a few changes to it which should a) help identify it and b) help resolve the issue

This feature is pretty old so it likely needs a rewrite to ensure things work smoothly, which has been added to my lengthy to-do list for Fire

For now, Fire is operational and should stay that way. If you encounter any issues, please report them in the Fire Discord (discord.gg/firebot)

Fire is now back online and looks to be operating just fine. I've made some changes that may help prevent the issue re-occurring but I'll be looking further into what caused this issue so that I can properly resolve it

Fire's VPS appears to have been blocked from accessing Discord's API due to exceeding ratelimits. It's unknown how this occurred at this time but for now, the bot has been turned off to avoid making requests while ratelimited.

It looks to be only an hour long block with about 50 minutes remaining so it shouldn't be down for long but unfortunately there's nothing that can be done other than waiting

Things look to have improved, requests aren't failing nearly as often and latency has returned to normal levels. I will continue to monitor requests for some time just to be sure it's fully resolved

Cloudflare have stated that things are now operating normally