- Detected by Pingoru
- Jun 01, 2026, 02:30 PM UTC
- Resolved
- Jun 01, 2026, 09:06 PM UTC
- Duration
- 6h 35m
Affected: Sisense Managed Service
Timeline · 4 updates
-
investigating Jun 01, 2026, 02:30 PM UTC
Unfortunately, an ongoing incident with an upstream provider (Red Hat / Quay.io) has degraded again, affecting container registry push/pull operations (https://status.redhat.com/incidents/jn6r256zc62c). As a precaution, customers may experience intermittent slowness or delays with some Sisense services that depend on this provider. We are actively monitoring the situation and assessing any potential impact to our platform.
-
monitoring Jun 01, 2026, 04:44 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jun 01, 2026, 05:01 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 01, 2026, 09:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 10:16 AM UTC
- Resolved
- Jun 01, 2026, 10:54 AM UTC
- Duration
- 37m
Affected: Sisense Managed Service
Timeline · 3 updates
-
investigating Jun 01, 2026, 10:16 AM UTC
We are aware of an ongoing incident with an upstream provider (Red Hat / Quay.io) that is reporting degraded performance on container registry push/pull operations https://status.redhat.com/incidents/jn6r256zc62c. As a precaution, customers may experience intermittent slowness or delays with some Sisense services that depend on this provider. We are actively monitoring the situation and assessing any potential impact to our platform.
-
monitoring Jun 01, 2026, 10:26 AM UTC
RedHat have restored manifest pushes and are monitoring the environment for stability.
-
resolved Jun 01, 2026, 10:54 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 10:42 AM UTC
- Resolved
- May 13, 2026, 10:47 AM UTC
- Duration
- 5m
Affected: Sisense for Cloud Data TeamsSisense Managed Service
Timeline · 4 updates
-
investigating May 13, 2026, 10:42 AM UTC
Please be aware that on May 11, starting at 10:30 AM EEST, we experienced a service outage affecting the AI Assistant. During this window, users across all accounts may have experienced non-responsive behavior when attempting to create charts or submit general queries to the Assistant.
-
identified May 13, 2026, 10:44 AM UTC
Following a technical investigation, the issue was traced back to the Shared Gateway Service, which was preventing requests from reaching the AI processing engine.
-
monitoring May 13, 2026, 10:46 AM UTC
Our engineering team applied mitigation steps and re-applied configuration to clear the gateway bottleneck and restore the flow of traffic.
-
resolved May 13, 2026, 10:47 AM UTC
2:00 PM EEST The fix was verified, and the service was confirmed as fully operational. Root Cause: The outage was corrupted configuration in the AI Shared Gateway Service, affecting its ability to handle Assistant-specific traffic. We sincerely apologize for the impact this had on your workflow. We are currently reviewing our gateway capacity and alerting thresholds to prevent a recurrence of this specific issue.
Read the full incident report →
- Detected by Pingoru
- Mar 21, 2026, 03:26 AM UTC
- Resolved
- Mar 21, 2026, 03:26 AM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Mar 21, 2026, 03:26 AM UTC
Mar 20, 20:26 PDT Resolved - The incident has been resolved. Mar 20, 20:02 PDT Monitoring - A fix has been implemented and we are monitoring the results. Mar 20, 19:45 PDT Identified - The issue has been identified and we are actively working on a fix. Mar 20, 17:49 PDT Investigating - We’re currently observing a partial outage affecting Sisense managed instances. Our team is actively investigating the issue and working to identify the root cause. We’ll share updates as soon as we have more information. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2026, 01:32 PM UTC
- Resolved
- Feb 21, 2026, 01:32 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Feb 21, 2026, 01:32 PM UTC
Feb 21, 05:32 PST Completed - The scheduled maintenance has been completed. Feb 21, 05:19 PST Verifying - Verification is currently underway for the maintenance items. Feb 21, 04:03 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 20, 11:55 PST Scheduled - Sisense for Cloud Data Teams platform is scheduled for maintenance with estimated downtime of approximately 6 hours. We will be using this time to perform database maintenance to ensure ongoing stability and performance. During this window, Sisense for Cloud Data Teams will be inaccessible. The system will be accessible immediately after the maintenance is complete. If you have any questions regarding the status of the maintenance or experience any issues after we’re back up and running, please check the status page at status.sisense.com or contact our support team as [email protected].
Read the full incident report →
- Detected by Pingoru
- Jan 13, 2026, 04:28 PM UTC
- Resolved
- Jan 13, 2026, 04:28 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Jan 13, 2026, 04:28 PM UTC
Jan 13, 08:28 PST Resolved - This incident has been resolved. Jan 13, 06:54 PST Monitoring - The issue has been resolved, and we are continuing to monitor to ensure stability. Jan 13, 05:25 PST Identified - We’ve identified an issue affecting specific EKS clusters that may impact the build process. Our team is actively working on a resolution.
Read the full incident report →
- Detected by Pingoru
- Jan 06, 2026, 05:32 PM UTC
- Resolved
- Jan 06, 2026, 05:32 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Jan 06, 2026, 05:32 PM UTC
Jan 6, 09:32 PST Resolved - The platform's performance has been restored to the normal level. Jan 6, 09:19 PST Monitoring - A fix was deployed, and the engineering team is continuously monitoring the state of the platform to make sure that the performance is back to normal. Jan 6, 07:56 PST Update - We are continuing to investigate this issue. Jan 6, 07:55 PST Investigating - Due to issues with the SSL certificate, some clients might experience an error while trying to log in. Our engineering team is aware of the situation and is investigating the matter in order to come up with a workaround or a fix.
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 09:26 AM UTC
- Resolved
- Dec 05, 2025, 09:26 AM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Dec 05, 2025, 09:26 AM UTC
Dec 5, 01:26 PST Resolved - This incident has been resolved. Dec 5, 01:23 PST Monitoring - Cloudflare has implemented a fix for the issue, and we are currently monitoring the results. Dec 5, 01:10 PST Investigating - Cloudflare is currently experiencing an issue. As a result, some requests may fail or errors may be displayed. We are monitoring the situation and will provide updates as it progresses.
Read the full incident report →
- Detected by Pingoru
- Dec 02, 2025, 02:12 PM UTC
- Resolved
- Dec 02, 2025, 02:12 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Dec 02, 2025, 02:12 PM UTC
Dec 2, 06:12 PST Resolved - This incident has been resolved. Dec 2, 06:00 PST Identified - We are aware of an incorrect banner message indicating that your trial will expire in 7 days. Please disregard this notification. Our Engineering team is actively working on a fix.
Read the full incident report →
- Detected by Pingoru
- Oct 29, 2025, 11:28 PM UTC
- Resolved
- Oct 29, 2025, 11:28 PM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Sep 27, 2025, 04:27 PM UTC
- Resolved
- Sep 27, 2025, 04:27 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Sep 27, 2025, 04:27 PM UTC
Sep 27, 09:27 PDT Completed - The scheduled maintenance has been successfully completed, and the platform is now fully operational. We are continuously monitoring system performance to ensure stability. In case you encounter any issues, please feel free to contact our support team at [email protected] Sep 27, 09:17 PDT Verifying - The scheduled maintenance has been successfully completed. All systems are now fully operational, and we are continuously monitoring performance to ensure everything runs smoothly. Sep 27, 04:15 PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep 27, 04:13 PDT Scheduled - We are currently performing routine maintenance to improve our services. The platform would be temporarily unavailable during this time. Thank you for your understanding — everything will be back online shortly.
Read the full incident report →
- Detected by Pingoru
- Sep 26, 2025, 05:06 AM UTC
- Resolved
- Sep 26, 2025, 05:06 AM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Sep 26, 2025, 05:06 AM UTC
Sep 25, 22:06 PDT Resolved - This incident has been resolved. Sep 25, 13:16 PDT Monitoring - The CDT Live Chat Support has been restored. The live chat service is now fully operational. You can once again reach our support team directly through live chat or via email at [email protected]. Thank you for your patience while we resolved this issue. Sep 25, 11:29 PDT Investigating - Our live chat service for Siense CDT is currently unavailable. Please reach us at [email protected] for assistance. We apologize for any inconvenience and will restore chat functionality as soon as possible.
Read the full incident report →
- Detected by Pingoru
- Sep 16, 2025, 07:33 PM UTC
- Resolved
- Sep 16, 2025, 07:33 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Sep 16, 2025, 07:33 PM UTC
Sep 16, 12:33 PDT Resolved - This incident has been resolved. Sep 16, 12:31 PDT Update - The issue with the ticketing system that was causing slower response times has been resolved. Support response times have returned to normal, and no further impact is expected. Sep 16, 09:35 PDT Identified - We’re experiencing an issue with our ticketing system that may cause slower response times than usual. Our Support team is working to fix this as quickly as possible.
Read the full incident report →
- Detected by Pingoru
- Aug 21, 2025, 07:53 PM UTC
- Resolved
- Aug 21, 2025, 07:53 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Aug 21, 2025, 07:53 PM UTC
Aug 21, 12:53 PDT Resolved - This incident has been resolved. Aug 21, 12:06 PDT Update - We are continuing to work on a fix for this issue. Aug 21, 11:50 PDT Identified - We are currently experiencing degraded availability of certain AI-powered features, including Natural Language Queries (NLQ), in the us-east-1 region. This is related to ongoing network performance issues reported by our security provider (Cloudflare), as noted on their status page: https://www.cloudflarestatus.com/incidents/d9n3g1vnxdd2 All core Sisense services remain fully operational. Only AI-related functionality is impacted, and customers may encounter intermittent errors or unavailability when using these features. Our engineering team is actively monitoring the situation and working with Cloudflare to track their progress toward resolution. We will continue to provide updates and confirm once AI feature availability has been fully restored.
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2025, 07:00 PM UTC
- Resolved
- Aug 18, 2025, 07:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 19, 2025, 06:20 PM UTC
Some customers experienced intermittent issues when accessing Sisense APIs and the Support Portal. The disruption was caused by a dynamic adjustment within our traffic bot management rules, which automatically adapt based on observed traffic patterns. In this instance, the adjustment inadvertently impacted certain legitimate API requests. Once the issue was identified, our security engineering team promptly reverted the adjustment, and services were quickly restored. All environments are fully operational, and we are actively monitoring system performance to ensure continued stability. We are working closely with our traffic management provider to fine-tune protections so that future adjustments do not affect customer traffic. We sincerely apologize for the disruption and greatly appreciate your patience and understanding as we resolved the issue.
Read the full incident report →
- Detected by Pingoru
- Jun 24, 2025, 06:58 PM UTC
- Resolved
- Jun 24, 2025, 06:58 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Jun 24, 2025, 06:58 PM UTC
Jun 24, 11:58 PDT Resolved - This incident has been resolved. Jun 24, 11:30 PDT Monitoring - A fix has been implemented and we are monitoring the results. Jun 24, 11:07 PDT Update - Patch is rolling out to all impacted instances. Jun 24, 10:11 PDT Identified - The issue has been identified and fix is going to be rollout soon. Jun 24, 06:42 PDT Investigating - We are currently investigating an issue affecting some of our embedded capabilities via iframe, where widgets may fail to load and appear blank on limited number of environment. Our engineering team is actively working to identify the root cause and implement a fix. At this time, there is no estimated time of resolution (ETA). Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 05:20 PM UTC
- Resolved
- Jun 03, 2025, 06:28 PM UTC
- Duration
- 1h 8m
Affected: Sisense for Cloud Data Teams
Timeline · 3 updates
-
investigating Jun 03, 2025, 05:20 PM UTC
Some CDT clients may experience a temporary interuption of the SQL query processing. The engineering team was notified and is already working on identifying the cause of the issue to apply an appropriate fix and restore SQL query processing.
-
monitoring Jun 03, 2025, 05:28 PM UTC
The engineering team was able to restore the SQL query processing service functionality. The fix was applied, we continue to actively monitor the situation and performance.
-
resolved Jun 03, 2025, 06:28 PM UTC
The issue was resolved, and the platform performance is restored to normal condition
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2025, 01:12 PM UTC
- Resolved
- Mar 05, 2025, 04:04 PM UTC
- Duration
- 2h 51m
Affected: Sisense Managed Service
Timeline · 2 updates
-
identified Mar 05, 2025, 01:12 PM UTC
The admin section is currently inaccessible in a limited number of lower environments. Our team is actively working on a resolution and expects to have it fixed by the end of the day.
-
resolved Mar 05, 2025, 04:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2025, 05:18 PM UTC
- Resolved
- Feb 25, 2025, 06:06 PM UTC
- Duration
- 47m
Affected: Sisense for Cloud Data Teams
Timeline · 3 updates
-
identified Feb 25, 2025, 05:18 PM UTC
Some clients might experience issues with accessing the password-protected shared dashboard links. The engineering team has identified the cause of the issue and is working to develop a fix. Please feel free to contact [email protected] for any additional questions
-
monitoring Feb 25, 2025, 06:02 PM UTC
A fix to address the access issues for shared dashboard links was deployed. The engineering team continues to monitor the platform to make sure that all services are operational. For any assistance please feel free to reach out to [email protected]
-
resolved Feb 25, 2025, 06:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2025, 09:07 AM UTC
- Resolved
- Feb 18, 2025, 09:59 AM UTC
- Duration
- 51m
Affected: Sisense Managed Service
Timeline · 3 updates
-
identified Feb 18, 2025, 09:07 AM UTC
The issue was reported to have begun on February 17th, 2025, at 5:30 PM GMT+2. The team has identified the cause of the problem and is actively working to resolve it.
-
monitoring Feb 18, 2025, 09:25 AM UTC
A fix has been implemented and we are monitoring the result.
-
resolved Feb 18, 2025, 09:59 AM UTC
The issue has been resolved, and previously affected components have been functioning properly for 30 minutes.
Read the full incident report →
- Detected by Pingoru
- Jan 07, 2025, 03:49 PM UTC
- Resolved
- Jan 07, 2025, 09:51 PM UTC
- Duration
- 6h 1m
Affected: Sisense for Cloud Data Teams
Timeline · 2 updates
-
monitoring Jan 07, 2025, 03:49 PM UTC
The issue with the SSL certificate was resolved and the platform is back to operating normally. Due to caching refresh in some regions of the Content Delivery Networks, some clients might still get the SSL error notification. The timeline for the update to be pushed to your region could vary based on your ISP networking configuration. We continue to monitor the platform to make sure that the access is fully restored for all the clients.
-
resolved Jan 07, 2025, 09:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 07, 2025, 02:10 PM UTC
- Resolved
- Jan 07, 2025, 02:26 PM UTC
- Duration
- 16m
Affected: Sisense for Cloud Data Teams
Timeline · 2 updates
-
investigating Jan 07, 2025, 02:10 PM UTC
Our engineers are taking proactive action to identify the cause of the outage and put the platform back online in the shortest terms possible.
-
resolved Jan 07, 2025, 02:26 PM UTC
The certificate issue was resolved. The access to CDT platform was fully restored
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2024, 02:49 PM UTC
- Resolved
- Nov 05, 2024, 07:41 PM UTC
- Duration
- 4h 51m
Affected: Sisense for Cloud Data Teams
Timeline · 2 updates
-
monitoring Nov 05, 2024, 02:49 PM UTC
The platform has experienced a minor DNS issue that our engineering team has already addressed. Unfortunately, the DNS caching timeframe could potentially delay the fix for some clients for approximately 24 hours or less. The issue could affect the clients with sites running a dedicated Warehouse infrastructure. In case you have experienced any such issues please contact us at [email protected] or start a live chat.
-
resolved Nov 05, 2024, 07:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2024, 02:30 PM UTC
- Resolved
- Jul 01, 2024, 05:28 PM UTC
- Duration
- 2h 57m
Affected: Sisense for Cloud Data Teams
Timeline · 4 updates
-
investigating Jul 01, 2024, 02:30 PM UTC
We noticed that there is an outage in transactional emails. Our engineering team is actively working on the issue.
-
identified Jul 01, 2024, 02:35 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 01, 2024, 05:13 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 01, 2024, 05:28 PM UTC
This incident has been resolved.
Read the full incident report →