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