Last checked: 19 minutes ago
Get notified about any outages, downtime or incidents for Gainsight and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Gainsight.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Gainsight CS - EU Region | Active |
EU Data Ingestion Queue | Active |
EU Data Processor Queue | Active |
EU Rules Engine Queue | Active |
Gainsight CS EU Application | Active |
Gainsight CS - US1 Region | Active |
Gainsight CS US1 Application | Active |
US1 Data Ingestion Queue | Active |
US1 Data Processor Queue | Active |
US1 Rules Engine Queue | Active |
Gainsight CS - US2 Region | Active |
Gainsight CS US2 Application | Active |
US2 Data Ingestion Queue | Active |
US2 Data Processor Queue | Active |
US2 Rules Engine Queue | Active |
View the latest incidents for Gainsight and check for official updates:
Description: Queues have returned to expected levels.
Status: Resolved
Impact: Minor | Started At: Oct. 3, 2024, 8 p.m.
Description: The issue is resolved. We will share RCA details as they become available.
Status: Resolved
Impact: Minor | Started At: Sept. 4, 2024, 4:16 p.m.
Description: **Incident:** 26th August, 2024: Some customers may have experienced elevated levels of latency while using our CS-US1 application. **Root Cause:** * There was an increased frequency of database calls tied to a recent hotfix. The increased traffic was intermittent but led to slower API response times and thus impacted customer experience from browser. * Customers in CS-US1 may have experienced the latency while browsing. Impact was relatively less for our CS-US2 and CS-EU regions. * Sanity testing in lower environments did not initially produce this issue which was only observed with production traffic in US1. **Recovery Action:** Once the source was identified, a subsequent fix was applied which restored performance to expected levels. **Preventive Measures:** The mentioned fix has resolved this issue. We will continue to review and learn from issues like this in effort to provide the best possible customer experience. Please contact [support@gainsight.com](mailto:support@gainsight.com) if there are any questions.
Status: Postmortem
Impact: Minor | Started At: Aug. 26, 2024, 5:06 p.m.
Description: CS-US1: Some customers may have experienced issues while exporting from Dashboard and Success Snapshot from 13:00 to 18:00 UTC. We restarted related services which resolved this issue. Please email support@gainsight.com with any questions.
Status: Resolved
Impact: Minor | Started At: Aug. 19, 2024, 1 p.m.
Description: **Incident Summary for issue on 28 May 2024 \(External\)** **Gainsight CS - EU - Elevated errors in NXT Authentication** On **2024-05-28** between **07:31 and 08:45 UTC**, users of the Gainsight Application in the CS EU Cloud experienced intermittent application availability issues. The Gainsight UI was inaccessible for approximately 75 minutes during this window. **Root Cause :** Investigations have identified the following cause of the incident: * An infrastructure component, specifically the backend worker service \(Kubernetes Karpenter\), was upgraded to a newer version to patch critical security and other updates. * This change had already been successfully executed in the STAGE and other PROD environments. * During the EU environment upgrade, all metadata configurations were transferred except for one critical rule. * The missing rule allowed for UDP communication to DNS Servers. * Due to the absence of this rule, DNS requests could not be resolved, causing microservices on newly provisioned worker nodes to fail. Microservices on older worker nodes were unaffected. * These failures resulted in a significant number of stale threads/connections in a short time frame, rendering the API Gateway unresponsive. * Updating the missing rule in the Network Security Group and reprovisioning the worker nodes resolved the issue. * Pending rule jobs were either skipped or resubmitted as necessary. **Recovery Action :** 1. Updated the missing UDP rule in the Network Security Group. 2. Restarted all affected services. **Preventive Measures:** 1. Ensure network rules consistency before and after any upgrade – this process has been initiated. 2. Schedule critical security updates and even low-risk infrastructure changes during non-peak hours, despite previous successes in other environments, to minimize impact.
Status: Postmortem
Impact: Major | Started At: May 28, 2024, 6:46 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.