Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Cronologia delle interruzioni di Insided

    54 Insided incidents · maggio 2023 — official updates, affected components, duration and resolution details.

    Torna allo stato attuale

    PHP Vulnerability annunciato - Capacità di carico disabilitate

    Inizio 21 ottobre 2026 alle ore 11:53 UTC · In corso

    Pending
    1. 21 ottobre 2026 alle ore 11:53 UTCidentified

      Come precauzione, abbiamo temporaneamente disabilitato la funzionalità di upload sulla comunità. Durante questo periodo, i membri non saranno in grado di caricare i file, comprese le immagini in linea, gli avatar del profilo e gli allegati di posta. Tutte le altre funzionalità della comunità, compresa la lettura, la pubblicazione e la risposta, non sono influenzate. Non abbiamo visto alcun impatto sui dati dei clienti o sulla disponibilità della comunità. Ci aspettiamo di ripristinare i caricamenti una volta che il nostro lavoro è completo e aggiornerà questa pagina non appena avremo più informazioni.

    2. 21 ottobre 2026 alle ore 12:40 UTCidentified

      Stiamo continuando a monitorare la piattaforma da vicino. La nostra indagine non ha trovato alcuna prova che la questione della sicurezza che stiamo affrontando sia stata sfruttata. Gli upload dei file rimangono temporaneamente disabilitati come precauzione, e stiamo lavorando per ripristinarli il prima possibile. Manterremo questa pagina aggiornata mentre la situazione si evolve.

    3. 21 ottobre 2026 alle ore 13:00 UTCidentified

      Vulnerabilità PHP (PHP2Shell): upload temporaneamente disabilitati Gainsight Customer Communities utilizza PHP. Il 20 ottobre, due vulnerabilità critiche in PHP stesso (CVE-2026-109618 e CVE-2026-109619, noto come PHP2Shell) sono state divulgate prima della correzione ufficiale. Il team di sicurezza PHP sta rilasciando la correzione oggi, 21 ottobre alle 16:00 CEST (14:00 UTC). Quello che abbiamo fatto: Disabilita tutti i file caricati in tutte le comunità, comprese le immagini in linea, gli avatar del profilo e gli allegati post. Mettere ulteriori protezioni firewall in atto contro il tipo di richiesta utilizzata in questi attacchi. Abbiamo esaminato i nostri registri per segni di sfruttamento. Finora, non abbiamo trovato alcuna prova che la vulnerabilità è stata sfruttata sulla nostra piattaforma. Cosa succederà dopo: Applicheremo l'aggiornamento di sicurezza PHP attraverso la nostra infrastruttura EMEA e Stati Uniti non appena sarà rilasciato. Dopo la patch, eseguiremo una recensione completa di compromesso e condividere il risultato qui. Ripristineremo gli upload una volta che la patch viene applicata e verificata. Leggere, postare e rispondere il lavoro come normale. Il nostro prossimo aggiornamento sarà entro le 17:00 CEST, o prima se qualcosa cambia.

    4. 21 ottobre 2026 alle ore 14:07 UTCidentified

      Stiamo continuando a lavorare per risolvere questo problema.

    5. 21 ottobre 2026 alle ore 14:08 UTCidentified

      Aggiornamento: Il team di sicurezza PHP ha rilasciato la correzione. Ora lo stiamo convalidando e lo stiamo testando contro la nostra piattaforma. Lo distribuiremo attraverso la nostra infrastruttura EMEA e USA una volta che il test è completo. Gli upload dei file rimangono temporaneamente disabilitati fino a quando la correzione viene implementata e verificata. Il nostro monitoraggio continua a dimostrare che la vulnerabilità è stata sfruttata sulla nostra piattaforma. La lettura, la pubblicazione e la risposta continuano a funzionare come normale. Il nostro prossimo aggiornamento sarà di 5PM CEST, o prima se qualcosa cambia.

    6. 21 ottobre 2026 alle ore 15:30 UTCidentified

      Aggiornamento: stiamo testando la correzione rilasciata per assicurarci di non introdurre regressioni. Gli upload dei file rimangono temporaneamente disabilitati fino a quando la correzione viene implementata e verificata. Il nostro monitoraggio continua a dimostrare che la vulnerabilità è stata sfruttata sulla nostra piattaforma. La lettura, la pubblicazione e la risposta continuano a funzionare come normale. Il nostro prossimo aggiornamento sarà di 6PM CEST, o prima se qualcosa cambia.

    7. 21 ottobre 2026 alle ore 16:16 UTCidentified

      Aggiornamento: stiamo testando la correzione rilasciata per assicurarci di non introdurre regressioni. Gli upload dei file rimangono temporaneamente disabilitati fino a quando la correzione viene implementata e verificata. Il nostro monitoraggio continua a dimostrare che la vulnerabilità è stata sfruttata sulla nostra piattaforma. La lettura, la pubblicazione e la risposta continuano a funzionare come normale. Il nostro prossimo aggiornamento sarà di 7PM CEST, o prima se qualcosa cambia.

    8. 21 ottobre 2026 alle ore 18: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. 21 ottobre 2026 alle ore 18: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. 22 ottobre 2026 alle ore 06: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. 22 ottobre 2026 alle ore 08: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. 22 ottobre 2026 alle ore 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. 22 ottobre 2026 alle ore 14: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. 22 ottobre 2026 alle ore 18: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. 22 ottobre 2026 alle ore 20: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. 23 ottobre 2026 alle ore 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. 23 ottobre 2026 alle ore 19: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. 26 ottobre 2026 alle ore 04:39 UTCmonitoring

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

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    [Comunità UE e USA] Elevato errore 500 e 504 errori durante l'accesso

    Inizio 29 settembre 2026 alle ore 11:05 UTC · 1h 30m

    OutageIncidente maggiore
    Componenti interessati
    Status of our EMEA Community InfrastructureStatus of our US Community Infrastructure
    1. 29 settembre 2026 alle ore 11:05 UTCidentified

      Il problema è stato identificato e si sta attuando una correzione.

    2. 29 settembre 2026 alle ore 11:28 UTCmonitoring

      Una soluzione è stata implementata e stiamo monitorando i risultati.

    3. 29 settembre 2026 alle ore 12:35 UTCresolved

      Questo incidente è stato risolto - ci scusiamo sinceramente per questa interruzione alla piattaforma e noi caricare un documento RCA qui quando completato.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Stati Uniti - Panoramica utente lenta per aggiornare

    Inizio 24 agosto 2026 alle ore 07:35 UTC · 1d 5h

    IssuesIncidente minore
    Componenti interessati
    User Overview
    1. 24 agosto 2026 alle ore 07:35 UTCinvestigating

      Stiamo attualmente indagando su questo problema - la panoramica degli utenti per le comunità degli Stati Uniti sta prendendo più tempo del solito per visualizzare nuovi utenti, questa lentezza si verifica anche sui widget di controllo homepage.

    2. 25 agosto 2026 alle ore 13:21 UTCresolved

      Questo incidente è stato risolto.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    [EU + US communities] Topics failing to load

    Inizio 4 agosto 2026 alle ore 07:57 UTC · 3h 30m

    OutageIncidente critico
    Componenti interessati
    Status of our EMEA Community InfrastructureStatus of our US Community Infrastructure
    1. 4 agosto 2026 alle ore 07: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. 4 agosto 2026 alle ore 08:08 UTCmonitoring

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

    3. 4 agosto 2026 alle ore 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.

    Intermittent timeouts and slowness are identified in our EU communities

    Inizio 8 luglio 2026 alle ore 09:45 UTC · 2h 9m

    OutageIncidente critico
    Componenti interessati
    Status of our EMEA Community Infrastructure
    1. 8 luglio 2026 alle ore 09: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. 8 luglio 2026 alle ore 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.

    Investigating AI Answers / AI Summary Services

    Inizio 2 luglio 2026 alle ore 17:28 UTC · 2h 7m

    Pending
    Componenti interessati
    Community SearchSearch Functionality
    1. 2 luglio 2026 alle ore 17: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. 2 luglio 2026 alle ore 19: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.

    Events Module Unavailable for US Communities

    Inizio 29 maggio 2026 alle ore 19:21 UTC · 24m

    OutageIncidente critico
    Componenti interessati
    Events Module
    1. 29 maggio 2026 alle ore 19: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. 29 maggio 2026 alle ore 19: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]

    Salesforce Connection Failure

    Inizio 21 novembre 2025 alle ore 12:47 UTC · 117d 3h

    IssuesIncidente minore
    Componenti interessati
    Salesforce IntegrationSalesforce Integration
    1. 21 novembre 2025 alle ore 12:47 UTCinvestigating

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

    2. 21 novembre 2025 alle ore 14: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. 22 novembre 2025 alle ore 02: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. 22 novembre 2025 alle ore 19: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. 22 novembre 2025 alle ore 19:48 UTCidentified

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

    6. 2 dicembre 2025 alle ore 17: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. 13 dicembre 2025 alle ore 22: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. 18 marzo 2026 alle ore 16:35 UTCresolved

      This incident has been resolved.

    Issue with content creation and edits

    Inizio 17 novembre 2025 alle ore 09:07 UTC · 4h 42m

    OutageIncidente maggiore
    Componenti interessati
    Status of our EMEA Community InfrastructureStatus of our US Community Infrastructure
    1. 17 novembre 2025 alle ore 09: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. 17 novembre 2025 alle ore 12:03 UTCidentified

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

    3. 17 novembre 2025 alle ore 12:20 UTCmonitoring

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

    4. 17 novembre 2025 alle ore 13: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.

    Custom community pages may not load properly

    Inizio 10 novembre 2025 alle ore 18:38 UTC · 5h 16m

    IssuesIncidente minore
    Componenti interessati
    Status of our EMEA Community InfrastructureStatus of our US Community Infrastructure
    1. 10 novembre 2025 alle ore 18:38 UTCinvestigating

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

    2. 10 novembre 2025 alle ore 20:15 UTCidentified

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

    3. 10 novembre 2025 alle ore 21: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. 10 novembre 2025 alle ore 22:19 UTCidentified

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

    5. 10 novembre 2025 alle ore 23:54 UTCresolved

      This incident has been resolved.

    Embedded Media Not Working

    Inizio 6 ottobre 2025 alle ore 15:18 UTC · 4h 37m

    IssuesIncidente minore
    Componenti interessati
    Text EditorText Editor
    1. 6 ottobre 2025 alle ore 15: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. 6 ottobre 2025 alle ore 19:25 UTCmonitoring

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

    3. 6 ottobre 2025 alle ore 19:55 UTCresolved

      This incident has been resolved.

    Embedded media (e.g., Vimeo videos) is currently not working across communities

    Inizio 26 settembre 2025 alle ore 08:32 UTC · 1h 39m

    IssuesIncidente minore
    Componenti interessati
    Text EditorText Editor
    1. 26 settembre 2025 alle ore 08: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. 26 settembre 2025 alle ore 10:12 UTCresolved

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

    US region degraded performance

    Inizio 3 settembre 2025 alle ore 16:49 UTC · 4h 7m

    IssuesIncidente minore
    Componenti interessati
    Status of our US Community Infrastructure
    1. 3 settembre 2025 alle ore 16: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. 3 settembre 2025 alle ore 17:43 UTCidentified

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

    3. 3 settembre 2025 alle ore 17:44 UTCidentified

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

    4. 3 settembre 2025 alle ore 17:44 UTCmonitoring

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

    5. 3 settembre 2025 alle ore 20:56 UTCresolved

      This incident has been resolved.

    [EU + US communities] Issues with Linkedin + Facebook Login

    Inizio 29 agosto 2025 alle ore 08:48 UTC · 2h 42m

    OutageIncidente maggiore
    Componenti interessati
    Single Sign On (SSO)Single Sign On (SSO)
    1. 29 agosto 2025 alle ore 08: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. 29 agosto 2025 alle ore 10:36 UTCmonitoring

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

    3. 29 agosto 2025 alle ore 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.

    EU + US Communities - Elevated error rates on topic load

    Inizio 6 agosto 2025 alle ore 14:05 UTC · 3h 22m

    OutageIncidente maggiore
    Componenti interessati
    Status of our EMEA Community InfrastructureStatus of our US Community Infrastructure
    1. 6 agosto 2025 alle ore 14: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. 6 agosto 2025 alle ore 14:24 UTCidentified

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

    3. 6 agosto 2025 alle ore 15:33 UTCmonitoring

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

    4. 6 agosto 2025 alle ore 17:28 UTCresolved

      This incident has been resolved.

    Community Pages Not Loading Properly

    Inizio 28 luglio 2025 alle ore 17:29 UTC · 3h 55m

    OutageIncidente maggiore
    Componenti interessati
    Status of our EMEA Community InfrastructureStatus of our US Community Infrastructure
    1. 28 luglio 2025 alle ore 17: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. 28 luglio 2025 alle ore 21:24 UTCresolved

      This incident has been resolved.

    Issues with Third Party Scripts due to Front End performance improvements

    Inizio 24 luglio 2025 alle ore 07:00 UTC · 0m

    Pending
    1. 11 agosto 2025 alle ore 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.

    EU Communities - elevated error rate

    Inizio 15 luglio 2025 alle ore 15:14 UTC · 20m

    OutageIncidente maggiore
    Componenti interessati
    Status of our EMEA Community Infrastructure
    1. 15 luglio 2025 alle ore 15: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. 15 luglio 2025 alle ore 15:24 UTCidentified

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

    3. 15 luglio 2025 alle ore 15: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.

    SSO Login issues

    Inizio 27 giugno 2025 alle ore 07:26 UTC · 2h 13m

    OutageIncidente maggiore
    Componenti interessati
    Status of our EMEA Community InfrastructureStatus of our US Community Infrastructure
    1. 27 giugno 2025 alle ore 07:26 UTCinvestigating

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

    2. 27 giugno 2025 alle ore 07:42 UTCidentified

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

    3. 27 giugno 2025 alle ore 08:08 UTCmonitoring

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

    4. 27 giugno 2025 alle ore 09: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].

    US Communities - Currently experiencing issues with community loading

    Inizio 13 giugno 2025 alle ore 15:19 UTC · 4h 44m

    OutageIncidente maggiore
    Componenti interessati
    Status of our US Community Infrastructure
    1. 13 giugno 2025 alle ore 15:19 UTCinvestigating

      We are currently investigating this issue.

    2. 13 giugno 2025 alle ore 15: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. 13 giugno 2025 alle ore 16: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. 13 giugno 2025 alle ore 17:37 UTCinvestigating

      We are continuing to investigate this issue.

    5. 13 giugno 2025 alle ore 18:11 UTCinvestigating

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

    6. 13 giugno 2025 alle ore 18:44 UTCinvestigating

      Users may experience degraded performance in some areas.

    7. 13 giugno 2025 alle ore 18:56 UTCidentified

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

    8. 13 giugno 2025 alle ore 19:05 UTCmonitoring

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

    9. 13 giugno 2025 alle ore 20:03 UTCresolved

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

    10. 19 giugno 2025 alle ore 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]).