Sigma Computing logo

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 November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Sigma Computing breaks

Sigma Computing is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

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

Status report

Sigma Computing Status Summary

As of 22:12 UTC on 9 November 2026, Sigma Computing is operational. PulsAPI checked Sigma Computing's official status page and found 13 of 13 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Sigma Computing, counting degraded performance as up. The latest incident, "Degraded performance in AWS US-WEST-2 hosted organizations", was on Nov 7, 2026 and lasted 1h 2m.

Cite as: PulsAPI, “Sigma Computing status”, checked 9 November 2026, 22:12 UTC. https://www.pulsapi.com/services/sigma-computing

Sigma Computing Component Status

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

13operational
AWS » Sigma - AWS · APAC Australia
Operational
AWS » Sigma - AWS · Canada
Operational
AWS » Sigma - AWS · Europe
Operational

10 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.

See all of them free

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.

Degraded performance in AWS US-WEST-2 hosted organizationsResolved Nov 7, 2026 · 1h 2mResolved

This incident has been resolved. AWS status page: https://health.aws.amazon.com/health/status --- [2026-11-07T00:21:39.924Z] (monitoring) At approximately 22:51 UTC on November 6, 2026, AWS reported elevated launch failures in the US-WEST-2 region (AWS status page: https://health.aws.amazon.com/health/status). Sigma organizations hosted on AWS US-WEST-2 may experience elevated latency during this time. We are monitoring AWS status.

Service degradation in GCP-US-hosted organizationsResolved Nov 5, 2026 · 5h 42mResolved

On November 5, 2026 between approximately 01:28 UTC to 02:25 UTC, Sigma users in GCP-US-hosted organizations saw high error rates when creating workbooks and explorations, publishing workbooks, tagging workbooks, and sending instant exports. This incident is now resolved and the Sigma app is fully operational. Incident Start Time: November 5, 2026 01:28 UTC Incident End Time: November 5, 2026 02:25 UTC We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days.

Service Degradation for writeback functionality on Databricks connectionsResolved Oct 12, 2026 · 3h 6mResolved

The AWS US West Databricks service interruption has been resolved. Sigma connections to Databricks on affected region are no longer experiencing writeback failures. The root cause has been identified as a Databricks AWS US West 2 service interruption (https://status.databricks.com/pages/incident/5cf02dde58a00904bda41926/6accd920d492610581e1c8c1). If you continue to have writeback errors on your Databricks connection in Sigma, please reach out to us. We apologize for the disruption and thank you for your patience. --- [2026-10-12T17:29:57.203Z] (monitoring) Databricks AWS US West 2 has recovered. Sigma Databricks connections in the affected region should no longer experience failures with writeback functionality, such as Input Tables. It was caused by an incident on Databricks here - https://status.databricks.com/pages/incident/5cf02dde58a00904bda41926/6accd920d492610581e1c8c1 We apologize for the disruption and thank you for your patience. We will continue to update this page as we monitor the status. --- [2026-10-12T16:10:24.082Z] (identified) Sigma is currently being affected by a 3rd party Databricks outage and some customers are unable to upload CSVs to our Sample Connection. Writeback functionality, such as Input Tables for customers with Databricks on the affected regions listed below may also be affected by this event. Our internal monitoring has identified a correlation between the two systems and we are currently monitoring the active incident here - https://status.databricks.com/pages/incident/5cf02dde58a00904bda41926/6accd920d492610581e1c8c1 We will provide another update within 120 minutes as the situation develops. --- [2026-10-12T15:13:34.469Z] (identified) Sigma is currently being affected by a 3rd party Databricks outage and some customers are unable to upload CSVs to our Sample Connection. Writeback functionality, such as Input Tables for customers with Databricks on the affected regions listed below may also be affected by this event. Our internal monitoring has identified a correlation between the two systems and we are currently monitoring the active incident here - https://status.databricks.com/pages/incident/5cf02dde58a00904bda41926/6accd920d492610581e1c8c1 We will update this page as the situation develops.

Sigma Computing Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Sigma Computing incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 4 days with incidentsNov 9

Going further back: Sigma Computing uptime by month and every recorded Sigma Computing outage.

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?

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. PulsAPI re-checks it every 60 seconds.

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%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Sigma Computing changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Sigma Computing outages?

PulsAPI reads the official Sigma Computing status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Sigma Computing components?

Yes. PulsAPI monitors 13 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 free account and subscribe to Sigma Computing: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

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. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Sigma Computing plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Sigma Computing with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services