Looking for an update now? Check the current status, or follow Sisense for future changes.
100%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
5 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Possible Service Degradation Due to Recurring Upstream Provider Incident
Source not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
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.
Possible Service Degradation Due to Upstream Provider Incident
Source not attested
Last archived state: resolved
View archived record details
monitoring
RedHat have restored manifest pushes and are monitoring the environment for stability.
investigating
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.
May 2026
Investigating Potential Service Issues
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our engineering team applied mitigation steps and re-applied configuration to clear the gateway bottleneck and restore the flow of traffic.
identified
Following a technical investigation, the issue was traced back to the Shared Gateway Service, which was preventing requests from reaching the AI processing engine.
investigating
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.
Investigating Potential Service Issues
Source not attested
Last archived state: resolved
View archived record details
monitoring
We no longer see the consequences of the AWS incident after they updated the AWS incident page with "Resolved" status.
For the latest on the underlying AWS infrastructure, please refer to: https://health.aws.amazon.com/health/status
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
Please be aware that AWS (Amazon Web Services) is currently reporting significant hardware and power issues in the US-EAST-1 (N. Virginia) region. For the most up-to-date information on their infrastructure recovery, please follow the official AWS Health Dashboard https://health.aws.amazon.com/health/status . Unfortunately, our Sisense servers are also severely impacted by this event. As a result, users may experience total loss of access, dashboard loading failures, or significant latency. ...
March 2026
Partial Outage Observed for Sisense Managed Instances
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and we are actively working on a fix.
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.
