Central Desktop Status - Incident history https://central-desktop.instatus.com Central Desktop Fri, 9 May 2025 13:15:00 +0000 Comments are not populating. Type: Incident Duration: 5 hours and 17 minutes Affected Components: Website May 9, 18:31:59 GMT+0 - Resolved - This incident has been resolved. May 9, 13:15:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 5 hours and 17 minutes

Affected Components:

<p><small>May <var data-var='date'> 9</var>, <var data-var='time'>18:31:59</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 9</var>, <var data-var='time'>13:15:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Fri, 9 May 2025 13:15:00 +0000 https://central-desktop.instatus.com/incident/cmagv1fsf001twsyfvdu8xuem https://central-desktop.instatus.com/incident/cmagv1fsf001twsyfvdu8xuem Some Central Desktop Workspaces are not loading Files and Discussions. Type: Incident Duration: 34 minutes Affected Components: Website May 14, 14:04:07 GMT+0 - Resolved - This incident has been resolved. May 14, 13:30:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 34 minutes

Affected Components:

<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>14:04:07</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Tue, 14 May 2024 13:30:00 +0000 https://central-desktop.instatus.com/incident/clw6ghqcz17282bbn4ao83bpe8 https://central-desktop.instatus.com/incident/clw6ghqcz17282bbn4ao83bpe8 Some Central Desktop Workspaces are not loading Files and Discussions. Type: Incident Duration: 5 hours and 57 minutes Affected Components: Website May 13, 23:12:15 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result to ensure that all pages are loading. May 14, 00:12:15 GMT+0 - Resolved - This incident is resolved, full system functionality is restored May 13, 19:31:09 GMT+0 - Investigating - This may be affecting other items as well. We are researching the issue. May 13, 18:15:00 GMT+0 - Investigating - We are currently investigating this issue. Type: Incident

Duration: 5 hours and 57 minutes

Affected Components:

<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>23:12:15</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result to ensure that all pages are loading. .</p> <p><small>May <var data-var='date'> 14</var>, <var data-var='time'>00:12:15</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved, full system functionality is restored.</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>19:31:09</var> GMT+0</small><br><strong>Investigating</strong> - This may be affecting other items as well. We are researching the issue..</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>18:15:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this issue..</p> ]]> Mon, 13 May 2024 18:15:00 +0000 https://central-desktop.instatus.com/incident/clw5c5wb061586bin1uqdohiw1 https://central-desktop.instatus.com/incident/clw5c5wb061586bin1uqdohiw1 We are investigating Issues Receiving Proof Notifications Type: Incident Duration: 4 hours and 16 minutes Affected Components: Proofing May 13, 21:45:35 GMT+0 - Resolved - This proof notification incident has been resolved. May 13, 17:30:00 GMT+0 - Investigating - Some users are unable to access proofs and are not receiving email notifications when proofs are created. We are working to identify and resolve the issue. May 13, 19:33:48 GMT+0 - Monitoring - Adobe had confirmed that there were proof issues earlier today causing proof notifications to not be sent. The corrected the issue, but there's still a backlog needing to be processed. Type: Incident

Duration: 4 hours and 16 minutes

Affected Components:

<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>21:45:35</var> GMT+0</small><br><strong>Resolved</strong> - This proof notification incident has been resolved..</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Investigating</strong> - Some users are unable to access proofs and are not receiving email notifications when proofs are created. We are working to identify and resolve the issue..</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>19:33:48</var> GMT+0</small><br><strong>Monitoring</strong> - Adobe had confirmed that there were proof issues earlier today causing proof notifications to not be sent. The corrected the issue, but there's still a backlog needing to be processed..</p> ]]> Mon, 13 May 2024 17:30:00 +0000 https://central-desktop.instatus.com/incident/clw5b5o9f28109bin1i0harzke https://central-desktop.instatus.com/incident/clw5b5o9f28109bin1i0harzke Cannot re-order Tasks in Task List. Type: Incident Duration: 25 days, 21 hours and 47 minutes Affected Components: Website Mar 5, 18:34:14 GMT+0 - Resolved - This incident has been resolved. Feb 8, 20:47:03 GMT+0 - Investigating - Users are receiving an error when trying to re-order Tasks in a Task List. We are researching. Type: Incident

Duration: 25 days, 21 hours and 47 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>18:34:14</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>20:47:03</var> GMT+0</small><br><strong>Investigating</strong> - Users are receiving an error when trying to re-order Tasks in a Task List. We are researching..</p> ]]> Thu, 8 Feb 2024 20:47:03 +0000 https://central-desktop.instatus.com/incident/clsdow6rj368747bfn9i9y77njk https://central-desktop.instatus.com/incident/clsdow6rj368747bfn9i9y77njk Impairment with Some Project Management Features Type: Incident Duration: 6 hours and 58 minutes Affected Components: Website Jan 29, 13:32:00 GMT+0 - Investigating - Affected features: Creating New Workspaces Milestones Tasks Jan 29, 20:30:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 6 hours and 58 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>13:32:00</var> GMT+0</small><br><strong>Investigating</strong> - Affected features: Creating New Workspaces Milestones Tasks.</p> <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>20:30:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 29 Jan 2024 13:32:00 +0000 https://central-desktop.instatus.com/incident/clrz5h2g652203bkofifq7f0xm https://central-desktop.instatus.com/incident/clrz5h2g652203bkofifq7f0xm Scheduled Maintenance Type: Maintenance Duration: 4 hours and 23 minutes Affected Components: Website, Proofing Jan 27, 15:00:00 GMT+0 - Identified - We are performing scheduled maintenance on Saturday, January 27th 2024 from 7:00 AM to 11:00 AM PST. While maintenance is performed, iMeet Central services will be unavailable. Full functionality will be restored once the maintenance window has ended. Please notify your users of the scheduled outage. This maintenance is necessary to ensure that our databases and proofing systems are up-to-date and running smoothly. We apologize for any inconvenience this downtime may cause and appreciate your patience and understanding. Jan 27, 19:23:12 GMT+0 - Completed - SCHEDULED MAINTENANCE is now complete. The full system is restored. If you are still unable to load your iMeet Central page, please clear your browser cache to reconnect Jan 27, 15:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 4 hours and 23 minutes

Affected Components: ,

<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are performing scheduled maintenance on Saturday, January 27th 2024 from 7:00 AM to 11:00 AM PST. While maintenance is performed, iMeet Central services will be unavailable. Full functionality will be restored once the maintenance window has ended. Please notify your users of the scheduled outage. This maintenance is necessary to ensure that our databases and proofing systems are up-to-date and running smoothly. We apologize for any inconvenience this downtime may cause and appreciate your patience and understanding..</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>19:23:12</var> GMT+0</small><br><strong>Completed</strong> - SCHEDULED MAINTENANCE is now complete. The full system is restored. If you are still unable to load your iMeet Central page, please clear your browser cache to reconnect .</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>15:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Sat, 27 Jan 2024 15:00:00 +0000 https://central-desktop.instatus.com/maintenance/clrv54wu137780bfogfoxq0rtv https://central-desktop.instatus.com/maintenance/clrv54wu137780bfogfoxq0rtv Comments and Reports are not populating Type: Incident Duration: 30 minutes Affected Components: Website Jan 18, 14:05:35 GMT+0 - Investigating - Comments aren't loading and reports are generating blank. We are currently investigating this incident. Jan 18, 14:35:24 GMT+0 - Resolved - This incident has been resolved and services have been restored. Type: Incident

Duration: 30 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>14:05:35</var> GMT+0</small><br><strong>Investigating</strong> - Comments aren't loading and reports are generating blank. We are currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>14:35:24</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved and services have been restored..</p> ]]> Thu, 18 Jan 2024 14:05:35 +0000 https://central-desktop.instatus.com/incident/clrjab0a417263ceoc8dsolfvq https://central-desktop.instatus.com/incident/clrjab0a417263ceoc8dsolfvq Scheduled Maintenance Type: Maintenance Duration: 4 hours Affected Components: Website Jan 13, 15:00:28 GMT+0 - Identified - On Saturday, January 13th 2024 from 7:00 AM to 11:00 AM PST. While maintenance is performed iMeet Central services will be unavailable. Full functionality will be restored once the maintenance window has ended. This maintenance is necessary to ensure that our systems are up-to-date and running smoothly. We apologize for any inconvenience this downtime may cause and appreciate your patience and understanding. Subscribe to this status to receive notification when maintenance is completed. If you have any questions or concerns, please do not hesitate to contact us at support@imeetcentral.com Jan 13, 19:23:40 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 4 hours

Affected Components:

<p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>15:00:28</var> GMT+0</small><br><strong>Identified</strong> - On Saturday, January 13th 2024 from 7:00 AM to 11:00 AM PST. While maintenance is performed iMeet Central services will be unavailable. Full functionality will be restored once the maintenance window has ended. This maintenance is necessary to ensure that our systems are up-to-date and running smoothly. We apologize for any inconvenience this downtime may cause and appreciate your patience and understanding. Subscribe to this status to receive notification when maintenance is completed. If you have any questions or concerns, please do not hesitate to contact us at support@imeetcentral.com.</p> <p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>19:23:40</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Sat, 13 Jan 2024 15:00:28 +0000 https://central-desktop.instatus.com/maintenance/clrc75mgo1801b1n4r2enpqxh https://central-desktop.instatus.com/maintenance/clrc75mgo1801b1n4r2enpqxh System Login Issue Type: Incident Affected Components: Website Jan 10, 01:45:00 GMT+0 - Resolved - Access has been restored for all affected customers. Closing the incident. Type: Incident

Affected Components:

<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>01:45:00</var> GMT+0</small><br><strong>Resolved</strong> - Access has been restored for all affected customers. Closing the incident..</p> ]]> Wed, 10 Jan 2024 01:45:00 +0000 https://central-desktop.instatus.com/incident/clr73pohk1680ciob4id12kn1 https://central-desktop.instatus.com/incident/clr73pohk1680ciob4id12kn1 Central Desktop System Outage Type: Incident Duration: 1 hour and 17 minutes Affected Components: Website Nov 28, 23:16:06 GMT+0 - Resolved - Service has been restored. Nov 28, 21:59:02 GMT+0 - Investigating - Users are experiencing issues accessing the site. We are currently investigating this incident. Type: Incident

Duration: 1 hour and 17 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>23:16:06</var> GMT+0</small><br><strong>Resolved</strong> - Service has been restored..</p> <p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>21:59:02</var> GMT+0</small><br><strong>Investigating</strong> - Users are experiencing issues accessing the site. We are currently investigating this incident..</p> ]]> Tue, 28 Nov 2023 21:59:02 +0000 https://central-desktop.instatus.com/incident/clpivrero21486bbn5ddusqics https://central-desktop.instatus.com/incident/clpivrero21486bbn5ddusqics Central Desktop System Outage Type: Incident Duration: 19 minutes Affected Components: Website Jun 29, 20:42:46 GMT+0 - Investigating - We are currently investigating this incident. Jun 29, 21:01:22 GMT+0 - Resolved - System has been restored. Processing may be a little slow initially as the system re-initializes all the systems. Type: Incident

Duration: 19 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>20:42:46</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>21:01:22</var> GMT+0</small><br><strong>Resolved</strong> - System has been restored. Processing may be a little slow initially as the system re-initializes all the systems..</p> ]]> Thu, 29 Jun 2023 20:42:46 +0000 https://central-desktop.instatus.com/incident/cljhm3v4c297043azoh0n3074mx https://central-desktop.instatus.com/incident/cljhm3v4c297043azoh0n3074mx Users are not receiving email notifications. Type: Incident Duration: 14 hours Affected Components: Website May 24, 01:00:00 GMT+0 - Investigating - We are currently investigating this incident. May 24, 15:00:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 14 hours

Affected Components:

<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 24 May 2023 01:00:00 +0000 https://central-desktop.instatus.com/incident/cli1rfirv717089b3n31hxbzyft https://central-desktop.instatus.com/incident/cli1rfirv717089b3n31hxbzyft Audit Logs are not loading. Type: Incident Duration: 3 hours and 5 minutes Affected Components: Website May 18, 16:00:00 GMT+0 - Investigating - When opening an Audit Log, it tries to load then returns the following error: Service is Unavailable, please try again later. We are currently researching. May 18, 18:45:13 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 18, 19:04:33 GMT+0 - Resolved - Our engineers have identified and corrected the issue. Service has been restored. Type: Incident

Duration: 3 hours and 5 minutes

Affected Components:

<p><small>May <var data-var='date'> 18</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Investigating</strong> - When opening an Audit Log, it tries to load then returns the following error: Service is Unavailable, please try again later. We are currently researching..</p> <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>18:45:13</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>19:04:33</var> GMT+0</small><br><strong>Resolved</strong> - Our engineers have identified and corrected the issue. Service has been restored..</p> ]]> Thu, 18 May 2023 16:00:00 +0000 https://central-desktop.instatus.com/incident/clhtfi38m14090364omo2q1w9x3 https://central-desktop.instatus.com/incident/clhtfi38m14090364omo2q1w9x3 Central Desktop System Outage Type: Incident Duration: 6 hours and 30 minutes Affected Components: Website May 17, 06:00:00 GMT+0 - Investigating - Users are receiving the following message: The site is not secure as it uses an Unsupported Protocol. We are currently researching. May 17, 12:30:00 GMT+0 - Resolved - We have identified the issue and confirmed that the system performance has been restored. Type: Incident

Duration: 6 hours and 30 minutes

Affected Components:

<p><small>May <var data-var='date'> 17</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Investigating</strong> - Users are receiving the following message: The site is not secure as it uses an Unsupported Protocol. We are currently researching..</p> <p><small>May <var data-var='date'> 17</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Resolved</strong> - We have identified the issue and confirmed that the system performance has been restored..</p> ]]> Wed, 17 May 2023 06:00:00 +0000 https://central-desktop.instatus.com/incident/clhs09qga63093oxn2pazreaqf https://central-desktop.instatus.com/incident/clhs09qga63093oxn2pazreaqf Certificate Error for Proofs Type: Incident Affected Components: Proofing May 3, 14:00:00 GMT+0 - Resolved - A certificate error is causing some proofs to not be accessible, or not upload. We are working with Adobe to resolve the certificate issue. If you are unable to access or create proofs, please email support at support@imeetcentral.com. Please include the link of the proof you are trying to access/upload. Type: Incident

Affected Components:

<p><small>May <var data-var='date'> 3</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Resolved</strong> - A certificate error is causing some proofs to not be accessible, or not upload. We are working with Adobe to resolve the certificate issue. If you are unable to access or create proofs, please email support at support@imeetcentral.com. Please include the link of the proof you are trying to access/upload..</p> ]]> Wed, 3 May 2023 14:00:00 +0000 https://central-desktop.instatus.com/incident/clh7y8wzj3603b2oiywmii6tx https://central-desktop.instatus.com/incident/clh7y8wzj3603b2oiywmii6tx "System Error" when logging in Type: Incident Duration: 6 days, 22 hours and 14 minutes Affected Components: Website Mar 23, 17:13:46 GMT+0 - Resolved - We have corrected the login page and confirmed that it is working properly again. Mar 21, 21:06:16 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. If you still experience any issues logging in via https://app.imeetcentral.com/login, please emails support at support@imeetcentral.com. Mar 16, 19:00:00 GMT+0 - Identified - **Description**: When attempting to log in via app.imeetcentral.com/login, users are receiving the following message: "This is a system error". **Workaround**: Please use your company's direct link to log in. This is usually (companyname).imeetcentral.com/login. In addition - if you have a link to an existing file or location on your iMeet Central site, you can use that as well. **Note**: If you don't know your company's direct link, please email support at support@imeetcentral.com **Status**: We are currently researching the impairment. For the moment, please use the workaround listed above. Type: Incident

Duration: 6 days, 22 hours and 14 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>17:13:46</var> GMT+0</small><br><strong>Resolved</strong> - We have corrected the login page and confirmed that it is working properly again..</p> <p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>21:06:16</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. If you still experience any issues logging in via https://app.imeetcentral.com/login, please emails support at support@imeetcentral.com..</p> <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - **Description**: When attempting to log in via app.imeetcentral.com/login, users are receiving the following message: "This is a system error". **Workaround**: Please use your company's direct link to log in. This is usually (companyname).imeetcentral.com/login. In addition - if you have a link to an existing file or location on your iMeet Central site, you can use that as well. **Note**: If you don't know your company's direct link, please email support at support@imeetcentral.com **Status**: We are currently researching the impairment. For the moment, please use the workaround listed above..</p> ]]> Thu, 16 Mar 2023 19:00:00 +0000 https://central-desktop.instatus.com/incident/clfcts3g7153468h2odv5k6t0dv https://central-desktop.instatus.com/incident/clfcts3g7153468h2odv5k6t0dv