Sisense incident
Possible Service Degradation Due to Upstream Provider Incident
Sisense experienced a notice incident on June 1, 2026 affecting Sisense Managed Service, lasting 37m. The incident has been resolved; the full update timeline is below.
Affected components
Sisense Managed Service
Update timeline
- 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.