tag:vyopta.statuspage.io,2005:/historyVyopta Status - Incident History2024-03-28T13:40:20-05:00Vyoptatag:vyopta.statuspage.io,2005:Incident/203236732024-03-23T12:33:20-05:002024-03-23T12:33:20-05:00my.vyopta.com - Database Maintenance<p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>12:33</var> CDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>12:00</var> CDT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>21</var>, <var data-var='time'>18:27</var> CDT</small><br><strong>Scheduled</strong> - We will be performing maintenance on the Analytics database servers this Saturday. There may be brief outages as they are restarted during the maintenance window. If you are unable to access a specific module, we recommend waiting until the end of our maintenance window.</p>tag:vyopta.statuspage.io,2005:Incident/203093842024-03-20T08:20:35-05:002024-03-20T08:20:35-05:00New Infrastructure Addition Fails - Existing systems unaffected<p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>08:20</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved. The User Interface was deployed prior to the deployment of a backend service to support it adding new infrastructure.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>06:29</var> CDT</small><br><strong>Investigating</strong> - We are aware of an issue preventing some customers from adding new infrastructure to their Vyopta configuration, and are investigating the cause. <br /><br />Systems already configured within the Vyopta platform are unaffected by this issue.</p>tag:vyopta.statuspage.io,2005:Incident/200604912024-02-26T16:02:50-06:002024-02-26T16:02:50-06:00Space Insights Outage<p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>16:02</var> CST</small><br><strong>Resolved</strong> - The issue that caused empty datasets for Space Insights customers has been resolved. It was due to an unexpected connectivity issue related to a recent feature release. The release was patched within 4 hours of the problem being reported and monitored over the weekend. For affected customers, we apologize for this inconvenience; please rest assured that no data was lost and room activity during that time will be reflected properly in the product. Thank you for your continued patience and support.</p><p><small>Feb <var data-var='date'>23</var>, <var data-var='time'>18:18</var> CST</small><br><strong>Monitoring</strong> - A patch has been applied in the last couple of hours, which addressed the issue. Will continue to monitor over the next couple of days, and provide an update on the results early next week.</p><p><small>Feb <var data-var='date'>23</var>, <var data-var='time'>15:15</var> CST</small><br><strong>Investigating</strong> - Customers are reporting empty datasets for bookings and workspaces in the Space Insights module. We are currently researching the issue</p>tag:vyopta.statuspage.io,2005:Incident/199109832024-02-06T04:33:49-06:002024-02-06T04:33:49-06:00Scheduled Reports Not Being Delivered<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>04:33</var> CST</small><br><strong>Resolved</strong> - Vyopta's engineering team have resolved the issue. Reports delayed due to this issue have been delivered.</p><p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>10:23</var> CST</small><br><strong>Update</strong> - Vyopta's engineering team have resolved the issue. Previously missed reports are being processed and should be delivered shortly. We are continuing to monitor for any further issues.</p><p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>10:22</var> CST</small><br><strong>Monitoring</strong> - We are continuing to monitor for any further issues.</p><p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>08:52</var> CST</small><br><strong>Identified</strong> - Vyopta's engineering team have identified the issue. Previously missed reports are being processed and should be delivered shortly. We will continue to monitor the situation.</p><p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>03:45</var> CST</small><br><strong>Investigating</strong> - Some customers may not be receiving scheduled reports at this time - we are investigating why this is the case and will provide updates here as soon as possible.</p>tag:vyopta.statuspage.io,2005:Incident/198710072024-02-03T13:41:19-06:002024-02-03T13:41:19-06:00my.vyopta.com - System Maintenance<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>13:41</var> CST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>13:00</var> CST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>17:13</var> CST</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.<br /><br />Event monitors will be delayed until the end of the maintenance window.</p>tag:vyopta.statuspage.io,2005:Incident/198560482024-01-30T17:58:59-06:002024-01-30T17:58:59-06:00Monitoring KPIs / Trend panels Not Updating<p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>17:58</var> CST</small><br><strong>Resolved</strong> - Our engineering team identified and implemented a solution to address the issue. Following their investigation, all monitoring KPIs and trend functionalities have been restored to full functionality. Our monitors are now operational, providing accurate and timely data as expected.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>14:41</var> CST</small><br><strong>Monitoring</strong> - We are no longer seeing any delays with customers data within monitoring. Customers may receive false positive monitor alert emails due to todays outage. We will monitor this issue over the next 24 hours.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>12:25</var> CST</small><br><strong>Identified</strong> - The issue has been identified and a fix has been implemented. Customers may see a delay in data with monitoring KPIs/Trends and monitor alerts for the next 1-2 hours. Once a delay is no longer seen, we will being monitoring over the next 24 hours.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>10:19</var> CST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>04:08</var> CST</small><br><strong>Investigating</strong> - Some customers may have KPIs and trend panels that are not updating in Monitoring, although data is present in other panels. We are investigating the cause of this issue and will provide updates here as soon as any information is available.</p>tag:vyopta.statuspage.io,2005:Incident/198559402024-01-30T17:34:53-06:002024-02-05T08:51:39-06:00Scheduled Reports Not Being Delivered<p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>17:34</var> CST</small><br><strong>Resolved</strong> - This incident has been resolved by our engineering team. Previously missed reports have been delivered.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>03:49</var> CST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>10:06</var> CST</small><br><strong>Monitoring</strong> - Vyopta's engineering team have resolved the issue. Previously missed reports should be delivered shortly. We will continue to monitor the situation.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>03:54</var> CST</small><br><strong>Investigating</strong> - Some customers may not be receiving scheduled reports at this time - we are investigating why this is the case and will provide updates here as soon as possible.</p>tag:vyopta.statuspage.io,2005:Incident/198315072024-01-26T12:21:11-06:002024-01-26T12:21:11-06:00FR.vyopta.com - MSTeams Data Collection Issues<p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>12:21</var> CST</small><br><strong>Resolved</strong> - Our engineering team have resolved this incident which was a result of a recent update. No issues observed in the last 24 hours.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>12:28</var> CST</small><br><strong>Monitoring</strong> - A fix has been implemented and collection of MSTeams calls has resumed. We will monitor over the next 24 hours.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>12:06</var> CST</small><br><strong>Investigating</strong> - We're currently investigating MSTeams collection issues for the fr.vyopta.com</p>tag:vyopta.statuspage.io,2005:Incident/197967962024-01-23T09:31:53-06:002024-01-23T09:31:53-06:00Some Customers Reporting issues with Analytics Dashboard and Datasets<p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>09:31</var> CST</small><br><strong>Resolved</strong> - Our engineering team have resolved this incident which was a result of a database connectivity issue. The engineering team will improve our exception handling and monitoring for this scenario.</p><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>12:54</var> CST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>12:51</var> CST</small><br><strong>Monitoring</strong> - A fix has been implemented for the customers impacted by analytics dashboards and datasets not returning data. We will monitor this issue for the next 24 hours.</p><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>12:00</var> CST</small><br><strong>Investigating</strong> - We've received several reports with missing data within our dashboards and datasets with Technology Insights Analytics. We're currently investigating the issue.</p>tag:vyopta.statuspage.io,2005:Incident/197446642024-01-20T17:00:32-06:002024-01-20T17:00:33-06:00my.vyopta.com - System Upgrades<p><small>Jan <var data-var='date'>20</var>, <var data-var='time'>17:00</var> CST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>20</var>, <var data-var='time'>12:01</var> CST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>17</var>, <var data-var='time'>17:33</var> CST</small><br><strong>Scheduled</strong> - We will be performing a series of upgrades on our production cloud this Saturday. There will be brief outages as we upgrade components during the maintenance window. If you are unable to access a specific module, we recommend you waiting till the end of our maintenance window, and try accessing the module again<br /><br />We will be disabling our alerting engine during this time, to prevent the sending of invalid alerts.<br /><br />If you are running an on-premise data collector, we recommend that you check your collector once the maintenance window is over. We expect that your collector will not be impacted, but in some cases if you are using an older version of our collector (4.8.3 or earlier) you may have to restart your collector. You can find the steps on how to check your collector here.<br /><br />https://support.vyopta.com/hc/en-us/articles/11947737794451-How-to-check-the-status-of-your-on-premise-collector</p>tag:vyopta.statuspage.io,2005:Incident/194915802023-12-22T11:04:43-06:002023-12-22T11:04:43-06:00Reports of no quality for Zoom QSS customers<p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>11:04</var> CST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>11:04</var> CST</small><br><strong>Update</strong> - The issues with Zoom quality with QSS has since been rectified and has returned to it's normal behavior. We will mark this incident as resolved.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>08:14</var> CST</small><br><strong>Monitoring</strong> - At 12AM CST, we began receiving quality data for Zoom QSS customers. We will monitor this for the rest of the day and resolved by End of Day.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>17:23</var> CST</small><br><strong>Identified</strong> - We have identified we are not receiving quality data. We will continue working on a resolution. Next update will be in the next 24 hours.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>12:59</var> CST</small><br><strong>Investigating</strong> - We've received a report of no quality for Zoom meetings when on QSS. We're currently investigating the report of no quality.</p>tag:vyopta.statuspage.io,2005:Incident/194285722023-12-14T03:20:09-06:002023-12-14T03:20:09-06:00Intermittent Access<p><small>Dec <var data-var='date'>14</var>, <var data-var='time'>03:20</var> CST</small><br><strong>Resolved</strong> - This issue has been resolved - customers are no longer experiencing intermittent loss of access</p><p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>12:37</var> CST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>10:03</var> CST</small><br><strong>Monitoring</strong> - We have identified the cause and implemented a solution - the system is operating normally although we continue to monitor the status.</p><p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>09:39</var> CST</small><br><strong>Update</strong> - We have identified the cause of this issue and are rolling out a solution</p><p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>09:38</var> CST</small><br><strong>Identified</strong> - We have identified the cause of this issue and are rolling out a solution</p><p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>09:07</var> CST</small><br><strong>Investigating</strong> - Customers may experience intermittent issues when accessing Vyopta. <br /><br />This issue is currently under investigation</p>tag:vyopta.statuspage.io,2005:Incident/192110662023-11-27T09:24:01-06:002023-11-27T09:24:01-06:00CISCOWEBEX Collection Issue for Some Customers<p><small>Nov <var data-var='date'>27</var>, <var data-var='time'>09:24</var> CST</small><br><strong>Resolved</strong> - The Vyopta platform is working correctly and the remaining few customers who need to re-authenticate their Webex systems have been notified.</p><p><small>Nov <var data-var='date'>24</var>, <var data-var='time'>10:37</var> CST</small><br><strong>Monitoring</strong> - We have identified the cause of the issue, which lies with authentication of the Webex system with Cisco's authentication service. Vyopta has taken steps to correct this issue wherever possible but a small number of customers may still be experiencing collection issues.<br /><br />In the event that you are still experiencing collection issues with your Cisco Webex system, please re-authenticate the existing system as described here: https://support.vyopta.com/hc/en-us/articles/1500000349141-Cisco-Webex-Integration.</p><p><small>Nov <var data-var='date'>24</var>, <var data-var='time'>09:42</var> CST</small><br><strong>Investigating</strong> - Some customers may be experiencing problems with data collection from CISCO Webex systems. We are aware of the issue and it is under investigation.</p>tag:vyopta.statuspage.io,2005:Incident/190351302023-11-06T10:10:52-06:002023-11-06T10:10:52-06:00Reports not being sent from the Vyopta Platform<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>10:10</var> CST</small><br><strong>Resolved</strong> - Our engineering team have resolved this incident and the backlog of reports has been processed.</p><p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>08:52</var> CST</small><br><strong>Monitoring</strong> - Our engineering team have identified the issue and have implemented a fix.</p><p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>08:23</var> CST</small><br><strong>Investigating</strong> - Our engineering team is currently investigating this issue</p>tag:vyopta.statuspage.io,2005:Incident/190020162023-11-06T08:41:50-06:002023-11-06T08:41:50-06:00No Real Time Webex Data<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>08:41</var> CST</small><br><strong>Resolved</strong> - The issues with Webex collection has since been rectified and has returned to it's normal behavior. We will mark this incident as resolved.</p><p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>09:58</var> CDT</small><br><strong>Monitoring</strong> - Our investigation today indicates the issue was resolved sometime yesterday by Webex. Analytics data should not have been affected. We will monitor this for the rest of the day and resolved by End of Day.</p><p><small>Nov <var data-var='date'> 2</var>, <var data-var='time'>13:00</var> CDT</small><br><strong>Identified</strong> - We have confirmed we are not receiving the necessary data back from Webex. We have contacted Webex Support to help us resolve the issue. We will provide another update tomorrow at the latest.</p><p><small>Nov <var data-var='date'> 2</var>, <var data-var='time'>12:01</var> CDT</small><br><strong>Investigating</strong> - We are currently investigating issues with Webex collection. Preliminary analysis indicates Webex is not providing meeting quality data to consume.</p>tag:vyopta.statuspage.io,2005:Incident/188562492023-10-30T14:08:09-05:002023-10-30T14:08:09-05:00Customers are seeing a high volume of false alerts<p><small>Oct <var data-var='date'>30</var>, <var data-var='time'>14:08</var> CDT</small><br><strong>Resolved</strong> - We have successfully pinpointed the root cause behind the false alert emails generated by the affected service. Our dedicated engineering team has implemented a robust fix for the issue. While it's important to note that such occurrences are exceptionally rare, there may still be isolated cases where the service may inadvertently trigger false alerts for a small subset of customers it serves. We appreciate your patience and understanding as we work towards ensuring a seamless experience for all our users.</p><p><small>Oct <var data-var='date'>19</var>, <var data-var='time'>15:14</var> CDT</small><br><strong>Monitoring</strong> - The high number of false alerts that were sent out impacted a small number of customers. The cause has been identified and we will continue to monitor.</p><p><small>Oct <var data-var='date'>19</var>, <var data-var='time'>13:32</var> CDT</small><br><strong>Update</strong> - Update: We have found that a couple of customers have been affected, while the majority have not received false alerts. We are continuing to investigate.</p><p><small>Oct <var data-var='date'>19</var>, <var data-var='time'>12:25</var> CDT</small><br><strong>Investigating</strong> - We are investigating reports of high volume of false alerts. Will provide more detail once its available.</p>tag:vyopta.statuspage.io,2005:Incident/186237452023-10-02T13:10:55-05:002023-10-02T13:10:55-05:00No Real Time Webex Data<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>13:10</var> CDT</small><br><strong>Resolved</strong> - Webex Team indicated the outage on the 27th was related to an incident on that day that caused API collection issues. The issue has since been rectified and Webex collection has returned to it's normal behavior. We will mark this incident as resolved.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>14:53</var> CDT</small><br><strong>Monitoring</strong> - Webex Support has indicated the issue was related to an incident yesterday. We are currently seeing Webex data coming in for our customers. We will monitor Webex data for the next 24 hours.</p><p><small>Sep <var data-var='date'>27</var>, <var data-var='time'>11:55</var> CDT</small><br><strong>Identified</strong> - We have confirmed we are not receiving the necessary data back from Webex. We have contacted Webex Support to help us resolve the issue. We will provide another update tomorrow at the latest.</p><p><small>Sep <var data-var='date'>27</var>, <var data-var='time'>11:42</var> CDT</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Sep <var data-var='date'>27</var>, <var data-var='time'>11:41</var> CDT</small><br><strong>Investigating</strong> - We are currently investigating issues with Webex collection. Preliminary analysis indicates Webex is not providing meeting quality data to consume</p>tag:vyopta.statuspage.io,2005:Incident/186258642023-09-30T15:00:22-05:002023-09-30T15:00:22-05:00my.vyopta.com - System Upgrades<p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>15:00</var> CDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Sep <var data-var='date'>30</var>, <var data-var='time'>12:01</var> CDT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Sep <var data-var='date'>27</var>, <var data-var='time'>16:10</var> CDT</small><br><strong>Scheduled</strong> - We will be performing a series of upgrades on our production cloud this Saturday. There will be brief outages as we upgrade components during the maintenance window. If you are unable to access a specific module, we recommend you waiting till the end of our maintenance window, and try accessing the module again<br /><br />We will be disabling our alerting engine during this time, to prevent the sending of invalid alerts.<br /><br />If you are running an on-premise data collector, we recommend that you check your collector once the maintenance window is over. We expect that your collector will not be impacted, but in some cases if you are using an older version of our collector (4.8.3 or earlier) you may have to restart your collector. You can find the steps on how to check your collector here.<br /><br />https://support.vyopta.com/hc/en-us/articles/11947737794451-How-to-check-the-status-of-your-on-premise-collector</p>tag:vyopta.statuspage.io,2005:Incident/185868682023-09-23T15:07:21-05:002023-09-23T15:07:21-05:00my.vyopta.com - System Upgrades<p><small>Sep <var data-var='date'>23</var>, <var data-var='time'>15:07</var> CDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Sep <var data-var='date'>23</var>, <var data-var='time'>12:07</var> CDT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Sep <var data-var='date'>23</var>, <var data-var='time'>12:06</var> CDT</small><br><strong>Scheduled</strong> - We will be performing a series of upgrades on our production cloud this Saturday. There will be brief outages as we upgrade components during the maintenance window. If you are unable to access a specific module, we recommend you waiting till the end of our maintenance window, and try accessing the module again<br /><br />We will be disabling our alerting engine during this time, to prevent the sending of invalid alerts.<br /><br />If you are running an on-premise data collector, we recommend that you check your collector once the maintenance window is over. We expect that your collector will not be impacted, but in some cases if you are using an older version of our collector (4.8.3 or earlier) you may have to restart your collector. You can find the steps on how to check your collector here.<br /><br />https://support.vyopta.com/hc/en-us/articles/11947737794451-How-to-check-the-status-of-your-on-premise-collector</p>tag:vyopta.statuspage.io,2005:Incident/183228912023-09-05T19:03:55-05:002023-09-05T19:03:55-05:00No Real Time Webex Data<p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>19:03</var> CDT</small><br><strong>Resolved</strong> - This incident has been resolved after the Webex team at Cisco deployed a fix on September 1st.</p><p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>08:35</var> CDT</small><br><strong>Monitoring</strong> - The Webex engineering team has deployed a fix around 12AM PST. Real Time Meeting data is now available within CPM Monitoring. We will monitor the behavior and begin back polling Analytics data if needed.</p><p><small>Aug <var data-var='date'>31</var>, <var data-var='time'>09:48</var> CDT</small><br><strong>Update</strong> - The Webex engineering team will be deploying a fix overnight. Once that has been deployed, we will verify behavior and monitor the issue.</p><p><small>Aug <var data-var='date'>30</var>, <var data-var='time'>12:03</var> CDT</small><br><strong>Identified</strong> - We have confirmed we are not receiving data back from Webex. We have contacted Webex Support to help us resolve the issue. We will provide another update tomorrow at the latest.</p><p><small>Aug <var data-var='date'>30</var>, <var data-var='time'>11:28</var> CDT</small><br><strong>Investigating</strong> - We are currently investigating issues with Webex collection. Preliminary analysis indicates Webex is not providing the meeting information to consume.</p>tag:vyopta.statuspage.io,2005:Incident/183081272023-09-01T13:14:31-05:002023-09-07T15:17:17-05:00Customers are seeing a high volume of false alerts<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>13:14</var> CDT</small><br><strong>Resolved</strong> - We have identified the issue and will be providing documentation on how to address this issue in the coming days.</p><p><small>Aug <var data-var='date'>30</var>, <var data-var='time'>10:15</var> CDT</small><br><strong>Investigating</strong> - We are still investigating why a couple of our customers are being impacted by a high volume of false alerts. Will provide an update once we have identified the problem</p><p><small>Aug <var data-var='date'>29</var>, <var data-var='time'>15:25</var> CDT</small><br><strong>Identified</strong> - We've determined that the problem is affecting only a small number of our clients, and the alerting system should be functioning correctly for all other customers.</p><p><small>Aug <var data-var='date'>29</var>, <var data-var='time'>09:56</var> CDT</small><br><strong>Investigating</strong> - We are investigating reports of high volume of false alerts. Will provide more detail once its available.</p>tag:vyopta.statuspage.io,2005:Incident/177929022023-07-08T15:00:15-05:002023-07-08T15:00:15-05:00US Cloud and EU Cloud - System Upgrades<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>15:00</var> CDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>12:00</var> CDT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>13:49</var> CDT</small><br><strong>Scheduled</strong> - We will be performing a series of upgrades on our production cloud this Saturday. There will be brief outages as we upgrade components during the maintenance window. If you are unable to access a specific module, we recommend you waiting till the end of our maintenance window, and try accessing the module again<br /><br />We will be disabling our alerting engine during this time, to prevent the sending of invalid alerts.<br /><br />If you are running an on-premise data collector, we recommend that you check your collector once the maintenance window is over. We expect that your collector will not be impacted, but in some cases if you are using an older version of our collector (4.8.3 or earlier) you may have to restart your collector. You can find the steps on how to check your collector here.<br /><br />https://support.vyopta.com/hc/en-us/articles/11947737794451-How-to-check-the-status-of-your-on-premise-collector</p>tag:vyopta.statuspage.io,2005:Incident/177714782023-07-06T12:03:08-05:002023-07-06T12:03:19-05:00Reported issues with CPM Analytics in EU Cloud<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>12:03</var> CDT</small><br><strong>Resolved</strong> - Issue has been resolved after monitoring for 24 hours. RCA will be provided.</p><p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>11:05</var> CDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we're currently monitoring the results.</p><p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>09:54</var> CDT</small><br><strong>Investigating</strong> - We are currently investigating reports of data not loading within CPM Analytics within the EU Cloud.</p>tag:vyopta.statuspage.io,2005:Incident/177549312023-07-05T08:46:45-05:002023-07-06T12:01:10-05:00Investigating reports of Non-Streamed data missing from CPM Monitoring<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>08:46</var> CDT</small><br><strong>Resolved</strong> - We have been monitoring the service since the fix has been implemented and have not seen the issue arise. All Non-Streamed data going to CPM Monitoring has been processed and no service delays are observed.</p><p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>14:40</var> CDT</small><br><strong>Monitoring</strong> - The service responsible for sending Non-Streamed data to CPM Monitoring had failed. The service was started and Non-Streamed data is now making it through. The service is processing all the data, therefore a delay in Microsoft Teams and Cisco Call Manager will be observed. We will monitor the progress and update once complete.</p><p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>14:00</var> CDT</small><br><strong>Investigating</strong> - We are currently investigating reports of Non-Streamed data missing from CPM Monitoring. This currently impacts Microsoft Teams calls and Cisco Call Manager.</p>tag:vyopta.statuspage.io,2005:Incident/176941112023-06-28T09:37:09-05:002023-07-06T11:59:41-05:00Users unable to log into Vyopta CPM<p><small>Jun <var data-var='date'>28</var>, <var data-var='time'>09:37</var> CDT</small><br><strong>Resolved</strong> - We have been monitoring the platform since the fix has been implemented and have not seen the issue arise. A RCA will be provided within a week.</p><p><small>Jun <var data-var='date'>26</var>, <var data-var='time'>20:53</var> CDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are currently monitoring the platform. Users are now able to access CPM Monitoring and Analytics. The alert generator was shutdown to minimize false alerts from being sent out, and will be turned back on in an hour.</p><p><small>Jun <var data-var='date'>26</var>, <var data-var='time'>20:37</var> CDT</small><br><strong>Identified</strong> - The issue has been identified and our engineers are working on a fix.</p><p><small>Jun <var data-var='date'>26</var>, <var data-var='time'>20:20</var> CDT</small><br><strong>Investigating</strong> - We are currently investigating reports of users unable to log in.<br />Users using my.vyopta.com are getting a "Failed to fetch" message while SSO users are getting a "502 Bad Gateway"<br />We will provide an update once we have identified the issue.</p>