SixAiy Status - Incident history https://sixaiy.instatus.com SixAiy Thu, 11 Dec 2025 10:42:07 +0000 Maintenance / Version Upgrade / Voice Fix Type: Incident Affected Components: Discord Bot Dec 11, 19:40:30 GMT+0 - Identified - We have found another bug >.<, we though we caught them all but not all of them it seems, we will apply a quick patch to see if we can fix the issue. Dec 11, 19:59:56 GMT+0 - Monitoring - We have applied a patch to the bot, it should fix the random shard crashing and also fix the random crashing when the bot errors out for stupid reasons. Dec 11, 20:11:13 GMT+0 - Monitoring - We have also repaired the new Galnet command now removing a webhook from galnet is easy as typing /galnet remove select\_channel\_by\_name Dec 11, 10:42:07 GMT+0 - Monitoring - The bot will be going down maintenance, we are preforming and version upgrade and the bot won't be available for the next few hours. Dec 11, 14:14:52 GMT+0 - Monitoring - Upgrades have been completed, we will continue to monitor the bot for the next few weeks making sure it hasn't got anymore problems. Type: Incident

Affected Components:

<p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>19:40:30</var> GMT+0</small><br><strong>Identified</strong> - We have found another bug >.<, we though we caught them all but not all of them it seems, we will apply a quick patch to see if we can fix the issue..</p> <p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>19:59:56</var> GMT+0</small><br><strong>Monitoring</strong> - We have applied a patch to the bot, it should fix the random shard crashing and also fix the random crashing when the bot errors out for stupid reasons..</p> <p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>20:11:13</var> GMT+0</small><br><strong>Monitoring</strong> - We have also repaired the new Galnet command now removing a webhook from galnet is easy as typing /galnet remove select\_channel\_by\_name.</p> <p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>10:42:07</var> GMT+0</small><br><strong>Monitoring</strong> - The bot will be going down maintenance, we are preforming and version upgrade and the bot won't be available for the next few hours..</p> <p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>14:14:52</var> GMT+0</small><br><strong>Monitoring</strong> - Upgrades have been completed, we will continue to monitor the bot for the next few weeks making sure it hasn't got anymore problems..</p> ]]> Thu, 11 Dec 2025 10:42:07 +0000 https://sixaiy.instatus.com/incident/cmj1b6o2s01qzcs3dsq31pnt7 https://sixaiy.instatus.com/incident/cmj1b6o2s01qzcs3dsq31pnt7 Zeno is down Type: Incident Nov 21, 22:08:13 GMT+0 - Investigating - Zeno is down at the moment. This incident was automatically created by Instatus monitoring. Nov 24, 18:37:45 GMT+0 - Resolved - Zeno is back up. This incident was automatically resolved by Instatus monitoring. Type: Incident

<p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>22:08:13</var> GMT+0</small><br><strong>Investigating</strong> - Zeno is down at the moment. This incident was automatically created by Instatus monitoring..</p> <p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>18:37:45</var> GMT+0</small><br><strong>Resolved</strong> - Zeno is back up. This incident was automatically resolved by Instatus monitoring..</p> ]]> Fri, 21 Nov 2025 22:08:12 +0000 https://sixaiy.instatus.com/incident/cmi9evxjn002hhwagkblltt9a https://sixaiy.instatus.com/incident/cmi9evxjn002hhwagkblltt9a Website Issues Type: Incident Duration: 22 hours and 41 minutes Affected Components: gensokyobot.com Nov 17, 19:34:19 GMT+0 - Investigating - We are currently investigating this incident. We know that the website is loading [sixaiy.com,](http://sixaiy.com) which is not normal, and we are working on this problem. We will provide more information when we have it. Nov 18, 18:15:21 GMT+0 - Resolved - This has been resolved. Type: Incident

Duration: 22 hours and 41 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>19:34:19</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. We know that the website is loading [sixaiy.com,](http://sixaiy.com) which is not normal, and we are working on this problem. We will provide more information when we have it..</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>18:15:21</var> GMT+0</small><br><strong>Resolved</strong> - This has been resolved..</p> ]]> Mon, 17 Nov 2025 19:34:19 +0000 https://sixaiy.instatus.com/incident/cmi3jmoj4055df5p1g2lmyvoq https://sixaiy.instatus.com/incident/cmi3jmoj4055df5p1g2lmyvoq Music Core Type: Incident Duration: 12 days, 19 hours and 48 minutes Affected Components: Discord Bot Nov 23, 11:55:02 GMT+0 - Resolved - We have managed to fix the music core of the bot, rewriting the whole handling on how to get the bot to stream the music was a bit of a mess around but it works fine now, I will be booting up a temp GensokyoBot on my other server Yuki, it will handle the bot for now until we have Zeno fixed. Nov 23, 11:59:31 GMT+0 - Postmortem - We will still monitor the music core, but everything seems to be fixed now Nov 16, 22:14:54 GMT+0 - Identified - The music core of the bot is unable to currently play music. We have identified the issue to be either ffmpeg or Eris.js itself. We are still looking into this issue, and when we have more details, we will provide more information and try to repair it. We are working on a minor patch to resolve this issue, but there are no guarantees Nov 21, 22:11:49 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 23, 12:16:10 GMT+0 - Investigating - We had it working fine, but when we moved to the bot, it ended up breaking again. We will look into this more. Nov 29, 18:02:45 GMT+0 - Resolved - After much deliberation, we have scrapped the current release and left it in recovery mode. We are working on a new version that will have the repairs done to the music aspect of the bot. There is no eta for the new version release. We apologise for any issues you have been having with our bot. We are working hard to get this resolved. Type: Incident

Duration: 12 days, 19 hours and 48 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>11:55:02</var> GMT+0</small><br><strong>Resolved</strong> - We have managed to fix the music core of the bot, rewriting the whole handling on how to get the bot to stream the music was a bit of a mess around but it works fine now, I will be booting up a temp GensokyoBot on my other server Yuki, it will handle the bot for now until we have Zeno fixed..</p> <p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>11:59:31</var> GMT+0</small><br><strong>Postmortem</strong> - We will still monitor the music core, but everything seems to be fixed now.</p> <p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>22:14:54</var> GMT+0</small><br><strong>Identified</strong> - The music core of the bot is unable to currently play music. We have identified the issue to be either ffmpeg or Eris.js itself. We are still looking into this issue, and when we have more details, we will provide more information and try to repair it. We are working on a minor patch to resolve this issue, but there are no guarantees.</p> <p><small>Nov <var data-var='date'> 21</var>, <var data-var='time'>22:11:49</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>12:16:10</var> GMT+0</small><br><strong>Investigating</strong> - We had it working fine, but when we moved to the bot, it ended up breaking again. We will look into this more..</p> <p><small>Nov <var data-var='date'> 29</var>, <var data-var='time'>18:02:45</var> GMT+0</small><br><strong>Resolved</strong> - After much deliberation, we have scrapped the current release and left it in recovery mode. We are working on a new version that will have the repairs done to the music aspect of the bot. There is no eta for the new version release. We apologise for any issues you have been having with our bot. We are working hard to get this resolved..</p> ]]> Sun, 16 Nov 2025 22:14:54 +0000 https://sixaiy.instatus.com/incident/cmi29xbsk002nl80zuzmp36je https://sixaiy.instatus.com/incident/cmi29xbsk002nl80zuzmp36je Service Down Type: Incident Duration: 13 hours and 32 minutes Affected Components: Discord Bot, gensokyobot.com, sixaiy.com May 21, 18:32:38 GMT+0 - Investigating - We are currently investigating this incident, we will get back with more information when we know more. May 22, 08:04:36 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 13 hours and 32 minutes

Affected Components: , ,

<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>18:32:38</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident, we will get back with more information when we know more..</p> <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>08:04:36</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 21 May 2025 18:32:38 +0000 https://sixaiy.instatus.com/incident/cmaya607m001cq1m95yxqtv4y https://sixaiy.instatus.com/incident/cmaya607m001cq1m95yxqtv4y Service Maintenance Type: Incident Duration: 13 days, 9 hours and 5 minutes Affected Components: Discord Bot May 8, 09:27:04 GMT+0 - Identified - we are reworking the server that the bot is hosted on. May 21, 18:31:58 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 13 days, 9 hours and 5 minutes

Affected Components:

<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>09:27:04</var> GMT+0</small><br><strong>Identified</strong> - we are reworking the server that the bot is hosted on..</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>18:31:58</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 8 May 2025 09:27:04 +0000 https://sixaiy.instatus.com/incident/cmaf5ydd000ll94cp1481ykgj https://sixaiy.instatus.com/incident/cmaf5ydd000ll94cp1481ykgj Network Outages Type: Incident Duration: 18 days, 9 hours and 41 minutes Affected Components: gensokyobot.com, sixaiy.com Sep 27, 12:30:00 GMT+0 - Investigating - We are currently experiencing at networking failure affecting the functions regarding the operations of [gensokyobot.com](http://gensokyobot.com) and [sixaiy.com](http://sixaiy.com) We are working on resolving this issue and we apologize for any impacts this may cause. Sep 27, 22:06:09 GMT+0 - Identified - We regret to inform you that due to a severe storm impacting the region, our data center has experienced a loss of connectivity. Our team is working closely with our partners and our carrier providers to restore services as quickly as possible. We understand the inconvenience this may cause, and we deeply appreciate your patience and understanding during this time. Please be assured that we are doing everything in our power to minimize the disruption, and we will continue to provide updates as the situation develops. Sep 27, 22:06:34 GMT+0 - Monitoring - Our data center has remained operational and has had power, although it has been intermittent. Our backup diesel generators have been running as needed. The high-efficiency UPS systems are also functioning as expected to provide stability during any power fluctuations. However, the external infrastructure surrounding the data center has been significantly impacted by the hurricane. This includes widespread power outages and severe damage to carrier networks, which has affected connectivity. Despite our multiple entry points, the external carriers’ infrastructure has not been fully restored. We are working closely with our partners to resolve this as quickly as possible, but their repair efforts are being delayed due to the extensive damage in the area. We are monitoring the situation closely and will continue to provide updates periodically. We greatly appreciate your patience and understanding during this challenging time. Sep 28, 21:27:03 GMT+0 - Identified - Unfortunately, we have not received any significant updates from our carrier partners as the entire region has been severely affected by the storm. We are unable to provide an estimated time for resolution as all repairs are being handled by carriers and power companies across the region. We share in the frustration and understand the desire to expedite the process, but we are unable to do so. I want to clarify that our facility did not lose power during the storm. The facility is on the same grid as Emergency Services, and as of yesterday, it was back on utility power, with the generators no longer in use. We appreciate everyone's concerns for our well-being. We have staff on-site and have been in touch with all staff in the area. While some are currently blocked in by storm damage, we can confirm that all staff are safe and sound. Thank you for your prayers and well wishes. Sep 29, 07:51:40 GMT+0 - Resolved - Things seem to be back to operational mode, we will keep monitoring the sites to see if there are any further outages Type: Incident

Duration: 18 days, 9 hours and 41 minutes

Affected Components: ,

<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently experiencing at networking failure affecting the functions regarding the operations of [gensokyobot.com](http://gensokyobot.com) and [sixaiy.com](http://sixaiy.com) We are working on resolving this issue and we apologize for any impacts this may cause..</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>22:06:09</var> GMT+0</small><br><strong>Identified</strong> - We regret to inform you that due to a severe storm impacting the region, our data center has experienced a loss of connectivity. Our team is working closely with our partners and our carrier providers to restore services as quickly as possible. We understand the inconvenience this may cause, and we deeply appreciate your patience and understanding during this time. Please be assured that we are doing everything in our power to minimize the disruption, and we will continue to provide updates as the situation develops..</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>22:06:34</var> GMT+0</small><br><strong>Monitoring</strong> - Our data center has remained operational and has had power, although it has been intermittent. Our backup diesel generators have been running as needed. The high-efficiency UPS systems are also functioning as expected to provide stability during any power fluctuations. However, the external infrastructure surrounding the data center has been significantly impacted by the hurricane. This includes widespread power outages and severe damage to carrier networks, which has affected connectivity. Despite our multiple entry points, the external carriers’ infrastructure has not been fully restored. We are working closely with our partners to resolve this as quickly as possible, but their repair efforts are being delayed due to the extensive damage in the area. We are monitoring the situation closely and will continue to provide updates periodically. We greatly appreciate your patience and understanding during this challenging time..</p> <p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>21:27:03</var> GMT+0</small><br><strong>Identified</strong> - Unfortunately, we have not received any significant updates from our carrier partners as the entire region has been severely affected by the storm. We are unable to provide an estimated time for resolution as all repairs are being handled by carriers and power companies across the region. We share in the frustration and understand the desire to expedite the process, but we are unable to do so. I want to clarify that our facility did not lose power during the storm. The facility is on the same grid as Emergency Services, and as of yesterday, it was back on utility power, with the generators no longer in use. We appreciate everyone's concerns for our well-being. We have staff on-site and have been in touch with all staff in the area. While some are currently blocked in by storm damage, we can confirm that all staff are safe and sound. Thank you for your prayers and well wishes..</p> <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>07:51:40</var> GMT+0</small><br><strong>Resolved</strong> - Things seem to be back to operational mode, we will keep monitoring the sites to see if there are any further outages.</p> ]]> Fri, 27 Sep 2024 12:30:00 +0000 https://sixaiy.instatus.com/incident/cm1l9u00h000ttminul1p9bgd https://sixaiy.instatus.com/incident/cm1l9u00h000ttminul1p9bgd GensokyoBot - 0.7.3 Development Type: Maintenance Duration: 29 days and 14 hours Affected Components: Discord Bot Oct 15, 23:41:16 GMT+0 - Completed - GensokyoBot Update to 0.7.3/0.7.4 is postponed until further notice. Sep 16, 09:51:00 GMT+0 - Identified - We will be performing maintenance over the next month with the bot, we have a few new backend integrations that will allow us much more control over the bot including monitoring the bot's uptime, total servers, active radio players, and active radio listeners. dont worry there will not be any discord id's and names involved in this, we keep privacy to the maximum, Over the next 2-3 months we will be making a lot of changes, and these changes can be seen from our other bot Compassion (TARDIS Type 102)#4201 Sep 17, 21:39:36 GMT+0 - Identified - Work is underway on the new backend of GensokyoBot allowing us to manage the bot in a much easier way. Oct 4, 17:10:47 GMT+0 - Identified - We are still conducting the upgrades to the bot we have no specific time for concussion but we will try to provide updates as things keep on developing. Type: Maintenance

Duration: 29 days and 14 hours

Affected Components:

<p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>23:41:16</var> GMT+0</small><br><strong>Completed</strong> - GensokyoBot Update to 0.7.3/0.7.4 is postponed until further notice..</p> <p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>09:51:00</var> GMT+0</small><br><strong>Identified</strong> - We will be performing maintenance over the next month with the bot, we have a few new backend integrations that will allow us much more control over the bot including monitoring the bot's uptime, total servers, active radio players, and active radio listeners. dont worry there will not be any discord id's and names involved in this, we keep privacy to the maximum, Over the next 2-3 months we will be making a lot of changes, and these changes can be seen from our other bot Compassion (TARDIS Type 102)#4201.</p> <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>21:39:36</var> GMT+0</small><br><strong>Identified</strong> - Work is underway on the new backend of GensokyoBot allowing us to manage the bot in a much easier way..</p> <p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>17:10:47</var> GMT+0</small><br><strong>Identified</strong> - We are still conducting the upgrades to the bot we have no specific time for concussion but we will try to provide updates as things keep on developing..</p> ]]> Mon, 16 Sep 2024 09:51:00 +0000 https://sixaiy.instatus.com/maintenance/cm14tyddl002dydx2aruewyv6 https://sixaiy.instatus.com/maintenance/cm14tyddl002dydx2aruewyv6 Music Playing Issues Type: Incident Duration: 8 days and 15 minutes Affected Components: Discord Bot May 2, 17:40:36 GMT+0 - Investigating - We have identified that the bot won't play music, this is something to do with our player, we are unable to repair this problem currently as we are still trying to figure out what is creating the problem, we have looked into the code of the Library of the bot and the FFMPEG that it uses to play but for some reason these problems are still not able to be found out, we are talking with our development team about this issue and will update when we have more information. Jun 10, 17:55:14 GMT+0 - Resolved - We have resolved this problem regarding the music player we found out after much playing around that the newest version of node that we run is unable to work with the library we use but that has all been resolved. Type: Incident

Duration: 8 days and 15 minutes

Affected Components:

<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>17:40:36</var> GMT+0</small><br><strong>Investigating</strong> - We have identified that the bot won't play music, this is something to do with our player, we are unable to repair this problem currently as we are still trying to figure out what is creating the problem, we have looked into the code of the Library of the bot and the FFMPEG that it uses to play but for some reason these problems are still not able to be found out, we are talking with our development team about this issue and will update when we have more information..</p> <p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>17:55:14</var> GMT+0</small><br><strong>Resolved</strong> - We have resolved this problem regarding the music player we found out after much playing around that the newest version of node that we run is unable to work with the library we use but that has all been resolved..</p> ]]> Thu, 2 May 2024 17:40:36 +0000 https://sixaiy.instatus.com/incident/clvpj7yvk28572baojvj8nsep6 https://sixaiy.instatus.com/incident/clvpj7yvk28572baojvj8nsep6 Bot Upgrades Type: Incident Duration: 9 days, 21 hours and 16 minutes Affected Components: Discord Bot Aug 13, 14:53:47 GMT+0 - Resolved - This incident has been resolved. Aug 3, 17:37:28 GMT+0 - Identified - We are happy to announce GensokyoBot v0.7.2, during this time GensokyoBot won't be available for use since we will have to bring it down and check for minor bugs while this is happening. Aug 3, 18:06:15 GMT+0 - Monitoring - GensokyoBot v0.7.2 has been released. Type: Incident

Duration: 9 days, 21 hours and 16 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>14:53:47</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>17:37:28</var> GMT+0</small><br><strong>Identified</strong> - We are happy to announce GensokyoBot v0.7.2, during this time GensokyoBot won't be available for use since we will have to bring it down and check for minor bugs while this is happening..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>18:06:15</var> GMT+0</small><br><strong>Monitoring</strong> - GensokyoBot v0.7.2 has been released..</p> ]]> Thu, 3 Aug 2023 17:37:28 +0000 https://sixaiy.instatus.com/incident/clkvfwdun30856btohhng2b1c1 https://sixaiy.instatus.com/incident/clkvfwdun30856btohhng2b1c1 Server Fault Type: Incident Duration: 47 minutes Affected Components: Discord Bot Aug 3, 13:56:10 GMT+0 - Identified - We are unable to reboot the server at this current time, we have submitted a support ticket to the data center to have them reset the server and pull the power as our management console isn't allowing us access to the server. We will update you when we have more information regarding this issue Aug 3, 14:42:59 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 47 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>13:56:10</var> GMT+0</small><br><strong>Identified</strong> - We are unable to reboot the server at this current time, we have submitted a support ticket to the data center to have them reset the server and pull the power as our management console isn't allowing us access to the server. We will update you when we have more information regarding this issue.</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>14:42:59</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 3 Aug 2023 13:56:10 +0000 https://sixaiy.instatus.com/incident/clkv7zs3p117266fgofjvntiur5 https://sixaiy.instatus.com/incident/clkv7zs3p117266fgofjvntiur5 Server Upgrades Type: Incident Duration: 27 days, 22 hours and 37 minutes Affected Components: Discord Bot Aug 2, 22:42:48 GMT+0 - Monitoring - We are doing some server upgrades thus all services that use DS1-NC will be down until further notice. Aug 3, 09:53:25 GMT+0 - Resolved - We are underway restoring the backups from our backup server thus GensokyoBot should be back up in the next 30 mins Type: Incident

Duration: 27 days, 22 hours and 37 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>22:42:48</var> GMT+0</small><br><strong>Monitoring</strong> - We are doing some server upgrades thus all services that use DS1-NC will be down until further notice..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>09:53:25</var> GMT+0</small><br><strong>Resolved</strong> - We are underway restoring the backups from our backup server thus GensokyoBot should be back up in the next 30 mins.</p> ]]> Wed, 2 Aug 2023 22:42:48 +0000 https://sixaiy.instatus.com/incident/clkubd6nr375089blocsb7vrff6 https://sixaiy.instatus.com/incident/clkubd6nr375089blocsb7vrff6 Server Migration Type: Incident Duration: 5 days, 3 hours and 46 minutes Affected Components: Discord Bot Jul 28, 18:55:50 GMT+0 - Monitoring - We have just purchased our server and it's going to be moved within the next week to the new co-location rack during this time our services won't be available for some time we are unable to tell you how long this will take, we will update this before the scheduled move of DS1-NC to the new rack Aug 2, 22:41:24 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 5 days, 3 hours and 46 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>18:55:50</var> GMT+0</small><br><strong>Monitoring</strong> - We have just purchased our server and it's going to be moved within the next week to the new co-location rack during this time our services won't be available for some time we are unable to tell you how long this will take, we will update this before the scheduled move of DS1-NC to the new rack.</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>22:41:24</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 28 Jul 2023 18:55:50 +0000 https://sixaiy.instatus.com/incident/clkmy22qa9404baojacooe7sj https://sixaiy.instatus.com/incident/clkmy22qa9404baojacooe7sj Server Overhauls/Upgrades Type: Incident Duration: 3 hours and 37 minutes Affected Components: Discord Bot Jul 25, 11:33:44 GMT+0 - Investigating - We are undergoing server overhauls, during this time only our website for GensokyoBot will be available this will take up to 2 hours to complete once we have done this overhauls we will post another update Jul 25, 15:10:22 GMT+0 - Resolved - We have completed the server overhauls it took longer then we expected but all services should be back to normal for now. Type: Incident

Duration: 3 hours and 37 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>11:33:44</var> GMT+0</small><br><strong>Investigating</strong> - We are undergoing server overhauls, during this time only our website for GensokyoBot will be available this will take up to 2 hours to complete once we have done this overhauls we will post another update.</p> <p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>15:10:22</var> GMT+0</small><br><strong>Resolved</strong> - We have completed the server overhauls it took longer then we expected but all services should be back to normal for now..</p> ]]> Tue, 25 Jul 2023 11:33:44 +0000 https://sixaiy.instatus.com/incident/clki7xy84257193bgosfh3714fr https://sixaiy.instatus.com/incident/clki7xy84257193bgosfh3714fr DS1-NC Issues Type: Incident Duration: 16 hours and 16 minutes Jul 13, 10:10:13 GMT+0 - Resolved - This incident has been resolved. Jul 12, 17:53:45 GMT+0 - Investigating - We are currently investigating this incident. Jul 12, 18:53:32 GMT+0 - Monitoring - We have managed to get the server back online, we will continue to monitor the server for now. Jul 13, 19:43:11 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 16 hours and 16 minutes

<p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>10:10:13</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>17:53:45</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>18:53:32</var> GMT+0</small><br><strong>Monitoring</strong> - We have managed to get the server back online, we will continue to monitor the server for now..</p> <p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>19:43:11</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 12 Jul 2023 17:53:45 +0000 https://sixaiy.instatus.com/incident/clk00sl7w85398bcomutqlnkvb https://sixaiy.instatus.com/incident/clk00sl7w85398bcomutqlnkvb GensokyoBot Type: Incident Duration: 1 day, 9 hours and 19 minutes Affected Components: Discord Bot Jul 13, 19:43:26 GMT+0 - Resolved - This incident has been resolved. Jul 12, 10:24:46 GMT+0 - Identified - We are currently investigating the reason why the bot is currently down. what we can see is the datacenter is lost our DHCP leasing to our IP. We have contacted the datacenter and this is being resolved as of this post. We will update with more information once we know more. Type: Incident

Duration: 1 day, 9 hours and 19 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>19:43:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>10:24:46</var> GMT+0</small><br><strong>Identified</strong> - We are currently investigating the reason why the bot is currently down. what we can see is the datacenter is lost our DHCP leasing to our IP. We have contacted the datacenter and this is being resolved as of this post. We will update with more information once we know more..</p> ]]> Wed, 12 Jul 2023 10:24:46 +0000 https://sixaiy.instatus.com/incident/cljzkr6dj97155bsolphjg9rai https://sixaiy.instatus.com/incident/cljzkr6dj97155bsolphjg9rai