Hitting the connection limit means that Discord will reset the token, preventing the bot from communicating with Discord in any way. It’s up to the owner to update their application with the new token.Ī bot’s token acts like a password, which tells Discord which bot is trying to connect, and that it has the proper authentication to do so. Upon hitting this limit, all active sessions for the bot will be terminated, the bot’s token will be reset, and the owner will receive an email notification. So, what happens if a bot tries to connect too many times?Īccording to Discord’s API documentation,
Streamcord, along with many other popular bots, are granted an extension of this limit to 2000 per 24 hours. Graph of shard connects, resumes, and disconnects before and after the outage.īecause connecting to the gateway can be intensive, Discord limits most bots to 1000 connections per 24 hours. This continued for several hours leading up until the outage. This caused some of the bot’s websocket connections to Discord’s gateway to be dropped, prompting the need for them to connect again. What caused the outageĪround 6:12 AM Eastern Time, our servers began experiencing occasional network issues. We apologize for the downtime and any disruptions caused by it, and we’re making changes to ensure that this kind of outage never happens again. On the morning of February 24th, our internal systems suffered a failure that resulted in a disruption of service for notifications and Live Role that lasted approximately 2 and a half hours, followed up by a further disruption of Legacy notifications service that lasted for another 21 hours. Uptime and consistency are some of the most important aspects that our users rely on, and unfortunately, we recently failed to meet this need. Hundreds of thousands of Discord servers rely on Streamcord to provide them with up-to-date Twitch notifications and Live Role. The outage, as visualized by Streamcord’s status page.
0 kommentar(er)
