tag:status.t1cloud.com,2005:/historyTechnologyOne Status - Incident History2024-03-29T01:47:01+10:00TechnologyOnetag:status.t1cloud.com,2005:Incident/203689502024-03-27T15:38:43+10:002024-03-27T15:38:43+10:00Spatial Cloud - ANZ Region - 2022B / 2023A / 2023B Releases<p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>15:38</var> AEST</small><br><strong>Resolved</strong> - We are pleased to inform you that the issue which impacted Spatial services has been resolved. The cause of the incident was traced back to an unresponsive IntraMaps service that ceased to respond to requests. The identified unresponsive services have been addressed and successfully brought back online.<br /><br />We apologise for the inconvenience this has caused and shall continue our efforts in ensuring preventive measures are in place to avoid recurrence. Thank you</p><p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>14:13</var> AEST</small><br><strong>Monitoring</strong> - Our team of engineers have identified the root cause and have implemented a fix to restore the stability of the spatial services. An update on the root cause will be shared prior to resolving this incident. Thank you.</p><p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>13:21</var> AEST</small><br><strong>Update</strong> - Our team are currently still investigating this issue and we shall provide you with an update in the next 60 minutes or as soon as we have isolated the root cause. We apologise inconvenience caused to you.</p><p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>11:46</var> AEST</small><br><strong>Investigating</strong> - We have identified an issue with some customer environments experiencing connection issues and performance degradation within CiAnywhere / ANZ Region / 2022B, 2023A & 2023B Releases.<br /><br /><br />Our engineers are currently investigating the root cause. Further updates will be provided. <br /><br />We apologise for the inconvenience caused.</p>tag:status.t1cloud.com,2005:Incident/202876462024-03-18T17:09:39+10:002024-03-18T17:09:39+10:00Spatial Cloud - ANZ Region - 2022B / 2023B Release<p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>17:09</var> AEST</small><br><strong>Resolved</strong> - We have been monitoring the stability of the implemented fix and are now in the process of resolving this incident. The cause of the incident was traced back to an unresponsive IntraMaps service that ceased to respond to requests. The identified unresponsive services have been addressed and successfully brought back online.<br /><br />Our team of engineers is continuing their investigation to identify and implement preventive measures. We sincerely apologize for any inconvenience this may have caused.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>15:30</var> AEST</small><br><strong>Update</strong> - A fix has been rolled out and our team of engineers are currently monitoring the stability of the services.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>14:50</var> AEST</small><br><strong>Monitoring</strong> - Our team of engineers have applied the fix identified and are currently monitoring the services for stability. Thank you and we apologies for any inconvenience this has caused.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>13:25</var> AEST</small><br><strong>Identified</strong> - Our engineers have identified the cause of the incident and are currently working towards addressing the issue. This is to ensure spatial services are restored to standard operation levels.<br /><br />We aim to provide the next update within the next 60 minutes.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>13:11</var> AEST</small><br><strong>Investigating</strong> - We have identified an issue with some customer environments experiencing connection issues and performance degradation within CiAnywhere / ANZ Region / 2022B & 2023B Release.<br /><br />Our engineers are currently investigating the root cause. Further updates will be provided. <br /><br />We apologise for the inconvenience caused.</p>tag:status.t1cloud.com,2005:Incident/202285852024-03-13T11:39:52+10:002024-03-13T15:06:32+10:00Spatial Cloud - ANZ Region - 2022B / 2023B Release<p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>11:39</var> AEST</small><br><strong>Resolved</strong> - Incident Resolution and Root Cause Analysis<br /><br />We are pleased to inform you that the recent service incident has been fully resolved.<br /><br />Root Cause:<br />Upon initial analysis, it was determined that the incident originated from an unexpected anomaly within our primary storage volume. This anomaly disrupted standard operations and access to crucial database services. Although the secondary volume remained operational and helped prevent a complete service outage, the issue with the primary volume required immediate intervention to ensure the continuity of our services.<br /><br />Service Restoration Actions:<br />To mitigate the impact and fully restore services, our technical team promptly initiated a failover process. This process involved transitioning the operational nodes from the primary to the secondary system and then back again, to ensure thorough resolution. This failover was meticulously executed twice—from System A to System B and back, and then from System B to System A and back—to guarantee a comprehensive restoration of services. Despite a brief service interruption during this process, our team made every effort to minimize the downtime and quickly return to normal operations.<br /><br />Further, we have proactively engaged with our upstream providers to investigate the cause of the anomaly within our storage services. This inquiry aims to uncover the root cause of the disruption and to identify and implement the necessary preventive measures to prevent future occurrences.<br /><br />We are committed to continuous improvement and ensuring the reliability of our services. We appreciate your understanding and apologize for any inconvenience this may have caused.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>08:36</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are currently monitoring the services for stability. Details of the root cause will be shared prior to resolving this incident.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>08:14</var> AEST</small><br><strong>Identified</strong> - Our engineers have identified the cause of the incident and are currently working towards addressing the issue. This is to ensure spatial services are restored to standard operation levels.<br />We shall aim to provide the next update within the next 60 minutes.</p><p><small>Mar <var data-var='date'>13</var>, <var data-var='time'>07:23</var> AEST</small><br><strong>Investigating</strong> - We have identified an issue with some customer environments experiencing connection issues and performance degradation within CiAnywhere / ANZ Region / 2022B & 2023B Release.<br /><br />Our engineers are currently investigating the root cause. Further updates will be provided. <br /><br />We apologise for the inconvenience caused.</p>tag:status.t1cloud.com,2005:Incident/201815882024-03-07T15:06:04+10:002024-03-07T15:06:04+10:00Performance and Connection Issues - CiAnywhere / ANZ Region / 2022B / 2023B Release<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>15:06</var> AEST</small><br><strong>Resolved</strong> - This incident is now resolved. <br /><br />We thank you for your patience and understanding while we worked towards restoring the services.</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>14:31</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are currently monitoring the services for stability. <br /><br />An update on the preliminary root cause will be shared prior to resolving this incident. <br /><br />Thank you</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>13:56</var> AEST</small><br><strong>Identified</strong> - Our team of engineers have identified the root cause and are in the process of applying a fix that would restore the services back to standard operating levels. <br /><br />We aim to provide you with an update in the next 30 minutes. <br /><br />Thank you.</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>13:29</var> AEST</small><br><strong>Investigating</strong> - We have identified an issue with some customer environments experiencing connection issues and performance degradation within CiAnywhere / ANZ Region / 2022B / 2023B Release.<br /><br />Our engineers are currently investigating the root cause. Further updates will be provided.<br /><br />Thank you.</p>tag:status.t1cloud.com,2005:Incident/201520662024-03-04T11:31:33+10:002024-03-04T11:31:33+10:00Performance Degradation - ANZ Region / 2023A Release<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>11:31</var> AEST</small><br><strong>Resolved</strong> - Great news! We are confident that the fix in place has resolved this incident. The root cause has been identified as a service disruption linked to a configuration limit at our upstream provider. Our team of engineers has diligently worked in partnership with our upstream provider to ensure that the issue has been addressed and preventive measures are in place to prevent similar recurrences.<br /><br />We apologize for any inconvenience this caused and thank you for your cooperation while we resolved this incident</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>09:15</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are currently monitoring the services for stability. <br />An update on the preliminary root cause will be shared prior to resolving this incident. Thank you</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>08:22</var> AEST</small><br><strong>Identified</strong> - Our engineers have identified the issue and are in the process of applying a fix. <br /><br />The next update will be provided once we have applied and tested the fix. <br /><br />Thank you.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>08:07</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing performance degradation within ANZ.<br />Our engineers are currently investigating the root cause. <br /><br />We will provide another update within the next 60 minutes. <br /><br />Thank you.</p>tag:status.t1cloud.com,2005:Incident/201196162024-03-01T13:44:14+10:002024-03-04T13:10:37+10:00Spatial Cloud - ANZ Region - 2022B and 2023B Release<p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>13:44</var> AEST</small><br><strong>Resolved</strong> - This incident is now resolved. <br />We thank you for your patience and understanding while we worked towards restoring the services.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>12:53</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are currently monitoring the services for stability. <br />Our engineers have identified the root cause to an unresponsive server which stopped responding to requests. The unresponsive server was identified and brought back online.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>12:24</var> AEST</small><br><strong>Identified</strong> - Our team of engineers have identified the root cause and are in the process of applying a fix that would restore the services back to standard operating levels. <br /><br />We shall aim to provide you with an update in the next 30 minutes. Thank you.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>12:14</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments who are experiencing unavailable service within ANZ Spatial Cloud.<br /><br />Our engineers are currently investigating the root cause. Further updates will be provided.</p>tag:status.t1cloud.com,2005:Incident/199874352024-02-15T17:15:53+10:002024-02-15T17:15:53+10:00Performance and Connection Issues - CiAnywhere / ANZ Region / 2023B Release<p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>17:15</var> AEST</small><br><strong>Resolved</strong> - We're pleased to announce that the recent service disruption has been resolved. Our team has successfully applied a fix and is actively monitoring the service to ensure stability is maintained.<br /><br />We sincerely apologise for any inconvenience this disruption may have caused. Your patience and understanding during this time have been greatly appreciated.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>11:46</var> AEST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>09:24</var> AEST</small><br><strong>Monitoring</strong> - Our engineers have identified the issue and we are pleased to inform you that the necessary fix has been successfully implemented. <br /><br />We are now in the monitoring phase to ensure stability. <br /><br />We apologise for any inconvenience caused and appreciate your patience during this process. <br /><br />The next update will be provided prior to resolving the incident, along with a root cause analysis. <br /><br />Thank you.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>09:03</var> AEST</small><br><strong>Identified</strong> - Our engineers have identified the issue and are in the process of applying a fix. <br /><br />The next update will be provided once we have applied and tested the fix. <br /><br />Thank you for your ongoing patience.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>08:37</var> AEST</small><br><strong>Investigating</strong> - We have identified an issue with some customer environments experiencing connection issues and performance degradation within CiAnywhere / ANZ Region / 2023B <br /><br />Our engineers are currently investigating the root cause. <br /><br />We will provide another update within the next 60 minutes. <br /><br />Thank you.</p>tag:status.t1cloud.com,2005:Incident/199811672024-02-15T08:07:26+10:002024-02-15T08:07:26+10:00Performance Degradation - ANZ Region (excl Federal Government)<p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>08:07</var> AEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>18:14</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>16:04</var> AEST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>16:04</var> AEST</small><br><strong>Investigating</strong> - We have identified an intermittent issue with CiA reporting time-out pop up on screen, for a select set of customers in the ANZ region.</p>tag:status.t1cloud.com,2005:Incident/199633222024-02-13T13:26:58+10:002024-02-13T13:26:58+10:00Performance Degradation - ANZ Region / 2023A and 2023B Release<p><small>Feb <var data-var='date'>13</var>, <var data-var='time'>13:26</var> AEST</small><br><strong>Resolved</strong> - Good News! We're pleased to inform you that the recent incident has been successfully resolved.<br /><br />Root Cause: Our preliminary analysis indicates that the issue was due to unhealthy servers.<br /><br />Action Taken: To address this, we have replaced the problematic servers, ensuring that all services are now back to standard operations.<br /><br />We appreciate your patience during this time and apologise for any inconvenience caused.</p><p><small>Feb <var data-var='date'>13</var>, <var data-var='time'>10:39</var> AEST</small><br><strong>Monitoring</strong> - Our engineers have identified the issue and we are pleased to inform you that the necessary fix has been successfully implemented. <br /><br />We are now in the monitoring phase to ensure stability. <br /><br />We apologise for any inconvenience caused and appreciate your patience during this process. <br /><br />The next update will be provided prior to resolving the incident, along with a root cause analysis. Thank you.</p><p><small>Feb <var data-var='date'>13</var>, <var data-var='time'>09:34</var> AEST</small><br><strong>Identified</strong> - We have identified a selection of customer environments experiencing performance degradation within ANZ.<br />Our engineers are currently investigating the root cause. <br /><br />We will provide another update within the next 60 minutes. Thank you</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>14:15</var> AEST</small><br><strong>Monitoring</strong> - We are pleased to inform you that the necessary fix has been successfully implemented. We are now in the monitoring phase to ensure stability. <br /><br />We apologise for any inconvenience caused and appreciate your patience during this process. <br /><br />The next update will be provided prior to resolving the incident, along with a root cause analysis. Thank you.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>12:51</var> AEST</small><br><strong>Identified</strong> - Our engineers have identified the issue and are in the process of applying a fix. <br /><br />The next update will be provided once we have applied and tested the fix. <br /><br />Thank you for your ongoing patience.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>11:49</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing performance degradation within ANZ.<br />Our engineers are currently investigating the root cause. <br /><br />We will provide another update within the next 60 minutes. Thank you.</p>tag:status.t1cloud.com,2005:Incident/199255942024-02-08T13:47:02+10:002024-02-08T13:47:02+10:00Spatial Cloud - ANZ Region - 2022B / 2023A / 2023B Release<p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>13:47</var> AEST</small><br><strong>Resolved</strong> - Our team is pleased to announce that the overnight processing has been completed successfully, aligning perfectly with our expectations. Our analysis has led to the identification of the preliminary root cause of the issue at hand. <br /><br />We are committed to transparency and thoroughness in our approach; therefore, we will share the detailed findings of our root cause analysis within the next 14 days.<br /><br />We appreciate your patience and understanding as we continue to improve your service experience. Thank you for your continued trust in our services.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>11:09</var> AEST</small><br><strong>Update</strong> - Through monitoring of services following the reruns of the nightly processes, our engineers have identified additional sites who would require their overnight process to be rerun. <br />These sites will have degraded performance while we rerun the services. <br />We apologise for the inconvenience caused and are committed to restoring the services to standard operational levels.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>08:57</var> AEST</small><br><strong>Monitoring</strong> - We are pleased to update that all overnight processing for the impacted customers has been completed successfully. <br />Our team of engineers will continue to monitor the services for stability before resolving the incident.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>08:12</var> AEST</small><br><strong>Identified</strong> - We have identified a selection of customer environments that failed to complete the overnight processing. What this means is the impacted customers will have the overnight processing run now, which would result in a degraded performance when using Spatial Cloud Services. <br />Please note this would not have any impact to other SaaS Services <br /><br />We shall aim to provide you with an update in the next 60 minutes. We apologise for the inconvenience caused.</p>tag:status.t1cloud.com,2005:Incident/198634252024-02-01T16:19:04+10:002024-02-01T16:19:04+10:00CPM Warehouse Import Issues - ALL Region / Fastline 2023B (448) Release<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>16:19</var> AEST</small><br><strong>Resolved</strong> - Following close monitoring of the latest software update, we're pleased to report no recurrence of the issue. We encourage all affected customers to consult the Known Issues page for additional guidance on safeguarding your data integrity.<br /><br />https://customercommunity.technologyonecorp.com/s/article/00628621<br /><br />The TechnologyOne team extends our gratitude for your understanding and cooperation throughout this process.</p><p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>22:11</var> AEST</small><br><strong>Update</strong> - We are pleased to advise that the upgrade process for UK and European regions has been successfully completed. <br /><br />This follows our earlier announcement regarding the successful upgrade of our ANZ customers on Fastline 2023B (448) to Fastline 2023B (457) overnight.<br /><br />Our engineering team continues to closely monitor the software's stability to ensure optimal performance and a smooth experience for all users. We will maintain vigilant oversight and provide any necessary support during this transition period<br /><br />Action Required for 2023B Production Customers who were on Fastline 448 and now 457:<br /><br />We acknowledge that the issue introduced in Fastline 448 may have affected some of your data. We are committed to providing the necessary support to ensure the integrity of your data. Please visit the Known Issue Article for next steps. <br /><br />https://customercommunity.technologyonecorp.com/s/article/00628621<br /><br />If you are unsure what snapshot you are on please see this article:<br /><br />https://customercommunity.technologyonecorp.com/s/article/How-to-Identify-Your<br /><br />We express our gratitude for your patience and apologise for any inconvenience caused.</p><p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>11:13</var> AEST</small><br><strong>Monitoring</strong> - We're pleased to announce that ANZ customers on 2023B Fastline (448) have been successfully upgraded to Fastline 2023B (457) overnight. Upgrades for UK and European customers are currently underway. Our engineering team is diligently monitoring the software's stability and we plan to provide a further update before the close of business today.<br />Thank you for your patience and we sincerely apologies for any inconvenience this may have caused you.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>16:41</var> AEST</small><br><strong>Update</strong> - Our teams have pinpointed the source of the problem. Consequently, we plan to upgrade all impacted Production and Non Production environments from 2023B Fastline (448) to a new snapshot (2023B Fastline (457). This updated snapshot will replicate the configuration of snapshot 448, while eliminating the issue that was previously identified in it. <br /><br />For more information, please refer to the published Known Issue link as below:<br />https://customercommunity.technologyonecorp.com/s/article/00628621</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>14:58</var> AEST</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>13:45</var> AEST</small><br><strong>Identified</strong> - Our teams have detected a problem whereby ETL is storing "System.Object[]" instead of blank or null string values via Warehouse Table Import. <br /><br />For more information, please refer to the published Known Issue link as below:<br />https://customercommunity.technologyonecorp.com/s/article/00628621<br /><br />Our engineers are currently working towards identifying a resolution. We shall aim to provide an update in the next 60 minutes.</p>tag:status.t1cloud.com,2005:Incident/197303702024-01-17T13:32:11+10:002024-01-17T13:32:11+10:00Performance Degradation - ANZ Region / 2023A Release<p><small>Jan <var data-var='date'>17</var>, <var data-var='time'>13:32</var> AEST</small><br><strong>Resolved</strong> - Great news, following thorough monitoring and confirmation from impacted customers, we are now closing this incident.<br /><br />Root Cause:<br />The issue was identified as an unusual surge in resource demand, which deviated from normal usage patterns. This unexpected increase placed excessive load on our shared resources, resulting in performance degradation for some customers.<br /><br />We thank you for your understanding and patience as we worked diligently to identify and resolve this issue. Your cooperation has been invaluable. We appreciate your continued trust in our services.</p><p><small>Jan <var data-var='date'>17</var>, <var data-var='time'>10:49</var> AEST</small><br><strong>Monitoring</strong> - We are pleased to inform you that the necessary fix has been successfully implemented. We are now in the monitoring phase to ensure stability. We apologize for any inconvenience caused and appreciate your patience during this process. <br /><br />Next update will be provided prior to resolving the Incident, along with a root cause analysis. Thank you.</p><p><small>Jan <var data-var='date'>17</var>, <var data-var='time'>09:48</var> AEST</small><br><strong>Identified</strong> - Our engineers have identified the issue and are in the process of applying a fix. <br /><br />The next update will be provided once we have applied and tested the fix. Thank you.</p><p><small>Jan <var data-var='date'>17</var>, <var data-var='time'>08:49</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing performance degradation within ANZ.<br />Our engineers are currently investigating the root cause. <br /><br />We will provide another update within the next 60 minutes. Thank you.</p>tag:status.t1cloud.com,2005:Incident/196723252024-01-11T10:38:43+10:002024-02-19T11:55:40+10:00Performance Degradation - ANZ Region / 2023A Release<p><small>Jan <var data-var='date'>11</var>, <var data-var='time'>10:38</var> AEST</small><br><strong>Resolved</strong> - We're pleased to announce that the recent service disruption has been resolved. Our team has successfully applied a fix and is actively monitoring the service to ensure stability is maintained.<br /><br />Preliminary investigations indicate that a significant increase in traffic was the primary cause of the incident. We're committed to a thorough analysis and will share the root cause analysis review once the investigation is complete.<br /><br />We sincerely apologize for any inconvenience this disruption may have caused. Your patience and understanding during this time have been greatly appreciated.</p><p><small>Jan <var data-var='date'>11</var>, <var data-var='time'>09:26</var> AEST</small><br><strong>Identified</strong> - Hi all,<br />Our engineers have identified the issue and are in the process of applying a fix. <br />The next update will be provided once we have applied and tested the fix. Thank you</p><p><small>Jan <var data-var='date'>11</var>, <var data-var='time'>09:08</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing performance degradation within ANZ <br />Our engineers are currently investigating the root cause. <br /><br />We shall aim to provide you with an update within the next 60 minutes. Thank you</p>tag:status.t1cloud.com,2005:Incident/196423002024-01-09T11:19:46+10:002024-01-09T11:19:46+10:00Performance Degradation - ANZ Spatial Cloud<p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>11:19</var> AEST</small><br><strong>Resolved</strong> - Good News! We're pleased to inform you that the recent incident has been successfully resolved.<br /><br />Root Cause: Our preliminary analysis indicates that the issue was due to an unhealthy server.<br /><br />Action Taken: To address this, we have replaced the problematic server, ensuring that all services are now back to standard operations.<br /><br />We appreciate your patience during this time and apologise for any inconvenience caused.</p><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>16:57</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>16:27</var> AEST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>15:39</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing performance degradation within ANZ Spatial Cloud<br /><br />Our engineers are currently investigating the root cause. Further updates will be provided.</p>tag:status.t1cloud.com,2005:Incident/195176212023-12-24T14:53:01+10:002023-12-24T14:53:01+10:00Login Issues - ANZ Region / 2023A(615) Mainline<p><small>Dec <var data-var='date'>24</var>, <var data-var='time'>14:53</var> AEST</small><br><strong>Resolved</strong> - Good News! We're pleased to inform you that the recent incident has been successfully resolved.<br /><br />Root Cause: Our preliminary analysis indicates that the issue was due to an unhealthy server.<br /><br />Action Taken: To address this, we have replaced the problematic server, ensuring that all services are now back to standard operations.<br /><br />We appreciate your patience during this time and apologize for any inconvenience caused.</p><p><small>Dec <var data-var='date'>24</var>, <var data-var='time'>14:47</var> AEST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Dec <var data-var='date'>24</var>, <var data-var='time'>14:46</var> AEST</small><br><strong>Monitoring</strong> - We detected an issue impacting selected few customers, where impacted customers would not have been able to log into the Production environment. <br /><br />Time of Impact: <br />24/12/2023<br />2:24PM AEDT - 2:34PM AEDT<br /><br />The issue has since been resolved and our team of engineers are monitoring the services.</p>tag:status.t1cloud.com,2005:Incident/193960762023-12-11T16:42:22+10:002023-12-18T14:55:45+10:00Performance Degradation - ANZ Region / 2023A and 2023B<p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>16:42</var> AEST</small><br><strong>Resolved</strong> - We've resolved the recent incident after thorough monitoring.<br /><br />Root Cause:<br />The issue was traced to a few unoptimized queries.<br /><br />Resolution:<br />Our engineers performed essential maintenance tasks, resulting in improved performance.<br /><br />We apologize for any inconvenience and appreciate your patience.<br /><br />Thank you for your support.</p><p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>14:04</var> AEST</small><br><strong>Monitoring</strong> - Apologies for the delay in getting this update out. Our engineers had applied a fix and we have been monitoring the services for stability. <br />From our monitoring, we can see services have normalized. We will continue to monitor this through the day before marking it as Resolved. <br />Thank you.</p><p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>12:12</var> AEST</small><br><strong>Update</strong> - We are continuing to work on getting a resolution as quickly as possible. We shall provide you with an update in the next 60 minutes or sooner. Thank you.</p><p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>10:54</var> AEST</small><br><strong>Identified</strong> - Our engineers have identified the issue and are working on addressing it. <br />Next update will be provided within the next 60 minutes. We appreciate your patience while we work towards restoring services back to its operational standards.</p><p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>10:03</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing performance degradation within CIANYWHERE. Services are still operational however may be slower than normal. We apologies for the inconvenience caused. Our engineers are investigating this issue as a matter of priority, and we shall aim to provide you with an update in the next 60 minutes. <br /><br />Thank you.</p>tag:status.t1cloud.com,2005:Incident/193433162023-12-06T13:53:03+10:002023-12-06T13:53:03+10:00Performance Degradation - ANZ Region - All Releases<p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>13:53</var> AEST</small><br><strong>Resolved</strong> - The issue has been identified and fixed.</p><p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>11:53</var> AEST</small><br><strong>Identified</strong> - We have identified a selection of customer environments experiencing performance degradation across the SaaS platform. Services are still operational however may be slower than normal.<br /><br />Our engineers are currently investigating the root cause.</p>tag:status.t1cloud.com,2005:Incident/192537382023-12-01T11:39:20+10:002023-12-01T11:39:20+10:00Performance Degradation - ANZ Region / 2022B CiAnywhere / Mainline (847) Release<p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>11:39</var> AEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>09:45</var> AEST</small><br><strong>Monitoring</strong> - The fix has been implemented and we are currently monitoring the services.</p><p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>09:26</var> AEST</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>09:22</var> AEST</small><br><strong>Identified</strong> - We have identified a selection of customer environments experiencing performance degradation in CIANYWHERE in the 2022B Mainline (847) Release. Services are still operational however may be slower than normal.<br /><br />Our engineers have identified the root cause and are currently working towards implementing a fix.</p>tag:status.t1cloud.com,2005:Incident/192227042023-11-27T17:13:38+10:002023-11-27T17:13:38+10:00Performance Degradation - AU/NZ Region / 2023B (338)D<p><small>Nov <var data-var='date'>27</var>, <var data-var='time'>17:13</var> AEST</small><br><strong>Resolved</strong> - This incident has been resolved.<br /><br />Thank you.</p><p><small>Nov <var data-var='date'>27</var>, <var data-var='time'>10:21</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are currently monitoring all services to ensure services are operating as expected. Thank you</p><p><small>Nov <var data-var='date'>27</var>, <var data-var='time'>10:18</var> AEST</small><br><strong>Update</strong> - We are continuing to implement the fix</p><p><small>Nov <var data-var='date'>27</var>, <var data-var='time'>10:17</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing performance degradation within CIA 2023B(338)D. Services are still operational however may be slower than normal.<br /><br />Our engineers have identified the root cause and are implementing the necessary fix to restore services.</p>tag:status.t1cloud.com,2005:Incident/191838342023-11-21T15:24:21+10:002023-11-21T15:24:21+10:00Performance Degradation - ANZ / 2022B / Spatial Cloud<p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>15:24</var> AEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>10:23</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>10:17</var> AEST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>08:43</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing intermittent periods of performance degradation within ANZ 2022B - Spatial Cloud. <br /><br />Our engineers are currently investigating the root cause.</p>tag:status.t1cloud.com,2005:Incident/191230772023-11-15T15:46:02+10:002023-11-15T15:46:02+10:00Performance Degradation - ANZ / 2022B / Spatial Cloud<p><small>Nov <var data-var='date'>15</var>, <var data-var='time'>15:46</var> AEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'>15</var>, <var data-var='time'>12:12</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Nov <var data-var='date'>15</var>, <var data-var='time'>11:51</var> AEST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Nov <var data-var='date'>15</var>, <var data-var='time'>10:20</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing performance degradation within ANZ 2022B - Spatial Cloud. Services are still operational however may be slower than normal.<br /><br />Our engineers are currently investigating the root cause.</p>tag:status.t1cloud.com,2005:Incident/191036262023-11-13T16:37:35+10:002023-11-13T16:37:35+10:00Failure HSF:500 internal server error when launching Ci in the Cloud<p><small>Nov <var data-var='date'>13</var>, <var data-var='time'>16:37</var> AEST</small><br><strong>Resolved</strong> - This incident is now resolved. <br /><br />Thank you.</p><p><small>Nov <var data-var='date'>13</var>, <var data-var='time'>16:11</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Nov <var data-var='date'>13</var>, <var data-var='time'>15:54</var> AEST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Nov <var data-var='date'>13</var>, <var data-var='time'>14:16</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing issues connecting to Ci in the Cloud. <br /><br />Our engineers are currently investigating the root cause and further updates will be provided.<br /><br />Thank you.</p>tag:status.t1cloud.com,2005:Incident/189747822023-11-01T12:20:23+10:002023-11-01T12:20:23+10:00Performance Degradation - Ci and CiA in the Cloud / Subset of Customers<p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>12:20</var> AEST</small><br><strong>Resolved</strong> - This incident is now resolved. Thank you.</p><p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>08:30</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Oct <var data-var='date'>31</var>, <var data-var='time'>19:59</var> AEST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Oct <var data-var='date'>31</var>, <var data-var='time'>13:28</var> AEST</small><br><strong>Investigating</strong> - We are currently investigating an issue where there is a decline in performance for a specific group of customers who are attempting to access CI and CiA in the Cloud.<br /><br />Our engineers are currently investigating the root cause and we shall provide an update as soon as we have identified the root cause. <br /><br />Thank you</p>tag:status.t1cloud.com,2005:Incident/189412392023-10-27T14:07:00+10:002023-10-27T14:07:00+10:00Performance Degradation - ANZ / 2022B / Spatial Cloud<p><small>Oct <var data-var='date'>27</var>, <var data-var='time'>14:07</var> AEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'>27</var>, <var data-var='time'>13:35</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Oct <var data-var='date'>27</var>, <var data-var='time'>13:22</var> AEST</small><br><strong>Identified</strong> - We have identified a selection of customer environments experiencing performance degradation within ANZ 2022B - Spatial Cloud. Services are still operational however may be slower than normal.<br /><br />Our engineers are currently investigating the root cause.</p>tag:status.t1cloud.com,2005:Incident/185073462023-09-15T17:18:20+10:002023-09-15T17:18:20+10:00Performance Degradation - ANZ Region - 2022B Spatial Cloud<p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>17:18</var> AEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>17:02</var> AEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are currently monitoring the fix.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>16:23</var> AEST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>14:50</var> AEST</small><br><strong>Investigating</strong> - We have identified a selection of customer environments experiencing performance degradation within Spatial (2022B). <br />Services are still operational however may be slower than normal.<br /><br />Our engineers are currently investigating the root cause.</p>