tag:status.unitq.com,2005:/historyunitQ Status - Incident History2024-03-28T05:51:08-07:00unitQtag:status.unitq.com,2005:Incident/180994672023-08-09T18:26:59-07:002023-08-09T18:26:59-07:00Identified unitQ Monitor data processing issue<p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>18:26</var> PDT</small><br><strong>Resolved</strong> - Data processing is caught up back to the present and delays in processing are resolved.</p><p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>15:56</var> PDT</small><br><strong>Update</strong> - We have added more resources to our data processing pipeline and seeing a positive trend in processing new data. We anticipate that this issue should be resolved soon.</p><p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>14:50</var> PDT</small><br><strong>Identified</strong> - We have identified the data processing issue with unitQ Monitor and are working on a fix. Please be patient as we continue work towards a resolution.<br /><br />We will let you know when we release the fix.</p>tag:status.unitq.com,2005:Incident/176575002023-06-22T15:09:25-07:002023-06-22T15:09:25-07:00Backend Scaling Issue<p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>15:09</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>13:32</var> PDT</small><br><strong>Update</strong> - Data for the last hour will be slightly delayed in processing.</p><p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>13:26</var> PDT</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>13:22</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.unitq.com,2005:Incident/174851362023-06-07T09:28:29-07:002023-06-07T09:28:29-07:00Investigating data processing issue with unitQ Monitor<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>09:28</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>09:07</var> PDT</small><br><strong>Update</strong> - The issue affecting unitQ data processing has been successfully resolved. Thank you for your patience.</p><p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>18:58</var> PDT</small><br><strong>Update</strong> - Data pipeline auditing is proceeding well. We expect to have all of last week's data reviewed by tomorrow.</p><p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>07:28</var> PDT</small><br><strong>Monitoring</strong> - Data capacity is fully restored and recent data has been classified at historical levels. We are now auditing all feedback data from last week and closely monitoring the data pipeline as we review last week's data.</p><p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>23:33</var> PDT</small><br><strong>Identified</strong> - Root causes of the issue have been identified and we are now working to restore capacity in our data processing pipeline. We expect to have full capacity available soon. Once capacity is restored we will conduct a data audit to ensure that all user feedback is fully classified.</p><p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>19:59</var> PDT</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>19:56</var> PDT</small><br><strong>Investigating</strong> - We are aware of an issue with unitQ Monitor's data processing and our team is actively working on bringing feedback back up to full throughput. <br /><br />We are investigating the matter and will provide an update later this evening and as our investigation progresses.</p>tag:status.unitq.com,2005:Incident/172955942023-05-18T15:49:46-07:002023-05-18T15:49:46-07:00Login Issue<p><small>May <var data-var='date'>18</var>, <var data-var='time'>15:49</var> PDT</small><br><strong>Resolved</strong> - Okta has posted that the incident is resolved as you can see here: https://status.okta.com/#incident/a9C4z000000TXDiEAO. Login functionality is restored. Apologies for any inconvenience.</p><p><small>May <var data-var='date'>18</var>, <var data-var='time'>15:05</var> PDT</small><br><strong>Monitoring</strong> - Root cause has been identified as an outage from Okta which can be monitored here https://status.okta.com/. It appears that most, if not all users should now be able to log in. We will be monitoring the situation closely and continue to provide regular updates.</p><p><small>May <var data-var='date'>18</var>, <var data-var='time'>14:42</var> PDT</small><br><strong>Investigating</strong> - We are investigating an issue preventing customers from logging in to unitQ. We've investigating currently. Stay tuned here for more updates, next update: 4:30 PM PST.</p>tag:status.unitq.com,2005:Incident/166117362023-03-23T15:30:38-07:002023-03-23T15:30:38-07:00Identified unitQ Monitor data processing issue<p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>15:30</var> PDT</small><br><strong>Resolved</strong> - The backfill of data is complete and fully accessible on the platform. Thank you for your patience and understanding.</p><p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>08:30</var> PDT</small><br><strong>Monitoring</strong> - All services are now back to normal, and able to receive, search, and evaluate monitors as normal. Some customers may still observe gaps in historical data for parts of the last 24 hours, and we are continuing with the backfilling operations.</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>17:23</var> PDT</small><br><strong>Update</strong> - unitQ Monitor is experiencing delays in processing data for some sources, especially Zendesk, and we have suspended Alerts until this issue is resolved to prevent issuing false positive Alerts. We have now identified the root cause of the problem. This issue was accidentally introduced from a system upgrade which resulted in sending twice as much feedback than usual through our pipeline, intermingling brand new feedback with reprocessed feedback, and leading to some delays in processing the new feedback. We have increased capacity in our pipeline to more quickly process this backlog of data. We estimate that it will take at least several hours to process all of this feedback, so we anticipate that this issue should be resolved sometime tomorrow. We will provide regular updates as the situation progresses. Thank you for your patience and feel free to reach out to us with any questions.</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>16:06</var> PDT</small><br><strong>Update</strong> - Alerts on Monitors and Saved Searches have been suspended while we investigate this issue.</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>16:00</var> PDT</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>15:51</var> PDT</small><br><strong>Identified</strong> - We have identified a data processing issue with unitQ Monitor where some sources such as Zendesk are experiencing a delay of several hours. We are working on a fix, please be patient as we continue work towards a resolution.<br /><br />We will let you know this issue has resolved.</p>tag:status.unitq.com,2005:Incident/164070972023-03-09T14:50:13-08:002023-03-09T14:50:13-08:00Investigating issue with unitQ Monitor<p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>14:50</var> PST</small><br><strong>Resolved</strong> - The issue with unitQ Monitor has been resolved. Thank you for your patience.</p><p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>14:45</var> PST</small><br><strong>Investigating</strong> - We are aware of an issue with unitQ Monitor and our team is actively investigating it.
<br />
<br />We will provide updates as our investigation progresses.</p>tag:status.unitq.com,2005:Incident/161707632023-02-16T19:11:16-08:002023-02-16T19:11:16-08:00unitQ Monitor Networking Maintenance<p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>19:11</var> PST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>19:00</var> PST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>17:11</var> PST</small><br><strong>Scheduled</strong> - unitQ Monitor will be offline so we can perform some important maintenance. We anticipate that service will be fully restored in minutes. Thanks for your patience.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>17:11</var> PST</small><br><strong>In progress</strong> - unitQ Monitor will be offline so we can perform some important maintenance. We anticipate that service will be fully restored in minutes. Thanks for your patience.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>17:05</var> PST</small><br><strong>Scheduled</strong> - unitQ Monitor is offline so we can perform some important maintenance. We anticipate that service will be fully restored in minutes. Thanks for your patience.</p>