Gainsight Status
Real-time updates of Gainsight issues and outages
Gainsight status is Operational
US1 Rules Engine Queue
US2 Rules Engine Queue
EU Rules Engine Queue
Active Incidents
No active incidents
Recently Resolved Incidents
We have identified that rule failures are occurring due to an ongoing Salesforce (SFDC) incident. Our team is actively monitoring the situation and will provide updates as more information becomes available.
Gainsight Outage Survival Guide
Gainsight Components
Gainsight CS - US1 Region
Gainsight CS US1 Application
US1 Rules Engine Queue
We have identified that rule failures are occurring due to an ongoing Salesforce (SFDC) incident. Our team is actively monitoring the situation and will provide updates as more information becomes available.
US1 Data Processor Queue
US1 Data Ingestion Queue
Gainsight CS - US2 Region
Gainsight CS US2 Application
US2 Rules Engine Queue
We have identified that rule failures are occurring due to an ongoing Salesforce (SFDC) incident. Our team is actively monitoring the situation and will provide updates as more information becomes available.
US2 Data Processor Queue
US2 Data Ingestion Queue
Gainsight CS - EU Region
Gainsight CS EU Application
EU Rules Engine Queue
We have identified that rule failures are occurring due to an ongoing Salesforce (SFDC) incident. Our team is actively monitoring the situation and will provide updates as more information becomes available.
EU Data Processor Queue
EU Data Ingestion Queue
Gainsight Alternatives
Close Application UI
We had an issue with our backend search infrastructure. The issue affected Lead search, Inbox, Opportunities, Leads, and Reporting.
The engineering team deployed a fix, and the items are being reindexed. We are monitoring the situation.
Close API
We had an issue with our backend search infrastructure. The issue affected Lead search, Inbox, Opportunities, Leads, and Reporting.
The engineering team deployed a fix, and the items are being reindexed. We are monitoring the situation.
Web App
We are currently investigating the issue
The problem persists, we are in contact with Meta support and we are trying to resolve the issue. We will have another update in 4 hours at the earliest