OptiDesk Status - Incident history https://optidesk.instatus.com OptiDesk Sat, 11 Jul 2026 12:45:00 +0000 Intermittent service outage Type: Incident Duration: 17 minutes Affected Components: OptiDesk Servers Jul 11, 12:45:00 GMT+0 - Investigating - Due to a failure with our Internet Service Provider, service is currently degraded. Jul 11, 13:00:33 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 11, 13:02:18 GMT+0 - Resolved - The service failure has been eliminated. It will not bother you again. Type: Incident

Duration: 17 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>12:45:00</var> GMT+0</small><br><strong>Investigating</strong> - Due to a failure with our Internet Service Provider, service is currently degraded..</p> <p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>13:00:33</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>13:02:18</var> GMT+0</small><br><strong>Resolved</strong> - The service failure has been eliminated. It will not bother you again..</p> ]]> Sat, 11 Jul 2026 12:45:00 +0000 https://optidesk.instatus.com/incident/cmrgdazwz0jd50rq6wnahe3af https://optidesk.instatus.com/incident/cmrgdazwz0jd50rq6wnahe3af Incident with Discord Type: Incident Duration: 13 minutes Affected Components: OptiDesk Servers Jun 12, 09:46:00 GMT+0 - Investigating - We are currently investigating an issue regarding Discord authentication. OptiDesk is currently down. Jun 12, 09:48:00 GMT+0 - Monitoring - OptiDesk is online again, but we are still investigating the incident due to potential risks regarding security. No user action is required. Jun 12, 10:01:18 GMT+0 - Resolved - The incident is a false-alarm and was a result of Discord's automated systems. No action from users is required. Jun 12, 10:29:33 GMT+0 - Postmortem - TLDR: Nothing ever happens - we thought something did and proactively took down OptiDesk for 2 minutes. Summary On the 12th of June, 2026, we received an unexpected lockout of our administrative Discord account that hosts the Discord bot user. Out of an abundance of caution, and that we could not confirm the accounts security status, we immediately activated emergency procedures to rotate credentials to mitigate any incident. Further investigation revealed no breach, access or incident, and the OptiDesk application was immediately restored. Impact OptiDesk was unavailable to all guilds using the service from approximately 7:46PM until 7:48PM AEST. Total downtime: \~2 minutes Time to detect: \~N/A Resolution from detection: \~15 minutes, 18 seconds Please note that the Instatus 'downtime' shows the incident as 15 minutes long as that is the amount of time it took for us to complete the audit. Actual users would have only noticed around 2 minutes of downtime on the OptiDesk Discord application. This discrepancy is shown in our uptime numbers. Incident Details At around 7:44PM, the superuser of the OptiDesk application on Discord was locked out of their Discord account. After continual failed attempts at login hinting towards total lockout or account takeover, an incident was triggered and emergency protocols were activated in case of a security incident in progress. At 7:46PM, access was regained to the account and immediate rotation of OptiDesk credentials started, with servers unable to serve OptiDesk requests for the 2 minutes it took to update the credentials and reboot the servers. Following this, the On-Call Response Team were paged and a full-scale swift audit of all OptiDesk infrastructure commenced as per protocol, and an additional audit of the Discord bot user was commenced to ensure integrity of the application. At 7:50PM, OptiDesk staff deemed that nothing happened, and that the Discord lockout was a result of an automated action. Conclusion We are proud to have such robust security and emergency protocols for incidents such as these, and the activation of these protocols was extremely successful. The security of OptiDesk is our utmost priority, and times like these reaffirm our commitment to that. \- Liam Type: Incident

Duration: 13 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>09:46:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an issue regarding Discord authentication. OptiDesk is currently down..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>09:48:00</var> GMT+0</small><br><strong>Monitoring</strong> - OptiDesk is online again, but we are still investigating the incident due to potential risks regarding security. No user action is required..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>10:01:18</var> GMT+0</small><br><strong>Resolved</strong> - The incident is a false-alarm and was a result of Discord's automated systems. No action from users is required..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>10:29:33</var> GMT+0</small><br><strong>Postmortem</strong> - TLDR: Nothing ever happens - we thought something did and proactively took down OptiDesk for 2 minutes. Summary On the 12th of June, 2026, we received an unexpected lockout of our administrative Discord account that hosts the Discord bot user. Out of an abundance of caution, and that we could not confirm the accounts security status, we immediately activated emergency procedures to rotate credentials to mitigate any incident. Further investigation revealed no breach, access or incident, and the OptiDesk application was immediately restored. Impact OptiDesk was unavailable to all guilds using the service from approximately 7:46PM until 7:48PM AEST. Total downtime: \~2 minutes Time to detect: \~N/A Resolution from detection: \~15 minutes, 18 seconds Please note that the Instatus 'downtime' shows the incident as 15 minutes long as that is the amount of time it took for us to complete the audit. Actual users would have only noticed around 2 minutes of downtime on the OptiDesk Discord application. This discrepancy is shown in our uptime numbers. Incident Details At around 7:44PM, the superuser of the OptiDesk application on Discord was locked out of their Discord account. After continual failed attempts at login hinting towards total lockout or account takeover, an incident was triggered and emergency protocols were activated in case of a security incident in progress. At 7:46PM, access was regained to the account and immediate rotation of OptiDesk credentials started, with servers unable to serve OptiDesk requests for the 2 minutes it took to update the credentials and reboot the servers. Following this, the On-Call Response Team were paged and a full-scale swift audit of all OptiDesk infrastructure commenced as per protocol, and an additional audit of the Discord bot user was commenced to ensure integrity of the application. At 7:50PM, OptiDesk staff deemed that nothing happened, and that the Discord lockout was a result of an automated action. Conclusion We are proud to have such robust security and emergency protocols for incidents such as these, and the activation of these protocols was extremely successful. The security of OptiDesk is our utmost priority, and times like these reaffirm our commitment to that. \- Liam.</p> ]]> Fri, 12 Jun 2026 09:46:00 +0000 https://optidesk.instatus.com/incident/cmqaqucss09lzquezx4ddbw9p https://optidesk.instatus.com/incident/cmqaqucss09lzquezx4ddbw9p Immediate Switchover Type: Maintenance Duration: 13 hours and 40 minutes Affected Components: Website May 26, 09:14:00 GMT+0 - Identified - We are conducting an unplanned switchover to a new hosting provider due to technical problems. The OptiDesk website is currently unavailable. We apologize for the inconvenience. May 26, 09:15:00 GMT+0 - Identified - Starting maintenance. May 26, 09:20:09 GMT+0 - Identified - We are still working on restoring service to the website. We will deliver an update in 15-30 minutes. May 26, 09:32:19 GMT+0 - Identified - We are still working on restoring service due to several CDN failures. We are re-populating them now. We will deliver an update in 1 hour. May 26, 09:40:02 GMT+0 - Completed - The site is now available. Thank you for your patience. Type: Maintenance

Duration: 13 hours and 40 minutes

Affected Components:

<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>09:14:00</var> GMT+0</small><br><strong>Identified</strong> - We are conducting an unplanned switchover to a new hosting provider due to technical problems. The OptiDesk website is currently unavailable. We apologize for the inconvenience..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>09:15:00</var> GMT+0</small><br><strong>Identified</strong> - Starting maintenance..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>09:20:09</var> GMT+0</small><br><strong>Identified</strong> - We are still working on restoring service to the website. We will deliver an update in 15-30 minutes..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>09:32:19</var> GMT+0</small><br><strong>Identified</strong> - We are still working on restoring service due to several CDN failures. We are re-populating them now. We will deliver an update in 1 hour..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>09:40:02</var> GMT+0</small><br><strong>Completed</strong> - The site is now available. Thank you for your patience..</p> ]]> Tue, 26 May 2026 09:14:00 +0000 https://optidesk.instatus.com/maintenance/cmpmebp820bj5nrmmi2ge94ax https://optidesk.instatus.com/maintenance/cmpmebp820bj5nrmmi2ge94ax Issues with Runtime Type: Incident Duration: 2 hours Affected Components: OptiDesk Servers May 13, 04:40:00 GMT+0 - Investigating - We are currently investigating a full service outage. May 13, 06:39:38 GMT+0 - Resolved - We have mitigated and resolved the issue. May 13, 06:54:23 GMT+0 - Postmortem - Summary On the 13th of May, 2026, OptiDesk experienced its first significant service outage. A deployment intended to ship reliability improvements failed, and a follow-up corrective deployment silently failed without raising an error. OptiDesk was unavailable for approximately 1 hour and 53 minutes before the incident was resolved. Impact OptiDesk was unavailable to all guilds using the service from approximately 2:45PM until 4:38PM AEST. Total downtime: \~1 hour, 53 minutes Time to detect: \~1 hour, 37 minutes Resolution from detection: \~11 minutes Incident Details A bug in the reliability changes that were deployed prevented OptiDesk from recovering after the deployment had failed. The corrective fix that followed also failed to apply, but a successful deployment was reported to GitHub, meaning that staff had no signal that the issue was still ongoing. The outage was not detected by internal monitoring, but rather by a beta tester approximately 1 hour and 37 minutes after services went down, wherein no member of the team was notified. Once alerted, staff manually rebooted and reconfigured the deployment service and restored operation within 11 minutes. Conclusion We're sorry for the disruption to OptiDesk. We are relatively young, and incidents like this are part of building reliable infrastructure - but the duration, especially the time it took for us to notice, is not the standard we hold ourselves to. We will be pushing improvements to ensure that further deployments can rollback successfully when health checks fail, and that our downtime systems can automatically detect these types of disruptions and incidents. \- Liam Type: Incident

Duration: 2 hours

Affected Components:

<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>04:40:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating a full service outage..</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>06:39:38</var> GMT+0</small><br><strong>Resolved</strong> - We have mitigated and resolved the issue..</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>06:54:23</var> GMT+0</small><br><strong>Postmortem</strong> - Summary On the 13th of May, 2026, OptiDesk experienced its first significant service outage. A deployment intended to ship reliability improvements failed, and a follow-up corrective deployment silently failed without raising an error. OptiDesk was unavailable for approximately 1 hour and 53 minutes before the incident was resolved. Impact OptiDesk was unavailable to all guilds using the service from approximately 2:45PM until 4:38PM AEST. Total downtime: \~1 hour, 53 minutes Time to detect: \~1 hour, 37 minutes Resolution from detection: \~11 minutes Incident Details A bug in the reliability changes that were deployed prevented OptiDesk from recovering after the deployment had failed. The corrective fix that followed also failed to apply, but a successful deployment was reported to GitHub, meaning that staff had no signal that the issue was still ongoing. The outage was not detected by internal monitoring, but rather by a beta tester approximately 1 hour and 37 minutes after services went down, wherein no member of the team was notified. Once alerted, staff manually rebooted and reconfigured the deployment service and restored operation within 11 minutes. Conclusion We're sorry for the disruption to OptiDesk. We are relatively young, and incidents like this are part of building reliable infrastructure - but the duration, especially the time it took for us to notice, is not the standard we hold ourselves to. We will be pushing improvements to ensure that further deployments can rollback successfully when health checks fail, and that our downtime systems can automatically detect these types of disruptions and incidents. \- Liam.</p> ]]> Wed, 13 May 2026 04:40:00 +0000 https://optidesk.instatus.com/incident/cmp3omm2x02skqjuv2ssc8kjh https://optidesk.instatus.com/incident/cmp3omm2x02skqjuv2ssc8kjh Scheduled Switchover Type: Maintenance Duration: 16 minutes Affected Components: OptiDesk Servers May 10, 04:00:00 GMT+0 - Identified - We're conducting a switchover from our backup cloud servers onto our permanent on-premises server. We expect the switchover to take up to a minute, however it could last up to 10 minutes if problems arise. We thank you for your patience and support. May 10, 04:00:01 GMT+0 - Identified - Maintenance is now in progress May 10, 04:06:58 GMT+0 - Identified - Complications have arised while undertaking the switchover. We are temporarily reinstating the application to it's previous servers while we investigate. May 10, 04:15:05 GMT+0 - Identified - We are now reattempting the switchover. May 10, 04:15:59 GMT+0 - Completed - Switchover has been completed successfully. Thank you for your patience. Type: Maintenance

Duration: 16 minutes

Affected Components:

<p><small>May <var data-var='date'> 10</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Identified</strong> - We're conducting a switchover from our backup cloud servers onto our permanent on-premises server. We expect the switchover to take up to a minute, however it could last up to 10 minutes if problems arise. We thank you for your patience and support..</p> <p><small>May <var data-var='date'> 10</var>, <var data-var='time'>04:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 10</var>, <var data-var='time'>04:06:58</var> GMT+0</small><br><strong>Identified</strong> - Complications have arised while undertaking the switchover. We are temporarily reinstating the application to it's previous servers while we investigate..</p> <p><small>May <var data-var='date'> 10</var>, <var data-var='time'>04:15:05</var> GMT+0</small><br><strong>Identified</strong> - We are now reattempting the switchover..</p> <p><small>May <var data-var='date'> 10</var>, <var data-var='time'>04:15:59</var> GMT+0</small><br><strong>Completed</strong> - Switchover has been completed successfully. Thank you for your patience..</p> ]]> Sun, 10 May 2026 04:00:00 +0000 https://optidesk.instatus.com/maintenance/cmowr2i2r01bca4f8xk8rpiph https://optidesk.instatus.com/maintenance/cmowr2i2r01bca4f8xk8rpiph Issues with Licensing Type: Incident Duration: 11 minutes Affected Components: OptiDesk Servers May 7, 06:26:00 GMT+0 - Investigating - We are currently investigating potential disruptions to the Licensing backend. You may experience slower load times. May 7, 06:28:00 GMT+0 - Identified - We're restarting servers now to deploy a fix. May 7, 06:37:00 GMT+0 - Resolved - The issue has been resolved, and all OptiDesk infrastructure is working as intended. May 7, 06:30:00 GMT+0 - Monitoring - The fix has been deployed and we are now evaluating impact. Type: Incident

Duration: 11 minutes

Affected Components:

<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>06:26:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating potential disruptions to the Licensing backend. You may experience slower load times..</p> <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>06:28:00</var> GMT+0</small><br><strong>Identified</strong> - We're restarting servers now to deploy a fix..</p> <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>06:37:00</var> GMT+0</small><br><strong>Resolved</strong> - The issue has been resolved, and all OptiDesk infrastructure is working as intended..</p> <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>06:30:00</var> GMT+0</small><br><strong>Monitoring</strong> - The fix has been deployed and we are now evaluating impact..</p> ]]> Thu, 7 May 2026 06:26:00 +0000 https://optidesk.instatus.com/incident/cmowfcbms03vxsn35584np7il https://optidesk.instatus.com/incident/cmowfcbms03vxsn35584np7il