Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Sigma Computing Outage History

Every past Sigma Computing outage tracked by IsDown, with detection times, duration, and resolution details.

There were 35 Sigma Computing outages since November 2021. The 9 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 8, 2026

April 2026: Permission Denied Errors on Elements Sourced from Custom SQL Tables

Detected Apr 8, 2026 2:22 PM EDT · Resolved Apr 8, 2026 7:39 PM EDT · Duration about 5 hours

Sigma Computing experienced permission denied errors affecting workbooks with elements sourced from custom SQL tables across all regions for 5.3 hours starting at 2:00PM UTC on April 8, 2026. View/Lite users were unable to access workbooks and received permission denied errors when attempting to view content. The incident was resolved after investigation into the permissions system issues.

Minor March 31, 2026

March 2026: Experiencing issues with Google sheets Integration

Detected Mar 31, 2026 5:08 PM EDT · Resolved Mar 31, 2026 11:31 PM EDT · Duration about 6 hours

Sigma Computing experienced a service disruption affecting Google Sheets integration across all regions from approximately 19:15 UTC to 22:12 UTC on March 31, 2026, lasting 6.4 hours. Users were unable to create or use Google Sheets integrations in their exports during this period. Engineers identified the root cause, deployed mitigation measures, and successfully restored full functionality to the Google Sheets integration and related export features.

Major March 4, 2026

March 2026: Burst email exports resumed

Detected Mar 4, 2026 3:50 PM EST · Resolved Mar 9, 2026 1:31 PM EDT · Duration 5 days

Sigma Computing experienced a technical issue that caused burst email exports to be temporarily paused for 116.7 hours, while standard exports remained fully operational throughout the incident. The engineering team identified and deployed a fix, then conducted thorough internal validation and monitoring before re-enabling the feature. The issue has been fully resolved with burst email exports now operating as expected.