Insided 장애 기록

1. 2026년 10월 21일 오전 11:53 UTCidentified

   우선권으로, 우리는 일시적으로 지역 사회에 업로드 기능. 이 시간 동안 회원은 인라인 이미지, 프로필 아바타 및 포스트 첨부 파일을 포함하여 파일을 업로드 할 수 없습니다. 다른 모든 지역 기능, 읽기, 게시물, 그리고 회신을 포함 하 여, unaffected. 우리는 고객 데이터 또는 커뮤니티 가용성에 영향을 미치지 않습니다. 우리는 한 번 업로드를 복원 할 것으로 예상됩니다. 우리의 작업이 완료되면이 페이지를 곧 업데이트합니다.

2. 2026년 10월 21일 오후 12:40 UTCidentified

   우리는 플랫폼을 밀접하게 감시하고 있습니다. 우리의 조사는 우리가 주소록이 악화 된 보안 문제가 없다는 증거가 없습니다. 파일 업로드는 일시적으로 사전으로 비활성화 유지, 우리는 가능한 한 빨리 복원 작업. 우리는이 페이지를 계속 상황을 진화.

3. 2026년 10월 21일 오후 1:00 UTCidentified

   PHP 취약점 (PHP2Shell): 일시적으로 사용 가능 Gainsight 고객 커뮤니티는 PHP를 사용합니다. 10 월 20 일, PHP 자체의 두 가지 중요한 취약점 (CVE-2026-109618 및 CVE-2026-109619, PHP2Shell로 알려진) 공식 수정 앞서 공개되었습니다. PHP 보안 팀은 오늘 수정, 10 월 21, at 16:00 CEST (14:00 UTC)을 해제합니다. 우리가 하는 일: 모든 파일이 인라인 이미지, 프로필 avatars 및 게시물 첨부 파일을 포함한 모든 커뮤니티에서 업로드를 해제 할 수 있습니다. 이 공격에 사용되는 요청의 유형에 대해 추가 방화벽 보호를 넣어. 악용의 징후에 대한 우리의 로그를 검토. 지금까지, 우리는 취약점이 우리의 플랫폼에 악화되지 않았습니다. 다음 것: 우리는 EMEA와 미국 인프라를 통해 PHP 보안 업데이트를 곧 출시 될 예정입니다. 패치 후, 우리는 전체 손상 검토를 실행하고 여기에 결과를 공유 할 것입니다. 패치가 적용되고 확인되면 업로드를 복원합니다. 정상적인 작업, 게시 및 회신. 다음 업데이트는 17 : 00 CEST, 또는 모든 변경 사항이 변경되면 더 빨리됩니다.

4. 2026년 10월 21일 오후 2:07 UTCidentified

   이 문제를 해결하기 위해 계속 노력하고 있습니다.

5. 2026년 10월 21일 오후 2:08 UTCidentified

   업데이트 : PHP 보안 팀은 수정을 발표했다. 우리는 지금 그것을 검증하고 우리의 플랫폼에 대한 테스트입니다. 우리는 EMEA와 US 인프라를 한 번 테스트하면 완료됩니다. 파일 업로드는 수정이 배포되고 확인 될 때까지 일시적으로 비활성화됩니다. 우리의 모니터링은 취약점이 우리의 플랫폼에 악용되지 않은 증거를 보여줍니다. 읽기, 게시 및 답변은 정상으로 계속 작동합니다. 다음 업데이트는 5PM CEST 또는 모든 변경 사항이 있으면 더 빨리됩니다.

6. 2026년 10월 21일 오후 3:30 UTCidentified

   업데이트 : 우리는 우리가 어떤 회귀를 소개하지 않는 것을 보장하기 위해 출시 된 수정을 테스트하고 있습니다. 파일 업로드는 수정이 배포되고 확인 될 때까지 일시적으로 비활성화됩니다. 우리의 모니터링은 취약점이 우리의 플랫폼에 악용되지 않은 증거를 보여줍니다. 읽기, 게시 및 답변은 정상으로 계속 작동합니다. 다음 업데이트는 6PM CEST 또는 모든 변경 사항이 있으면 더 빨리됩니다.

7. 2026년 10월 21일 오후 4:16 UTCidentified

   업데이트 : 우리는 우리가 어떤 회귀를 소개하지 않는 것을 보장하기 위해 출시 된 수정을 테스트하고 있습니다. 파일 업로드는 수정이 배포되고 확인 될 때까지 일시적으로 비활성화됩니다. 우리의 모니터링은 취약점이 우리의 플랫폼에 악용되지 않은 증거를 보여줍니다. 읽기, 게시 및 답변은 정상으로 계속 작동합니다. 다음 업데이트는 7PM CEST 또는 모든 변경 사항이 있으면 더 빨리됩니다.

8. 2026년 10월 21일 오후 6:18 UTCidentified

   Update: We are completing the testing in staging before deploying to production. File uploads remain temporarily disabled until the fix is deployed and verified. Our monitoring continues to show no evidence that the vulnerability was exploited on our platform. Reading, posting and replying continue to work as normal. Our next update will be by 8:30PM CEST, or sooner if anything changes.

9. 2026년 10월 21일 오후 6:53 UTCmonitoring

   Update: The PHP security fix has been deployed to production and we are continuing to monitor closely. We have found no evidence that the vulnerability was exploited on our platform. File uploads remain temporarily disabled out of an abundance of caution. Reading, posting and replying work as normal. Next update by 08:00AM CEST, or sooner if anything changes.

10. 2026년 10월 22일 오전 6:12 UTCmonitoring

    Update: We are continuing to monitor and have found no evidence that the vulnerability was exploited on our platform. File uploads remain temporarily disabled out of an abundance of caution. Reading, posting and replying work as normal. Next update by 10:00AM CEST, or sooner if anything changes.

11. 2026년 10월 22일 오전 8:17 UTCmonitoring

    Update: We are continuing to monitor and have found no evidence that the vulnerability was exploited on our platform. File uploads remain temporarily disabled out of an abundance of caution. Reading, posting and replying work as normal. Next update by 12:00PM CEST, or sooner if anything changes.

12. 2026년 10월 22일 오전 11:19 UTCmonitoring

    Update: We are continuing to monitor and have found no evidence that the vulnerability was exploited on our platform. File uploads remain temporarily disabled out of an abundance of caution. Reading, posting and replying work as normal. Next update by 3:00PM CEST, or sooner if anything changes.

13. 2026년 10월 22일 오후 2:18 UTCmonitoring

    Update: We are continuing to monitor and have found no evidence that the vulnerability was exploited on our platform. File uploads remain temporarily disabled out of an abundance of caution. Reading, posting and replying work as normal. Next update by 6:00PM CEST, or sooner if anything changes.

14. 2026년 10월 22일 오후 6:43 UTCmonitoring

    Update: We are continuing to monitor and have found no evidence that the vulnerability was exploited on our platform. File uploads that render in the page remain temporarily disabled out of an abundance of caution. Reading, posting and replying work as normal. Attachments of files pdf, zip, txt is again possible. Next update by 10:00PM CEST, or sooner if anything changes.

15. 2026년 10월 22일 오후 8:02 UTCmonitoring

    Update: We are continuing to monitor and have found no evidence that the vulnerability was exploited on our platform. File uploads that render in the page remain temporarily disabled out of an abundance of caution. Reading, posting and replying work as normal. Attachments of files pdf, zip, txt is again possible. Next update by 10:00AM CEST, or sooner if anything changes.

16. 2026년 10월 23일 오전 11:13 UTCmonitoring

    Update: We are continuing to monitor and have found no evidence that the vulnerability was exploited on our platform. Image file uploads that render in the page remain temporarily disabled out of an abundance of caution. Reading, posting and replying work as normal. We will have an update on restoring image file uploads by end of day. Attachments of files pdf, zip, txt is again possible. Next update by 6:00PM CEST, or sooner if anything changes.

17. 2026년 10월 23일 오후 7:44 UTCmonitoring

    Update: We are continuing to monitor and have found no evidence that the vulnerability was exploited on our platform. Image file uploads that render in the page remain temporarily disabled out of an abundance of caution. Reading, posting and replying work as normal. We have started reworking the concerned services to ensure we can restore image uploads as fast as possible. We will have a firm ETA by 25 Sunday 12pm CET Attachments of files pdf, zip, txt is again possible. Next update by 12:00PM CEST, or sooner if anything changes.

18. 2026년 10월 26일 오전 4:39 UTCmonitoring

    Uploads restored: Uploads are available again in all Gainsight Customer Communities. No action is needed. We will continue to monitor closely.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 29일 오전 11:05 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

2. 2026년 9월 29일 오전 11:28 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 9월 29일 오후 12:35 UTCresolved

   이 사건은 해결되었습니다 - 우리는 플랫폼에 이 붕괴를 위해 진심으로 사과하고 여기에 RCA 문서를 업로드 할 것입니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 24일 오전 7:35 UTCinvestigating

   우리는 현재이 문제를 조사하고있다 - 미국 커뮤니티에 대한 사용자 개요는 새로운 사용자를 표시하기 위해 평소보다 오래 걸릴, 이 느린 제어 홈페이지 위젯에 발생할 수 있습니다.

2. 2026년 8월 25일 오후 1:21 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 4일 오전 7:57 UTCinvestigating

   We are currently investigating an issue with topics not loading correctly, we will update this page asap with more information once known.

2. 2026년 8월 4일 오전 8:08 UTCmonitoring

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

3. 2026년 8월 4일 오전 11:27 UTCresolved

   This issue has been resolved - time of the incident (CEST) 9:33am - 10:00am; a 27 minute period in which most topics were returning a 404 error page instead of the topic. It was caused by an unexpected side affect of a downstream change to one of our platform security mechanisms, we apologise for this temporary disruption.

1. 2026년 7월 8일 오전 9:45 UTCidentified

   Intermittent timeouts and slowness are identified in our EU communities. We identified the issue and are mitigating it. We will follow up and update this page as soon as we have more information.

2. 2026년 7월 8일 오전 11:54 UTCresolved

   We have traced the root cause of the recent downtime to an AWS hardware failure. We apologize for the inconvenience this caused. Our team is already putting structural measures in place to ensure that similar hardware issues will not impact our platform going forward.

1. 2026년 7월 2일 오후 5:28 UTCinvestigating

   We are currently investigating an issue affecting AI Summary features, which may result in unexpected or incomplete responses. Search results are not impacted.

2. 2026년 7월 2일 오후 7:34 UTCresolved

   The issue affecting AI Summary features has been successfully resolved, and normal functionality has been fully restored. Thank you for your patience while we worked to fix this.

1. 2026년 5월 29일 오후 7:21 UTCinvestigating

   We are currently investigating reports that the Events module is not working or failing to load for users within our US communities. Our engineering team is looking into the root cause, and we will provide an update within the next 30 minutes. We apologize for the inconvenience and appreciate your patience while we work to resolve this.

2. 2026년 5월 29일 오후 7:45 UTCresolved

   The issue affecting the Events module in US communities has been fully resolved, and normal functionality has been restored. We appreciate your patience and apologize for any disruption this caused to your workflow. If you continue to experience any issues, please reach out to our support team at [email protected]

1. 2025년 11월 21일 오후 12:47 UTCinvestigating

   We are investigating reports of Salesforce Connection failures and we will update here as soon as we have more details.

2. 2025년 11월 21일 오후 2:01 UTCidentified

   This issue has been tied to the temporary revocation of Salesforce authentication credentials by Salesforce - we are working on getting these reinstated asap, no community data should be lost and events can be replayed again on our side to fill in the gaps once the authentication credentials have been reinstated.

3. 2025년 11월 22일 오전 2:57 UTCidentified

   Work is ongoing to get Salesforce authentication reinstated. No community data should be lost and events can be replayed again on our side to fill in the gaps once the authentication credentials have been reinstated.

4. 2025년 11월 22일 오후 7:36 UTCidentified

   The Salesforce and Gainsight incident remains ongoing. Our teams are actively working to resolve the issue and restore functionality as quickly and safely as possible. For the latest updates and FAQs, please visit the main status page: https://status.gainsight.com/incidents/gvng0kly8vwf

5. 2025년 11월 22일 오후 7:48 UTCidentified

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

6. 2025년 12월 2일 오후 5:42 UTCidentified

   The Salesforce and Gainsight incident remains ongoing. Rest assured our teams are working around the clock to resolve the issue and restore functionality as quickly and safely as possible. In the meantime, we are preparing a workaround and steps to re-enable services. For the latest updates and FAQs, please visit the main status page: https://status.gainsight.com/incidents/gvng0kly8vwf

7. 2025년 12월 13일 오후 10:43 UTCmonitoring

   The Gainsight CC<>Salesforce integration has now been re-enabled and customers can proceed with re-authenticating their connection. To restore full functionality, please follow the step-by-step reconnection guide available here: https://communities.gainsight.com/customer-communities-cc-17/communities-salesforce-integration-restoration-guide-29962

8. 2026년 3월 18일 오후 4:35 UTCresolved

   This incident has been resolved.

1. 2025년 11월 17일 오전 9:07 UTCinvestigating

   We are currently investigating an issue on some communities where content cannot be created or edited; either via the control administration area or sometimes from within the community destination pages.

2. 2025년 11월 17일 오후 12:03 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2025년 11월 17일 오후 12:20 UTCmonitoring

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

4. 2025년 11월 17일 오후 1:49 UTCresolved

   This issue has been resolved - we traced the source of the issue to some database indexes that were lost when a subsequent database update wiped out these indexes. We estimate that only around 10% of customers had this issue happen to their community and the problem was certainly not widespread. Any left over issues please contact [email protected] and we apologies for any inconvenience caused by this.

1. 2025년 11월 10일 오후 6:38 UTCinvestigating

   We’re investigating an issue where custom community pages may not load correctly.

2. 2025년 11월 10일 오후 8:15 UTCidentified

   Our engineering team has identified the root cause and is actively working on a fix.

3. 2025년 11월 10일 오후 9:08 UTCidentified

   We have applied the initial fix which resolves this issue for the majority of customers. We are actively working on a fix that continues to impact custom pages for less than 1% of CC customers.

4. 2025년 11월 10일 오후 10:19 UTCidentified

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

5. 2025년 11월 10일 오후 11:54 UTCresolved

   This incident has been resolved.

1. 2025년 10월 6일 오후 3:18 UTCidentified

   Embedded media is currently not working for some video providers (e.g., Vimeo, Twitter, Vidyard, etc.). YouTube embeds remain unaffected and continue to work as expected. We’ve identified the root cause of the issue, and our engineering team is actively working on a fix. We’ll share an update as soon as the resolution is deployed.

2. 2025년 10월 6일 오후 7:25 UTCmonitoring

   The fix was deployed, we are now monitoring this issue.

3. 2025년 10월 6일 오후 7:55 UTCresolved

   This incident has been resolved.

1. 2025년 9월 26일 오전 8:32 UTCinvestigating

   Embedded media (e.g., Vimeo videos) is currently not working across communities. Users may see “Media not available” when trying to play embedded videos. Our engineering team is actively investigating the issue and working on a fix.

2. 2025년 9월 26일 오전 10:12 UTCresolved

   The incident affecting embedded media has been resolved. Embedded videos should now display correctly across all affected communities.

1. 2025년 9월 3일 오후 4:49 UTCidentified

   We identified a degraded performance especially on the homepages of our US communities. The investigation is ongoing into what is the root cause to this.

2. 2025년 9월 3일 오후 5:43 UTCidentified

   The root cause was identified, and the performance is back to expected performance. We will continue monitoring this incident.

3. 2025년 9월 3일 오후 5:44 UTCidentified

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

4. 2025년 9월 3일 오후 5:44 UTCmonitoring

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

5. 2025년 9월 3일 오후 8:56 UTCresolved

   This incident has been resolved.

1. 2025년 8월 29일 오전 8:48 UTCidentified

   We have identified an issue with LinkedIn and Facebook login functionality - it can be temporarily mitigated by adding a new 'Authorized redirect URL for your app', adding a http version of the url e.g: http://[yourcommunityurl.com]/sso/return. We are working on a full fix for this now though and will update this page with more information once available. Please note that this issue will not affect normal SSO logins / registrations which continue to function normally.

2. 2025년 8월 29일 오전 10:36 UTCmonitoring

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

3. 2025년 8월 29일 오전 11:30 UTCresolved

   This incident has been resolved and both Linkedin and Facebook logins are back to normal, we sincerely apologise for the disruption caused by this.

1. 2025년 8월 6일 오후 2:05 UTCinvestigating

   We are investigating an issue where topics are not loading and and error page is shown, it seems to be affecting Articles and Product Updates.

2. 2025년 8월 6일 오후 2:24 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2025년 8월 6일 오후 3:33 UTCmonitoring

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

4. 2025년 8월 6일 오후 5:28 UTCresolved

   This incident has been resolved.

1. 2025년 7월 28일 오후 5:29 UTCidentified

   We’re currently experiencing an issue where community pages are not loading correctly. Our engineering team has identified the root cause and is actively working on a fix. We’re aiming to restore full functionality as soon as possible and will share updates here as progress is made. Thank you for your patience and understanding.

2. 2025년 7월 28일 오후 9:24 UTCresolved

   This incident has been resolved.

1. 2025년 8월 11일 오전 10:21 UTCresolved

   Incident Summary: On 24 July 2025, we deployed a performance improvement designed to speed up page loading by changing when certain parts of our application load in the browser. As a result of this change, some page elements loaded later than before. Certain third party scripts used by customers depended on those elements being available straight away, so those scripts failed to run correctly. This caused integration errors and broken functionality for affected customers. Impact: Seven customers experienced issues with their integrations. In these cases, third party scripts could not access the expected page elements, which led to errors and features not working as intended. Timeline: - 24 July 2025 9:00 AM (CET) - Deployment completed with new loading behaviour as part of performance improvements. - 25 July 2025 - First customer reports of integration issues received. An internal investigation began to identify the cause. - 26 to 29 July 2025 - Investigation confirmed that lazy loading of certain elements meant they were not available when customer scripts ran. Compatibility checks were carried out to assess possible fixes and confirm the scope of the impact. - 30 July 2025 15:30 AM (CET) - Decision made to revert the change to restore the original loading behaviour. Reversion deployed to production. Monitoring confirmed resolution for all affected accounts. Impacted customers were contacted and confirmed the issue was resolved. Resolution: We rolled back the performance change so that all elements load as they did before. This restored the expected functionality for all affected customers. Mitigation and Next Steps: - Implement a compatibility aware rollout strategy for future performance changes. - Conduct an audit of existing third party scripts to identify other potential compatibility risks. - Include broader customer impact reviews before releasing performance optimisations. - Give customers and support teams more notice of significant changes that may affect integrations. Lessons Learned: There are a wide range of third party scripts in use across all customer instances, and changes to page performance can have unintended side effects. Future performance updates will be introduced in phased rollouts with additional compatibility checks, and customer impact will be reviewed more thoroughly before release.

1. 2025년 7월 15일 오후 3:14 UTCinvestigating

   We are currently investing an issue with an elevated error rate (15-20%) affecting EU communities, we will update here once more information is available.

2. 2025년 7월 15일 오후 3:24 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2025년 7월 15일 오후 3:34 UTCresolved

   This issue has been resolved and the platform is stable again. Any more follow up issues please contact [email protected] - apologies for this short disruption.

1. 2025년 6월 27일 오전 7:26 UTCinvestigating

   We are currently investigating an issue with SSO logins leading to an error 500 page after login.

2. 2025년 6월 27일 오전 7:42 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2025년 6월 27일 오전 8:08 UTCmonitoring

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

4. 2025년 6월 27일 오전 9:39 UTCresolved

   This incident has been resolved - we sincerely apologise for the disruption caused by this, any more issues or questions please email [email protected].

1. 2025년 6월 13일 오후 3:19 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 6월 13일 오후 3:45 UTCinvestigating

   We are continuing to investigate this issue - we have identified a couple of infrastructure issues thought to be causing this. We appreciate your continued patience,

3. 2025년 6월 13일 오후 4:46 UTCinvestigating

   We are continuing to investigate the source of the problem, and have identified a few possibilities for it. As soon as we know more information we will post it here asap.

4. 2025년 6월 13일 오후 5:37 UTCinvestigating

   We are continuing to investigate this issue.

5. 2025년 6월 13일 오후 6:11 UTCinvestigating

   User experience is improving at this time but we are still investigating.

6. 2025년 6월 13일 오후 6:44 UTCinvestigating

   Users may experience degraded performance in some areas.

7. 2025년 6월 13일 오후 6:56 UTCidentified

   The issue has been identified, and a fix was deployed. Performance is steadily improving.

8. 2025년 6월 13일 오후 7:05 UTCmonitoring

   We are monitoring the results of our fix, and performance is back to normal.

9. 2025년 6월 13일 오후 8:03 UTCresolved

   This incident has been resolved. Details will be added once available.

10. 2025년 6월 19일 오전 10:58 UTCpostmortem

    **Redis Cache Degradation and Service Impact - June 13, 2025** ### **Overview** On **June 13, 2025**, from **17:09 to 21:13 CET**, some of our services in the **US region** experienced significant disruptions due to a cascading infrastructure failure. The issue began with degraded performance in our Redis caching layer, triggered by underlying **AWS infrastructure instability**, and ultimately led to elevated error rates and service outages across several systems. ‌ ### **What Happened** A sudden degradation in our Redis cache - likely caused by transient **network issues within AWS infrastructure** - resulted in dramatically slower response times and dropped connections. As Redis became unavailable, systems attempted to query the main database directly, which caused that database to hit its connection limits and become overloaded. This caused broader performance issues across multiple services. ### **Customer Impact** * **High error rates** \(HTTP 5XX\) across several services in the US region * **Slower API response times** and degraded system performance * **Stale or delayed data** due to failed or missed caching * **Up to 4 hours of partial or full service disruption** * **No customer data was lost**, but availability and performance were impacted ### **Timeline of Events \(CEST\)** * **17:09** - Error rates spike and initial alarms trigger * **17:13** - Incident response begins * **17:30-19:00** - Teams work to stabilise the system, including service rollbacks and traffic load reduction * **18:38** - AWS confirms a related infrastructure/network event affecting Redis connectivity * **19:30** - Redis instance upgraded to a higher-capacity configuration * **21:10** - Services fully recover * **21:13** - Incident officially resolved ### **What Caused the Issue?** Our Redis cache experienced performance degradation and stopped serving traffic effectively. Based on internal logs and external confirmations, this was **likely due to transient network and infrastructure issues within AWS**, which impacted bandwidth and connection handling for Redis. As a result, traffic was redirected to the main database, which then became overloaded, creating a cascading service failure. ### **How Was It Resolved?** * Redis was scaled up to handle more traffic and recover performance * Non-essential services were temporarily paused to reduce system load * Once Redis recovered, database pressure eased and systems began returning to normal ### **Could This Have Been Prevented?** Partially. Some safeguards helped limit impact \(such as CDN caching for guest users\), but earlier detection of Redis degradation and better isolation between cache and core systems could have reduced downtime. The unexpected AWS infrastructure event contributed significantly to the incident’s scope. ‌ ### **Key Lessons and Next Steps** * **Improve monitoring and alerting** for Redis resource exhaustion and network saturation * **Isolate caching infrastructure** by service or use case to prevent single points of failure * **Enhance fallback logic** to reduce stress on primary databases when caching layers fail * **Work closely with AWS** to better understand and mitigate infrastructure-related disruptions * **Explore more resilient multi-layer caching strategies** to handle future spikes gracefully We sincerely apologise for the disruption and appreciate your patience. We are taking meaningful steps to strengthen our infrastructure and improve our detection and response capabilities to prevent similar events in the future. For any more information or issues please email [[email protected]](mailto:[email protected]).