Aug <var data-var='date'> 3</var>, <var data-var='time'>22:54</var> UTC Resolved - Our service provider has reported that service has been restored and Virtual Assistant works as expected. Aug <var data-var='date'> 3</var>, <var data-var='time'>22:28</var> UTC Monitoring - We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it. Aug <var data-var='date'> 3</var>, <var data-var='time'>21:58</var> UTC Investigating - Our service provider has reported service disruption affecting Virtual Assistant. We are communicating with our service provider and closely monitoring the incident and their developments to fix it. Thank you for your patience.

[Some GVA users] Service provider reporting service disruption affecting Virtual Assistant

Jun <var data-var='date'>24</var>, <var data-var='time'>17:22</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>24</var>, <var data-var='time'>17:11</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>24</var>, <var data-var='time'>17:11</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>24</var>, <var data-var='time'>17:10</var> UTC Update - We are currently investigating an elevated number of errors in our telemetry. We are working to solve this issue. Jun <var data-var='date'>24</var>, <var data-var='time'>17:09</var> UTC Investigating - We are currently investigating an elevated number of errors in our telemetry. We are working to solve this issue.

GVA Downtime

Jun <var data-var='date'>10</var>, <var data-var='time'>17:20</var> UTC Resolved - The problem that was causing GVAs to experience intermittent failures has now been fully resolved and all services are fully operational. Thank you! Jun <var data-var='date'>10</var>, <var data-var='time'>16:49</var> UTC Monitoring - We have implemented a fix and our telemetry shows that all systems are fully operational. We are actively monitoring the fix deployment to confirm this has been resolved. Jun <var data-var='date'>10</var>, <var data-var='time'>16:06</var> UTC Identified - The problem that is causing GVAs to experiencing intermittent failures has now been identified and our team is working on a fix to address it. We continue on this. Thank you for your continued patience! Jun <var data-var='date'>10</var>, <var data-var='time'>15:37</var> UTC Investigating - We are seeing high error rates from the Banking Flows when attempting to authenticate users via GVA. Users could be experiencing intermittent failures. We are aware of the issue and are working on a fix to remediate the issue. Thank you for your patience.

[Some GVA Users] Elevated rate of errors for Auth GVA

May <var data-var='date'> 8</var>, <var data-var='time'>02:12</var> UTC Resolved - Glia is fully operational and the incident is resolved. May <var data-var='date'> 8</var>, <var data-var='time'>02:05</var> UTC Monitoring - Our telemetry shows that all systems are fully operational. We are continuing to monitor the issue. May <var data-var='date'> 8</var>, <var data-var='time'>01:20</var> UTC Identified - We are experiencing an elevated rate of errors and users could be experiencing intermittent failures with reporting. We are aware of the issue and are working on a fix to remediate the issue.

Elevated rate of errors for Glia affecting reporting

May <var data-var='date'> 8</var>, <var data-var='time'>01:47</var> UTC Resolved - Our service provider has reported that service has been restored, our telemetry and monitoring shows that Glia works as expected. May <var data-var='date'> 8</var>, <var data-var='time'>01:15</var> UTC Monitoring - We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it. May <var data-var='date'> 8</var>, <var data-var='time'>00:37</var> UTC Identified - Our service provider has reported service disruption affecting Glia Platform. We are communicating with our service provider and closely monitoring the incident and their developments to fix it.

Service provider reporting service disruption affecting Glia

Feb <var data-var='date'>22</var>, <var data-var='time'>09:00</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>22</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'> 6</var>, <var data-var='time'>19:17</var> UTC Scheduled - We will be undergoing scheduled maintenance during this time.

US Hosting Infrastructure Upgrade

Jan <var data-var='date'>31</var>, <var data-var='time'>12:00</var> UTC Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>31</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>19</var>, <var data-var='time'>18:25</var> UTC Scheduled - We will be undergoing scheduled maintenance during this time.

Jan <var data-var='date'>19</var>, <var data-var='time'>13:43</var> UTC Resolved - We have verified that the post-engagement surveys are now working as intended. Jan <var data-var='date'>19</var>, <var data-var='time'>13:35</var> UTC Monitoring - We are currently monitoring the results to ensure that engagements are fully functional. Jan <var data-var='date'>19</var>, <var data-var='time'>13:28</var> UTC Identified - The issue has been indentified and a fix has been implemented. Jan <var data-var='date'>19</var>, <var data-var='time'>13:17</var> UTC Investigating - A small number of users are unable to end engagements due to the post-engagement survey not closing.

Partial degradation of service

Dec <var data-var='date'>11</var>, <var data-var='time'>15:30</var> UTC Resolved - The root cause has been identified and all engagements are fully functional. Dec <var data-var='date'>11</var>, <var data-var='time'>15:08</var> UTC Update - We continue to investigate. The impact is minimal, causing a few engagements that need to be ended by the visitor. Dec <var data-var='date'>11</var>, <var data-var='time'>13:47</var> UTC Investigating - We are investigating a small number of transferred engagements that do not end for the visitor once the operator has ended them.

Partial degradation of outbound calls

Dec <var data-var='date'> 7</var>, <var data-var='time'>12:00</var> UTC Completed - The scheduled maintenance has been completed. Dec <var data-var='date'> 7</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov <var data-var='date'>25</var>, <var data-var='time'>00:18</var> UTC Scheduled - We will be undergoing scheduled maintenance during this time.

Dec <var data-var='date'> 3</var>, <var data-var='time'>16:55</var> UTC Resolved - The incident has been resolved, our telemetry shows that all features continue to be fully functional. Dec <var data-var='date'> 3</var>, <var data-var='time'>16:49</var> UTC Monitoring - There was an elevated number of errors affecting a small number of Phone GVA interactions. The operations team has taken actions to address these issues, and our telemetry shows that all phone GVA interactions are now working as expected. We are continuing to monitor the issue.

Elevated number of errors affecting a small number of Phone GVA interactions

Nov <var data-var='date'> 3</var>, <var data-var='time'>19:44</var> UTC Resolved - This incident has been resolved. All Cortex AI services are fully operational. Nov <var data-var='date'> 3</var>, <var data-var='time'>19:29</var> UTC Update - Our team continues to monitor system behavior. Forecast Analyst, Cortex Wrap-Up, and Cortex Heads-Up are fully operational. Nov <var data-var='date'> 3</var>, <var data-var='time'>19:09</var> UTC Monitoring - Our team has identified this issue and is currently monitoring the behavior for further updates. Nov <var data-var='date'> 3</var>, <var data-var='time'>18:12</var> UTC Investigating - We are currently investigating an issue affecting the performance of the Cortex AI features.

Service disruption of Glia Platform affecting Cortex AI

Nov <var data-var='date'> 2</var>, <var data-var='time'>06:00</var> UTC Completed - The scheduled maintenance has been completed. Nov <var data-var='date'> 2</var>, <var data-var='time'>04:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct <var data-var='date'>16</var>, <var data-var='time'>12:42</var> UTC Scheduled - We are testing our failover procedures. Only EU clients are affected.

EU Failover training

Oct <var data-var='date'>21</var>, <var data-var='time'>14:48</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'>21</var>, <var data-var='time'>14:42</var> UTC Investigating - We are currently investigating an elevated number of errors in our telemetry with Cortex AI. We are working to solve this issue.

Elevated number of errors in our telemetry impacting Cortex AI features

Oct <var data-var='date'>21</var>, <var data-var='time'>06:51</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'>20</var>, <var data-var='time'>23:08</var> UTC Monitoring - Our team has confirmed that all data is available and is actively being processed. Some customers may experience minor delays in viewing their processed data. Our systems continue to work through all outstanding information to ensure full completion.

Service disruption of Glia Platform affecting Insights

Oct <var data-var='date'>20</var>, <var data-var='time'>23:08</var> UTC Resolved - Our team has confirmed that all data is available and is actively being processed. Some customers may experience minor delays in viewing their processed data. Our systems continue to work through all outstanding information to ensure full completion. Oct <var data-var='date'>20</var>, <var data-var='time'>22:29</var> UTC Update - Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>21:38</var> UTC Update - We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>20:37</var> UTC Update - We are actively assessing the specific scope of this service interruption. We have confirmed a clear link to the current, widespread AWS operational incident. Please refer to the official AWS status page for updates on the overarching issue: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>20:02</var> UTC Update - Our team is conducting internal diagnostics to assess the exact impact on our service. This interruption is associated with the current AWS operational event. The overall status of the incident can be monitored here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>19:36</var> UTC Update - We are actively reviewing our systems in light of the current AWS incident. This issue is directly related to that event. For updates on the overall situation, please refer to the AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>19:03</var> UTC Update - We are continuing to assess the extent of the disruption. The service interruption is associated with the reported AWS platform incident. We advise tracking the broader situation via the official AWS status page: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>18:33</var> UTC Update - We're continuing our investigation into the specific impact on our service. The service interruption is connected to the ongoing, widespread AWS incident. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>18:10</var> UTC Update - Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>17:34</var> UTC Update - We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>17:00</var> UTC Update - Our investigation is continuing. This service issue is tied to the current AWS incident. See the AWS status page for details: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>15:29</var> UTC Investigating - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>14:45</var> UTC Identified - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>13:37</var> UTC Update - We are continuing to investigate this issue. Oct <var data-var='date'>20</var>, <var data-var='time'>13:36</var> UTC Investigating - We are currently investigating an issue affecting the performance of Insights. We are working to resolve this issue. We will share updated info here as soon as possible.

Oct <var data-var='date'>20</var>, <var data-var='time'>22:57</var> UTC Resolved - The incident has been fully resolved with all instances fully functional and performing as expected. Oct <var data-var='date'>20</var>, <var data-var='time'>22:38</var> UTC Monitoring - We have implemented a fix and are monitoring the system as it recovers. We are continuing to monitor the issue. Oct <var data-var='date'>20</var>, <var data-var='time'>22:35</var> UTC Identified - The system is recovering. Our engineering team is working on clearing out stuck engagements. Our expected time to completion is 20 min.

Infrastructure Service Provider Reporting Service Disruption Affecting Glia Engagement Routing

Oct <var data-var='date'>20</var>, <var data-var='time'>21:25</var> UTC Resolved - Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia SMS Services work as expected. Oct <var data-var='date'>20</var>, <var data-var='time'>20:37</var> UTC Update - We are actively assessing the specific scope of this service interruption. We have confirmed a clear link to the current, widespread AWS operational incident. Please refer to the official AWS status page for updates on the overarching issue: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>20:02</var> UTC Update - Our team is conducting internal diagnostics to assess the exact impact on our service. This interruption is associated with the current AWS operational event. The overall status of the incident can be monitored here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>19:36</var> UTC Update - We are actively reviewing our systems in light of the current AWS incident. This issue is directly related to that event. For updates on the overall situation, please refer to the AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>19:03</var> UTC Update - We are continuing to assess the extent of the disruption. The service interruption is associated with the reported AWS platform incident. We advise tracking the broader situation via the official AWS status page: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>18:33</var> UTC Update - We're continuing our investigation into the specific impact on our service. The service interruption is connected to the ongoing, widespread AWS incident. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>18:10</var> UTC Update - Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>17:33</var> UTC Update - We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>16:59</var> UTC Update - Our investigation is continuing. This service issue is tied to the current AWS incident. See the AWS status page for details: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>15:28</var> UTC Update - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>14:45</var> UTC Update - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>11:58</var> UTC Update - Our Phone Service Provider has reported a service disruption affecting SMS engagements for our EU customers only. We are communicating closely with the provider and monitoring developments to fix the incident. Oct <var data-var='date'>20</var>, <var data-var='time'>11:54</var> UTC Identified - Our Phone Service Provider has reported service disruption affecting phone engagements. We are communicating and monitoring closely the incident and the developments to fix it.

EU: SMS Service Provider reporting service disruption affecting Glia

Oct <var data-var='date'>20</var>, <var data-var='time'>21:08</var> UTC Resolved - Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia Engagement Routing works as expected. Oct <var data-var='date'>20</var>, <var data-var='time'>20:40</var> UTC Monitoring - We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it. Oct <var data-var='date'>20</var>, <var data-var='time'>20:37</var> UTC Update - We are actively assessing the specific scope of this service interruption. We have confirmed a clear link to the current, widespread AWS operational incident. Please refer to the official AWS status page for updates on the overarching issue: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>19:51</var> UTC Update - The team is starting to see the system recover. AWS is currently throttling the speed of requests which adversely impacts real-time systems. We are in active communication with AWS and their engineers are on the line with our team. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>19:35</var> UTC Update - We are actively reviewing our systems in light of the current AWS incident. This issue is directly related to that event. For updates on the overall situation, please refer to the AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>19:03</var> UTC Update - We are continuing to assess the extent of the disruption. The service interruption is associated with the reported AWS platform incident. We advise tracking the broader situation via the official AWS status page: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>18:31</var> UTC Update - We're continuing our investigation into the specific impact on our service. The service interruption is connected to the ongoing, widespread AWS incident. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>18:09</var> UTC Update - Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>17:35</var> UTC Update - We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>17:01</var> UTC Update - Our investigation is continuing. This service issue is tied to the current AWS incident. See the AWS status page for details: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>16:38</var> UTC Update - We are continuing to investigate this issue. Oct <var data-var='date'>20</var>, <var data-var='time'>16:35</var> UTC Investigating - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status).

Infrastructure service provider reporting service disruption affecting Glia Engagement Routing

Oct <var data-var='date'>20</var>, <var data-var='time'>20:42</var> UTC Resolved - Our service provider has reported that service has been restored, telemetry and monitoring shows that Glia Phone services works as expected. Oct <var data-var='date'>20</var>, <var data-var='time'>20:06</var> UTC Monitoring - We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it. Oct <var data-var='date'>20</var>, <var data-var='time'>19:35</var> UTC Update - We are actively reviewing our systems in light of the current AWS incident. This issue is directly related to that event. For updates on the overall situation, please refer to the AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>19:03</var> UTC Update - We are continuing to assess the extent of the disruption. The service interruption is associated with the reported AWS platform incident. We advise tracking the broader situation via the official AWS status page: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>18:32</var> UTC Update - We're continuing our investigation into the specific impact on our service. The service interruption is connected to the ongoing, widespread AWS incident. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>18:09</var> UTC Update - Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>17:35</var> UTC Update - We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>17:00</var> UTC Update - Our investigation is continuing. This service issue is tied to the current AWS incident. See the AWS status page for details: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>15:30</var> UTC Update - Our Phone Service Provider has reported intermittent service disruption related to an ongoing AWS incident (https://health.aws.amazon.com/health/status) affecting phone engagements. We are communicating with our service provider and closely monitoring the incident and their developments to fix it. Oct <var data-var='date'>20</var>, <var data-var='time'>14:28</var> UTC Identified - Our Phone Service Provider has reported intermittent service disruption related to an ongoing AWS incident (https://health.aws.amazon.com/health/status) affecting phone engagements. We are communicating with our service provider and closely monitoring the incident and their developments to fix it. Oct <var data-var='date'>20</var>, <var data-var='time'>14:20</var> UTC Investigating - Our Phone Service Provider has reported service disruption affecting phone engagements. We are communicating and monitoring closely the incident and the developments to fix it.

Phone Service Provider reporting service disruption affecting Glia

Oct <var data-var='date'>20</var>, <var data-var='time'>19:45</var> UTC Resolved - Our service provider has reported that service has been restored, telemetry and monitoring shows that Cortex AI services works as expected. Oct <var data-var='date'>20</var>, <var data-var='time'>18:56</var> UTC Monitoring - We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it. Oct <var data-var='date'>20</var>, <var data-var='time'>18:32</var> UTC Update - We're continuing our investigation into the specific impact on our service. The service interruption is connected to the ongoing, widespread AWS incident. You can monitor the official AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>18:10</var> UTC Update - Our service interruption stems from the ongoing AWS incident, and we are actively investigating its impact. For real-time updates, please follow the AWS status page here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>17:34</var> UTC Update - We're still actively investigating this issue. The service interruption is connected to the ongoing AWS incident you can track here: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>17:00</var> UTC Update - Our investigation is continuing. This service issue is tied to the current AWS incident. See the AWS status page for details: (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>15:29</var> UTC Investigating - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>14:46</var> UTC Identified - We are continuing to investigate this issue. This service interruption is related to the ongoing AWS incident (https://health.aws.amazon.com/health/status). Oct <var data-var='date'>20</var>, <var data-var='time'>14:09</var> UTC Investigating - We are currently investigating an issue affecting the performance of the Cortex AI features. Agents are able to connect with customers via chat, audio, video. We are working to resolve this issue. We will share updated info here as soon as possible.

Oct <var data-var='date'>20</var>, <var data-var='time'>11:06</var> UTC Resolved - Our service provider has reported that the service has been restored, and Glia works as expected. Oct <var data-var='date'>20</var>, <var data-var='time'>10:30</var> UTC Monitoring - We continue to communicate with our service provider to monitor the incident closely and follow their developments to fix it. Oct <var data-var='date'>20</var>, <var data-var='time'>10:27</var> UTC Update - Our Phone Service Provider has reported a service disruption affecting phone engagements. We are communicating and monitoring closely the incident and the developments to fix it. Oct <var data-var='date'>20</var>, <var data-var='time'>10:14</var> UTC Update - The platform provider reported that mitigation steps have been applied. Services are still in recovery at this time. Oct <var data-var='date'>20</var>, <var data-var='time'>10:12</var> UTC Identified - The platform provider reported that mitigation steps have been applied. Services are still in recovery at this time.

Infrastructure service provider reporting service disruption affecting Glia

Sep <var data-var='date'>24</var>, <var data-var='time'>16:36</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>24</var>, <var data-var='time'>16:27</var> UTC Monitoring - We have implemented a fix and are monitoring the system as it recovers. Thank you for your patience. Sep <var data-var='date'>24</var>, <var data-var='time'>16:11</var> UTC Investigating - We are currently investigating a potential degradation of Virtual Assistant performance. We are working to resolve this issue. Thank you for your patience.

[All GVA users] Potential degraded Virtual Assistant performance

Sep <var data-var='date'>24</var>, <var data-var='time'>16:18</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>24</var>, <var data-var='time'>16:12</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>24</var>, <var data-var='time'>15:49</var> UTC Update - We're currently investigating an issue affecting SMS communications. This incident is limited to SMS messages, and all other services are operating normally. We'll provide another update as soon as we have more information. Sep <var data-var='date'>24</var>, <var data-var='time'>15:46</var> UTC Investigating - We are currently investigating an elevated number of errors in our telemetry. We are working to solve this issue.

Elevated number of errors in our telemetry for SMS

Aug <var data-var='date'>24</var>, <var data-var='time'>01:32</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>24</var>, <var data-var='time'>00:48</var> UTC Investigating - We are currently investigating an issue resulting in the Virtual Assistant being unavailable. All other Glia functionalities are working as expected. We are working to resolve this issue. Thank you for your patience.

Is Glia down?

Glia status is UP

Lastest published events

[Some GVA users] Service provider reporting service disruption affecting Virtual Assistant

GVA Downtime

[Some GVA Users] Elevated rate of errors for Auth GVA

Glia Services, Components and Regions

Recent Glia events

[Some GVA users] Service provider reporting service disruption affecting Virtual Assistant

GVA Downtime

[Some GVA Users] Elevated rate of errors for Auth GVA

Elevated rate of errors for Glia affecting reporting

Service provider reporting service disruption affecting Glia

US Hosting Infrastructure Upgrade