Sisense Service Page Outage History

11 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Sisense Service Page status100.00% uptime history

Every Recorded Sisense Service Page Incident

Sisense Service Page incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jun 1, 2026Possible Service Degradation Due to Recurring Upstream Provider IncidentThis incident has been resolved.6h 35mResolved
Jun 1, 2026Possible Service Degradation Due to Upstream Provider IncidentThis incident has been resolved.37 minResolved
May 13, 2026Investigating Potential Service Issues2: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…5 minResolved
May 8, 2026Investigating Potential Service IssuesAWS has officially resolved the thermal and power event in the US-EAST-1 region. All underlying infrastructure supporting our Sisense servers has been stabilized and is performing at pre-event levels. Our engineering…32h 29mResolved
Mar 21, 2026Partial Outage Observed for Sisense Managed InstancesThe incident has been resolved.2h 36mResolved
Feb 21, 2026Scheduled Sisense for Cloud Data Teams maintenanceThe scheduled maintenance has been completed.6h 0mScheduled
Jan 13, 2026Investigating Potential EKS Service IssuesThis incident has been resolved.3h 3mResolved
Jan 6, 2026CDT platform is unavailable to some clients due to SSL certificate errorThe platform's performance has been restored to the normal level.1h 36mResolved
Dec 5, 2025Cloudflare Incident UpdateThis incident has been resolved.16 minResolved
Dec 2, 2025Trial Expiration BannerThis incident has been resolved.12 minResolved
Nov 18, 2025Investigating Potential Service IssuesThis incident has been resolved.5h 45mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Sisense Service Page incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Sisense Service Page Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Sisense Service Page acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Sisense Service Page outage in this window ran 1d 8h, against a mean recovery of 5h 23m. If you depend on Sisense Service Page in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.