Is Sigma Computing Down?

SaaSLive status, outages, and incident history

No. Sigma Computing is up right now.

Every monitored Sigma Computing system is operational as of August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 12m agoLive, rechecked every 60s

Start monitoring Sigma Computing Official Sigma Computing status page

How we know: the official Sigma Computing status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Sigma Computing Component Status

The main Sigma Computing systems on this page. All 11 are operational right now.

11operational

AWS » Sigma - AWS

Operational

AWS » Sigma - AWS

Operational

AWS » Sigma - AWS

Operational

8 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Azure » Sigma - Azure, GCP » Sigma - GCP.

Create a free account

Component statuses may change independently during partial outages.

Recent Sigma Computing Outages & Incidents

Incident history from the official Sigma Computing status page, including resolution updates.

Uptime history4 days observed

Aug 8100.00% averageAug 11

Delayed audit logs and usage data in AWS US WestStarted Aug 10, 2026Investigating

Status: Mitigated The issue has been mitigated - audit logs and usage data are flowing and updating normally again. We're now in a monitoring phase to confirm stability. No data has been lost. --- [2026-08-10T22:52:25.799Z] (identified) The resync remains in progress. No data has been lost - records are being backfilled and will appear as the sync progresses. We'll provide another update as soon as there's meaningful progress to share. --- [2026-08-10T18:37:31.566Z] (identified) Impact: Some organizations in the AWS US West (Oregon) region are seeing delayed updates to audit logs and usage dashboards. Our engineering team has identified the cause and is actively resyncing the affected data. No data has been lost - records are being backfilled and will appear as the sync progresses. We'll post an update as soon as the data is fully current. Incident Start Time: Aug 5, 2026, 15:37 UTC

Materialization cleanup delayed for Sigma users on AWS US-West-2Resolved Aug 4, 2026 · 3h 20mResolved

The mitigation measures have proven effective, and the issue has been resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note in the coming days. We apologize for any inconvenience this may have caused. Impacted Cloud Regions & Services: Sigma users hosted on AWS US-West-2 using materialization User Experience: Customers using materializations on AWS US-West-2 should no longer see the previously reported table accumulation. Incident Start Time: Approximately August 3, 2026, at 2:44 PM UTC Incident End Time: Approximately August 5, 2026, at 02:40 AM UTC --- [2026-08-05T00:20:13.678Z] (monitoring) Our engineers have implemented mitigation measures for this issue and are closely monitoring their effectiveness. We expect the backlog to continue clearing over the next several hours. We will provide a further update once we can confirm full resolution. Impacted Cloud Regions & Services: Sigma users hosted on AWS US-West-2 using materialization User Experience: Customers using materializations on AWS US-West-2 may continue to see table accumulation reported earlier while the backlog clears; no new action is needed. Incident Start Time: Approximately August 3, 2026, at 2:44:18 PM UTC --- [2026-08-04T23:58:39.246Z] (investigating) We are investigating an issue affecting materialization tables, which are not being cleaned up as expected in some customers' connected warehouses, causing them to accumulate over time. We are treating this as our highest priority and are actively working to identify and resolve the root cause. We apologize for any inconvenience this may cause. Impacted Cloud Regions & Services: Sigma users hosted on AWS US-West-2 using materialization User Experience: Customers using materializations on AWS US-West-2 may see stale materialization tables accumulating in their connected warehouse, which over time could approach warehouse storage/object limits. Incident Start Time: Approximately August 3, 2026, at 2:44:18 PM UTC

Workbooks containing Snowflake Semantic Views fail to loadResolved Aug 4, 2026 · 33 minResolved

Sigma engineering has identified the cause, and the issue is now resolved. Users will need to perform a hard refresh of their browser to see the fix take effect. We will conduct a root cause analysis (RCA) and publish our findings in a postmortem note on the Sigma Community site in the coming days. Impacted Cloud Regions & Services: All Regions User Experience: Workbooks should now load normally after a hard refresh or browser restart. Incident Start Time: Approximately 08:30 UTC, August 4, 2026 Incident End Time: Approximately 10:42 UTC, August 4, 2026 --- [2026-08-04T11:22:20.272Z] (investigating) We are investigating an issue where workbooks containing a Snowflake Semantic View fail to load. Sigma Engineering is actively engaged as our highest priority. We apologize for any inconvenience caused. Impacted Cloud Regions & Services: All Regions User Experience: Workbook stuck in loading state when containing snowflake semantic views Workarounds: None at this time ETA: We do not have an ETA for resolution at this time. Updates will be provided as more information becomes available. Incident Start Time: Approximately 08:30 UTC, August 4, 2026

Live Sigma Computing Outage Reports

Problems reported by engineers using Sigma Computing. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No Sigma Computing problems reported yet.

Something wrong with Sigma Computing on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Sigma Computing

Sigma Computing exposes 14 monitored components on its status page at status.sigmacomputing.com — Sigma - GCP (US), Sigma - AWS (Europe) and Sigma - Azure (US) among them. Follow Sigma Computing downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured Sigma Computing uptime at 100.00%. Response times, incident history, and SLA tracking for Sigma Computing are available on the PulsAPI dashboard.

Sigma Computing Status FAQ

Is Sigma Computing down right now?

PulsAPI checks Sigma Computing every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Sigma Computing status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Sigma Computing is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Sigma Computing recovers.

How do I check Sigma Computing uptime history?

PulsAPI tracks Sigma Computing uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Sigma Computing.

How fast does PulsAPI detect Sigma Computing outages?

PulsAPI polls the official Sigma Computing status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Sigma Computing components?

Yes. PulsAPI monitors 11 individual Sigma Computing components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Sigma Computing goes down?

Yes. Create a PulsAPI account and subscribe to Sigma Computing. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Sigma Computing status changes.

How do I report an issue with Sigma Computing to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Sigma Computing problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Sigma Computing?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Sigma Computing alongside up to 9 other services at pulsapi.com/signup.

Track Sigma Computing with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Sigma Computing status changes.

Start free trial