- ResolvedResolved
This incident has been open for a few days, marking as resolved
- IdentifiedIdentified
so uh, turns out I am a dumbass and due to my lack of braincells I am the reason why Fire left all of those guilds basically, I ran the TypeScript rewrite of Fire on the main token to check resource usage with all 631 guilds and since the hosted instance of the rewrite is for premium guilds only, I had "premiumOnly" set to true meaning it left guilds that weren't premium. It thankfully didn't get down to just premium guilds but boy am I pissed that I didn't realize what happened sooner. I sincerely apologize for my stupidity. To make it up to y'all, I will make Fire TS available for non-premium guilds too as soon as I can get this update deployed correctly. This incident will stay open for another little while to allow people to see the update.
- InvestigatingInvestigating
I am opening an incident for this so that people can hopefully find it if Fire has left their guild and reinvite it. Updates will be posted here and in Fire's Discord ( https://inv.wtf/fire ); ----- So uh, not the kind of announcement I'm wanting to make but it seems somehow Fire has left most of it's guilds. It went from 639 to 151. Around the time it happened, Fire got disconnected from the gateway so I'm hoping that it's just a bug and the guilds it lost will return but if Fire has left your guild I would strongly recommend just reinviting it from https://inv.wtf/bot just in case it doesn't magically return. I have also reset Fire's token in case it somehow got leaked, which is very unlikely as Fire has never had a token leak. I apologize for any inconvenience this may have caused. I know a lot of you rely on Fire for managing your server e.g. logging or moderation. I will be investigating the cause for this and will provide new information as soon as I find anything. Once again I am deeply sorry for any inconvenience caused.