Incidents | VaultCord Incidents reported on status page for VaultCord https://status.vaultcord.com/ https://d1lppblt9t2x15.cloudfront.net/logos/a5f795c40ec426a5e1cc3283cda07681.png Incidents | VaultCord https://status.vaultcord.com/ en Bot was ONLINE, uptime checker misconfigured https://status.vaultcord.com/incident/432439 Fri, 20 Sep 2024 20:21:00 -0000 https://status.vaultcord.com/incident/432439#a3c34f1c68c6b3a0d05dae3d5af6f7d1572cdaa399add67d5a30c23b47effe68 Maintenance completed Bot was ONLINE, uptime checker misconfigured https://status.vaultcord.com/incident/432439 Thu, 19 Sep 2024 19:25:00 -0000 https://status.vaultcord.com/incident/432439#817fd5d5635b586e6dfcfdf9776ab47398c6b8244542732d46fd4aebf56ea8ee The bot was ONLINE and UP. We updated the bot yesterday on 09.19.2024 and didn't update the uptime checking to reflect the changes. This is why it was appearing as down, even though it was online the entire time, according to our server logs. Changing IP for one of our servers https://status.vaultcord.com/incident/306579 Sun, 31 Dec 2023 09:59:00 -0000 https://status.vaultcord.com/incident/306579#91eb4ce2fbb8fbc5428d454658a749e755f494859e5486958d436aa91999dc5d Maintenance completed Changing IP for one of our servers https://status.vaultcord.com/incident/306579 Sat, 30 Dec 2023 10:00:00 -0000 https://status.vaultcord.com/incident/306579#1f9f6831a359bedd55529ce4e1b59dc6eb3d8bd29cb1fcbbcb0fd9e18b60c491 Rate limit on Discord API encountered, changing IP for one of our servers. some bad person spammed our APIs API was down https://status.vaultcord.com/incident/285907 Sun, 12 Nov 2023 06:30:00 -0000 https://status.vaultcord.com/incident/285907#ca06bb086fe367d98c6e73b9d5df7001623a33a7ec44b62413ad2f898225ad75 Maintenance completed API was down https://status.vaultcord.com/incident/285907 Sun, 12 Nov 2023 06:00:00 -0000 https://status.vaultcord.com/incident/285907#3b507c5ae0b17701955e028e003b0770db973df97e080b08ffb147a5f4ef7b38 API was down for 5 minutes due to a configuration issue. Issue resolved and paid users had 1 week added to their subscription's expiration. The bot didn't go down, but the API serves as a middle-ware in between the status checker and the bot, which is why it was shown as down when it really wasn't down.