Is Gorgias Down Right Now? Check if there is a current outage ongoing.

One of our cloud providers (Google) is encountering a widespread issue with its services impacting some components in charge of processing new messages, updating stats and search results, leading to delays.

We have identified an issue causing a delay in data processing.

Help Center related issue has been resolved.

A fix has been implemented and we are monitoring the results.

Incident Update: Help Center API Error Rate We are currently experiencing a high error rate with our Help Center API due to a sudden increase in API call volume. This situation may result in some help centers being unavailable and the AI Agent not responding correctly to user tickets. Impact: - Some help centers are experiencing downtime. - AI Agent responses may be affected with a higher failure rate. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible. We appreciate your patience and understanding as we work through this incident. We will provide updates as we receive more information. Thank you for your understanding.

A fix has been implemented and we are monitoring the results.

Incident Update: Help Center API Error RateWe are currently experiencing a high error rate with our Help Center API due to a sudden increase in API call volume. This situation may result in some help centers being unavailable and the AI Agent not responding correctly to user tickets.Impact:- Some help centers are experiencing downtime.- AI Agent responses may be affected with a higher failure rate.Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible. We appreciate your patience and understanding as we work through this incident.We will provide updates as we receive more information. Thank you for your understanding.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

On Wednesday, June 4th between 07:00 and 08:00 UTC time (03:00am and 04:00am ET), for up to 60 minutes, customers in our North America region may experience interruptions or limited availability while we perform maintenance on our infrastructure. This proactive measure is designed to continue improving the reliability, redundancy, and performance across the infrastructure of our services.Due to the nature of these changes we will be rolling them out across our regions progressively over the week of June 2nd - June 6th.If you receive an upcoming maintenance banner in the Helpdesk your account is impacted for this wave.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

On Tuesday, June 3rd between 21:00 and 22:00 UTC time (11:00pm 3rd of June and 12:00am 4th of June CEST), for up to 60 minutes, customers in our Europe region may experience interruptions or limited availability while we perform maintenance on our infrastructure. This proactive measure is designed to continue improving the reliability, redundancy, and performance across the infrastructure of our services.Due to the nature of these changes we will be rolling them out across our regions progressively over the week of June 2nd - June 6th.If you receive an upcoming maintenance banner in the Helpdesk your account is impacted for this wave.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

On Tuesday, June 3rd between 07:00 and 08:00 UTC time (03:00am and 04:00am ET), for up to 60 minutes, customers in our North America region may experience interruptions or limited availability while we perform maintenance on our infrastructure. This proactive measure is designed to continue improving the reliability, redundancy, and performance across the infrastructure of our services.Due to the nature of these changes we will be rolling them out across our regions progressively over the week of June 2nd - June 6th.If you receive an upcoming maintenance banner in the Helpdesk your account is impacted for this wave.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

On Monday, June 2nd between 22:00 and 23:00 UTC time (3rd of June 00:00am to 1:00am CEST), for up to 60 minutes, customers in our Europe region may experience interruptions or limited availability while we perform maintenance on our infrastructure. This proactive measure is designed to continue improving the reliability, redundancy, and performance across the infrastructure of our services.Due to the nature of these changes we will be rolling them out across our regions progressively over the week of June 2nd - June 6th.If you receive an upcoming maintenance banner in the Helpdesk your account is impacted for this wave.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

On Monday, June 2nd between 14:00 and 15:00 UTC time (0:00am and 1:00am AEST), for up to 60 minutes, customers in our APAC region may experience interruptions or limited availability while we perform maintenance on our infrastructure. This proactive measure is designed to continue improving the reliability, redundancy, and performance across the infrastructure of our services.If you receive an upcoming maintenance banner in the Helpdesk your account is impacted for this wave.

This incident has been resolved.

We have applied mitigations and all impacted features are operating well. All delayed messages have been processed. We will continue to monitor the situation. Again we apologize for any inconvenience this may have caused. Please reach out to support@gorgias.com if you have additional questions.

We are currently experiencing delays in processing within our incoming messages pipeline. This may result in delays for you in receiving messages and minor delays in the processing of AI Agent messages. We're not experiencing any data loss, as messages are buffered. The root cause of this issue is related to issues in our Cloud Provider's infrastructure. Our team is actively working to mitigate the impact and restore normal functionality as quickly as possible. We sincerely apologize for any inconvenience this may cause and appreciate your patience during this time. We will keep you updated on our progress.

This incident has been resolved.

We have applied mitigations and all impacted features are operating well. All delayed messages have been processed. We will continue to monitor the situation.Again we apologize for any inconvenience this may have caused. Please reach out to support@gorgias.com if you have additional questions.

We are currently experiencing delays in processing within our incoming messages pipeline. This may result in delays for you in receiving messages and minor delays in the processing of AI Agent messages. We're not experiencing any data loss, as messages are buffered.The root cause of this issue is related to issues in our Cloud Provider's infrastructure.Our team is actively working to mitigate the impact and restore normal functionality as quickly as possible.We sincerely apologize for any inconvenience this may cause and appreciate your patience during this time. We will keep you updated on our progress.

We are pleased to announce that the mitigation measures applied to address the recent connectivity issues impacting our AI Agent have been successful. Since implementing these changes, we have not observed any further occurrences of these issues. We will continue to monitor the situation closely to ensure ongoing stability and performance. Additionally, we will be conducting further investigations to understand the root cause of the initial connectivity problems and prevent similar incidents in the future. Thank you for your patience and understanding as we worked to resolve this matter. If you have any questions or concerns, please reach out to our support team.

As of May 28, 2025, at 2:09 AM UTC, we have successfully mitigated the connectivity issues impacting our AI Agent features. We are pleased to inform you that all AI Agent functionalities are now operating at full health. The root cause of the disruptions was attributed to third-party networking issues within our hosting provider. We apologize for any inconvenience this may have caused and appreciate your patience as we worked to resolve the issue. We are continuing to actively monitor the situation. Thank you for your understanding, and please feel free to reach out if you have any further questions or concerns at support@gorgias.com

We have identified multiple axes of improvement around AI Agent timeouts and are currently working on their implementation and testing.

We are currently investigating connectivity issues with the AI Agent, which can result in intermittent failures when using the feature.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

We are pleased to announce that the mitigation measures applied to address the recent connectivity issues impacting our AI Agent have been successful. Since implementing these changes, we have not observed any further occurrences of these issues.We will continue to monitor the situation closely to ensure ongoing stability and performance. Additionally, we will be conducting further investigations to understand the root cause of the initial connectivity problems and prevent similar incidents in the future.Thank you for your patience and understanding as we worked to resolve this matter. If you have any questions or concerns, please reach out to our support team.

As of May 28, 2025, at 2:09 AM UTC, we have successfully mitigated the connectivity issues impacting our AI Agent features. We are pleased to inform you that all AI Agent functionalities are now operating at full health.The root cause of the disruptions was attributed to third-party networking issues within our hosting provider. We apologize for any inconvenience this may have caused and appreciate your patience as we worked to resolve the issue.We are continuing to actively monitor the situation.Thank you for your understanding, and please feel free to reach out if you have any further questions or concerns at support@gorgias.com

We have identified multiple axes of improvement around AI Agent timeouts and are currently working on their implementation and testing.

We are currently investigating connectivity issues with the AI Agent, which can result in intermittent failures when using the feature.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

The maintenance event that caused a database node to restart has been addressed. Our maintenance exclusion workaround is in place and is preventing other clusters from restarting unexpectedly. Everything is stable at this time. We will take the necessary steps to ensure this does not happen again in the future.

The unexpected maintenance that triggered a database restart has paused. We have introduced a workaround that should prevent other clusters from undergoing the same issue. Everything appears stable for now. We will post another update if there are any changes or in two hours.

We have found that an unexpected maintenance event caused some of our database nodes to restart. While they were coming back online, the customers assigned to the nodes could not access the service. Our team is keeping a close eye on the system to make sure everything returns to normal. We will share another update within the next 30 minutes or as soon as we confirm full restoration.

Our monitoring systems have detected potential access problems affecting a subset of users. We are actively investigating the root cause and working to restore full service as quickly as possible. We will provide an update within the next 30 minutes or as soon as we have more information.

The maintenance event that caused a database node to restart has been addressed. Our maintenance exclusion workaround is in place and is preventing other clusters from restarting unexpectedly. Everything is stable at this time. We will take the necessary steps to ensure this does not happen again in the future.

The unexpected maintenance that triggered a database restart has paused. We have introduced a workaround that should prevent other clusters from undergoing the same issue. Everything appears stable for now.We will post another update if there are any changes or in two hours.

We have found that an unexpected maintenance event caused some of our database nodes to restart. While they were coming back online, the customers assigned to the nodes could not access the service.Our team is keeping a close eye on the system to make sure everything returns to normal.We will share another update within the next 30 minutes or as soon as we confirm full restoration.

Our monitoring systems have detected potential access problems affecting a subset of users. We are actively investigating the root cause and working to restore full service as quickly as possible.We will provide an update within the next 30 minutes or as soon as we have more information.

Between 5:00 PM and 6:00 PM UTC, a faulty deployment caused a failure in the rules responsible for auto-tagging tickets. As a result, some tickets may not have been auto-tagged as expected. We reverted the deployment to restore normal functionality. We apologize for any disruption this may have caused and appreciate your understanding as we work to maintain a reliable experience.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

We are currently investigating this issue.

## **Incident Post-Mortem: May 14, 2025** ### **Summary** Between May 12 and May 14, 2025, a subset of Gorgias customers experienced an issue where Gorgias did not deliver emails sent or forwarded to specific email addresses to their helpdesks. A configuration change we made disabled our ability to receive emails from certain addresses. We resolved the issue, and no data loss occurred. We successfully recovered and processed all affected emails. ### **What Happened?** In 2019, Gorgias improved the security of customer email addresses by switching from easily guessable addresses \(e.g., [support@yourdomain.gorgias.io](mailto:support@yourdomain.gorgias.io)\) to a more secure, randomized format \(e.g., [123PUY9qcgsABC@emails.gorgias.com](mailto:bPUY9qcgsVdXL@emails.gorgias.com)\). Despite this change, we continued to support the older, customer-specific addresses to maintain a smooth experience for our users. Thanks to a fallback mechanism, our system was able to recognize and connect emails sent to either format. In March 2024, we updated the email setup interface to show the addresses stored in our database, instead of always displaying the new, secure format. On May 12, 2025, we made another change that stopped accepting emails forwarded to addresses not stored in our database. Our pre-change analysis showed that most traffic to these addresses was spam, and we assumed that they were no longer being actively used. Unfortunately, we missed a small number of active accounts that were still relying on these older addresses for email delivery. This led to email disruptions for these accounts. Once we identified this error, we immediately rolled back the change, restored the prior functionality, and re-processed all affected emails, ensuring no data loss. ### **What We Are Doing to Prevent This in the Future** Following an internal review, we have identified several actions to reduce the likelihood of similar incidents: * **Properly Provision Missing Addresses: We have provisioned the email addresses that relied on the fallback search mechanism, so that is no longer required.** * **Improved Monitoring and Alerts:** We will enhance our monitoring systems to detect disruptions in inbound email processing more quickly, minimizing response times. * **Stricter Change Management:** We will refine our internal processes for identifying and flagging potentially breaking changes, ensuring that our customer support teams are better prepared to respond if issues arise. * **Customer Communication and Migration Support:** We will improve our outreach to ensure customers are fully transitioned to the new email format, reducing reliance on legacy systems. We sincerely apologize for any disruption this incident caused to your operations. We know how important email delivery is to you. Providing a reliable, resilient platform is our top priority, and we are committed to learning from this event to prevent future disruptions. Thank you for your continued trust in Gorgias. Sincerely, The Gorgias Team

Between May 12 and May 14, 2025, a subset of Gorgias customers experienced an issue where Gorgias did not deliver emails sent or forwarded to specific email addresses to their helpdesks. A configuration change we made disabled our ability to receive emails from certain addresses. We resolved the issue, and no data loss occurred. We successfully recovered and processed all affected emails.

This incident has been resolved.

BigCommerce is working on a fix for the webhooks. We are going to post an update in the following 2 hours.

BigCommerce have an outage regarding the webhooks: https://status.bigcommerce.com/. The impact is that the widget data is not getting updated for the BigCommerce integrations. All the accounts are affected by this issue. We are following BigCommerce status page and we are going to post an update in the following 2 hours.

This incident has been resolved.

The issue with the billing process for Automate products has been resolved. The redeployment has been completed, and the system has successfully reprocessed all data to accurately calculate usage.

We are continuing to monitor for any further issues.

The billing process for Automate products has been redeployed and is currently reprocessing the data to accurately calculate the actual usage.

The usage reported in the billing page for Automate product is misaligned with the real usage count. We are working on a fix and reconciliation of the data.

We sincerely apologize for the recent interruption you experienced with our Recommender service. Our team identified and addressed the high error rate that occurred earlier today. As of now, the service is fully operational. Thank you for your understanding and patience. We appreciate your continued support.

We have an ongoing incident in our recommendation engine, We are currently investigating this issue. We understand that this is affecting our users operations and we are doing our best to fix this

This incident has been resolved.

We're investigating an internal issue

We are currently investigating this issue.

This incident has been resolved.

Statistics are back online, and we are actively monitoring to ensure stability.

We are currently investigating this issue.

Our Phone provider has resolved this incident and we will continue to monitor status.

Our Phone provider has Identified the issue and is scaling up systems and deployed new hosts in order to ease issues.

Our Phone provider has partial outage and working on a fix. We will post an update in one hour or as soon as the issue has been resolved.

We have raised the issue to our phone provider, and we are following up with them on resolving the issue.

This incident has been resolved.

The following features have degraded performances on Machine Learning related features: - AI agent - Auto QA - Ticket fields

Standard voice integration settings page are operational again.

We have identified the issue and are working on a fix.

We are currently investigating this issue.

During the incident, we experienced increased latency in one of our internal services, leading to higher-than-usual AI Agent handovers. The issue has since been mitigated, and all services are back to normal.

The fix has been applied. All Auto QA scores are processed without any issues. We are still monitoring service.

We have identified the issue. We are currently working on restoring processing Auto QA scores.

We are currently investigating this issue.

This incident has been resolved.

Customer Search is now fully operational and up-to-date with the latest customer data.

We are currently investigating an issue affecting our Customer Search service. The service is experiencing a lag and is not fully updated with the latest customer data from the past two hours.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We identified a display issue with the updates received from Shopify caused by a version change. We have rolled back the change, and all new updates will now correctly include variant quantities. We are actively monitoring the results.

We are aware of the issue and are currently investigating it. We will provide an update as soon as we have more information or, at the latest, within 30 minutes.

We fixed the configuration issue. Everything is back to normal

We are currently investigating this issue. The impact is we hand over more than usual to human agents

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating the issue with our ticket search engine. Ticket search results might be outdated.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating the issue with our customer search engine. Customer search results might be outdated.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

We have identified the source of the problem and we are working on a fix

This incident has been resolved.

Internal latencies are beeing mitigated

We are currently investigating this issue.

This incident has been resolved, and all search features are functioning normally.

We identified the issue. We are solving it now. Time to fully resolve it is approximately 5 hours.

We identified the issue. We are solving it now. Time to fully resolve it is approximately 5 hours.

We are currently investigating this issue.

We are currently addressing an issue with our search capabilities in Gorgias. You may not be able to search for recent customers, products and calls. Our team is investigating and working to resolve the problem promptly.

All data has been processed and statistics are now up-to-date

We are currently investigating this issue.

This incident has been resolved.

We are continuing to work on a fix for this issue.

The incident now appears to be related only to Recharge’s analytics and not to updates, installations, or the API, so it should no longer affect Gorgias. We will continue to monitor the situation closely to ensure no issues arise on our side. For further updates on Recharge analytics and the incident resolution progress, please refer to the Recharge status page: https://status.getrecharge.com/incidents/nxhcq2qx5qz4

Recharge is still undergoing maintenance, with no updates on their side. Our monitors are stable. We are still actively monitoring the situation and will provide another update tomorrow.

Recharge is still undergoing maintenance, and our monitors are still stable. We are still actively monitoring the situation and will provide another update tomorrow.

Recharge is still undergoing maintenance, and our monitors are still stable. The maintenance might affect the performance of our API calls and the live updates we receive from them. We are still actively monitoring the situation and will provide another update tomorrow.

Recharge is still undergoing maintenance, while our monitors are stable. The maintenance might affect the performance of our API calls and the live updates we receive from them. We are actively monitoring the situation and will provide another update within the next four hours.

Recharge is still undergoing maintenance, while our monitors are stable. The maintenance might affect the performance of our API calls and the live updates we receive from them. We are actively monitoring the situation and will provide another update within the next four hours.

Recharge is still undergoing maintenance, while our monitors are stable. The maintenance might affect the performance of our API calls and the live updates we receive from them. We are actively monitoring the situation and will provide another update tomorrow.

Recharge is still undergoing maintenance, although our monitors are showing that everything is back to normal. The maintenance might affect the performance of our API calls and the live updates we receive from them. We are actively monitoring the situation and will provide another update within the next four hours.

Recharge is reporting that the systems are stable. We will continue to monitor the situation and we will have another update in 4 hours at the latest

The status remains unchanged—Recharge is still in maintenance mode and experiencing degraded performance. We are closely monitoring the situation and will provide another update by morning at the latest.

Recharge is still undergoing maintenance, which is affecting the performance of our API calls and the live updates we receive from them. We are actively monitoring the situation and will provide another update within the next four hours.

This incident has been resolved.

We have identified an issue where, in some cases the Help Center doesn't load when embedded on a website.

This incident has been resolved.

Recharge is undergoing a scheduled maintenance during which time Recharge related operations will not function correctly.

Incident Resolution Time: January 22, 2025, 5:52 PM UTC We are pleased to inform you that the incident affecting our email processing and automated features has been resolved. All delayed events have been successfully processed, and systems are now operating normally. We sincerely apologize for any inconvenience this may have caused and appreciate your patience as we worked to rectify the situation. Our team is committed to providing a seamless experience, and we will continue to monitor the situation closely. Thank you for your understanding. If you have any further questions, please don't hesitate to reach out to our Support team at support@gorgias.com.

A fix has been implemented. All delayed events has been processed. We are monitoring the current state.

Incident Start Time: January 22, 2025, 3:50 PM UTC We are currently investigating an incident that has caused delays in several critical features of our services. The following functionalities are affected: - Email Rules: Processing of email rules is delayed, which may impact your ability to manage and organize your inbox efficiently. - AI Agent: The AI Agent is experiencing delays in processing emails, affecting its ability to respond and assist promptly. - Auto-Merge and Auto-QA: There are delays in auto-merging and auto-quality assurance processes, which may result in slower updates and checks. We understand the importance of these features to your workflow and are actively working to resolve the situation. Our team is engaged in diagnosing the root cause of the delays and will provide updates as more information becomes available.

This incident has been resolved. We have discontinued directing sign-ups to https://www.gorgias.com/signup-2 due to issues. All users are now redirected to https://www.gorgias.com/signup, which is functioning correctly.

Users should now be directed to the working signup page at https://gorgias.com/signup/. A workaround has been implemented and we are monitoring the results. Thank you for your patience!

A third-party API disruption is causing issues with https://www.gorgias.com/signup-2. In the meantime, you can still sign up using this link: https://www.gorgias.com/signup. We are actively working on resolving the issue. Thank you for your understanding!

We are currently investigating this issue.

The fix that we applied is effective, the spike of events is gone, and all the systems are back to normal. The incident is now resolved.

A fix has been implemented and we are monitoring the results. It seems that one of our providers, Google, had an issue with dispatching all the events to our system, and that lead to delays in our ecom data, disruptions in chat and voice. Currently we are monitoring if the fix that we applied is fixing the issue

We identified the issue. It seems that we've been flooded by a big number of webhooks, and our system took a long time to respond. Because of this, the ecom data had some delay in getting updated in helpdesk. The ecom, chat and voice have been affected by this issue. Currently, we increased the resources that we allocated, and it seems that the situation is back in control.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

We identified the issue as coming from a change on the Web front component. We invite users to refresh their page to get the latest version of the app which will solve the issues observed with the search and views features.

We are currently investigating this issue.

This incident has been resolved. Customer search results are up- to-date

A fix has been implemented and we are monitoring the results. Customer search still have some delay, but the delay is descreasing.

We have identified the issue. We are working on processing recent data.

We are currently investigating this issue.

This incident has been resolved.

Fixes have been applied and we are monitoring this situation. We are processing a backlog of Shopify integration data for a small subset of customers, with a resolution ETA of 2h. We apologize for any inconvenience this may have caused.

We have identified an issue causing delays in message processing and elevated error rates in our Helpdesk product. We have fully recovered for 80% of affected customers, and are working to recover the remaining subset of traffic. We will provide further updates as soon as they are available.

We are currently investigating this issue. You may not be affected.

Meta resolved the incident on their end. Messages sent and received for Instagram DMs are now properly formatted.

Meta resolved the incident on their end and we are monitoring the results. Messages received from Instagram DM should now contain properly formatted messages.

It appears that Meta API for Instagram is suffering from a widespread outage: https://metastatus.com/ig-messenger Messages displayed within the platform might show technical information coming from Meta. We're monitoring the situation and will continue to update on this matter.

It appears that Messenger API for Instagram is suffering from a widespread outage: https://metastatus.com/ig-messenger This has direct impact to our Instagram integrations that may be not working correctly at this time. We are currently investigating the issue, and will provide further details as they come from Meta.

Meta solved all incidents on their end and the traffic received in Gorgias indicates normal operations.

The issue is still being worked on by the Meta team and traffic is getting back to normal levels, notably for WhatsApp. - Instagram: https://metastatus.com/ig-messenger - Facebook: https://metastatus.com/messenger - Whatsapp: https://metastatus.com/whatsapp-business-api We will provide further updates as the situation evolves or within the next two hours at most.

The issue is still being worked on by the Meta team: - Instagram: https://metastatus.com/ig-messenger - Facebook: https://metastatus.com/messenger - Whatsapp: https://metastatus.com/whatsapp-business-api We will provide further updates as the situation evolves or within the next two hours at most.

Meta is currently experiencing a major outage, and they are investigating the issue: - instagram: https://metastatus.com/ig-messenger - facebook: https://metastatus.com/messenger - whatsapp: https://metastatus.com/whatsapp-business-api We will provide further updates as the situation evolves or within the next two hours at most.

It appears that Meta services (API, Webhooks) are suffering from a widespread outage. This has direct impact to our Meta integrations: Facebook, Instagram and WhatsApp, that may be not working correctly at this time. We are currently investigating the issue, and will provide further details as they come from Meta.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.

OpenAI is experiencing a large outage: https://status.openai.com/incidents/ctrsv3lwd797 Impacted features are AI Agent, AutoQA, and Ticket Intent Detection. We are working on a solution and will provide updates as soon as possible.

The AI Agent stopped processing tickets due to an internal system issue. The issue was resolved quickly, but reactivating the AI Agent on all accounts took some additional time.

This incident has been resolved.

We are currently addressing an issue that affects ticket views. You may not be able to see your latest tickets or the current state of tickets in your views. Our team is investigating and working to resolve the problem promptly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified the issue and are continuing to work on a fix for it.

Our monitoring has detected high CPU usage on one of our PostgreSQL databases within the europe-west3-86c1 cluster. This may impact database performance and cause delays in processing requests. Our team is actively investigating and working to resolve the issue to restore optimal performance. We appreciate your patience and will provide updates as we make progress.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

We have discovered discrepancies in the Automation rate computing, affecting the Automate analytics page. The root cause have been identified and we are working on a fix.