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

OperationalChecked 4m agoLive · 60s while moving

Know the moment Sigma Computing breaks

Sigma Computing is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment 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 while one is moving, every 5 to 20 minutes while it is stable), 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.

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.

Unable to change email message in scheduled exports inside Sigma reportsResolved Sep 21, 2026 · 1h 54mResolved

The issue has now been fixed and users should be able to change the scheduled export email messages successfully now. --- [2026-09-21T18:28:26.347Z] (monitoring) We are continuing to monitor for any further issues. --- [2026-09-21T18:25:11.536Z] (monitoring) A fix has been implemented and we are monitoring the results now. --- [2026-09-21T17:03:50.097Z] (identified) The issue has been identified and a fix is being implemented by the Engineering team. --- [2026-09-21T16:34:54.869Z] (investigating) We are investigating an issue with scheduled exports in reports where users are unable to change the email message. We are treating this as our highest priority. Our apologies for any inconvenience caused. Impacted Cloud Regions & Services: All regions User Experience: Upon changing the scheduled export message, it reverts back to the default message. Incident Start Time: Approximately 15:43 UTC September 21, 2026

Databricks Azure East US query timeoutResolved Sep 14, 2026 · 3h 21mResolved

The Azure East US Databricks service interruption has been resolved. Sigma connections to Databricks Azure East US are no longer experiencing query execution failures or timeouts, and warehouse connections are working normally. This was caused by a Databricks Azure East US service interruption (https://status.azuredatabricks.net/). If you continue to see errors on your Databricks connection in Sigma, please reach out to us. We apologize for the disruption and thank you for your patience. --- [2026-09-14T21:55:54.758Z] (monitoring) Databricks Azure East US has recovered and is now operational. Sigma connections to Databricks Azure East US should no longer experience query execution failures or timeouts, and warehouse connections should be working normally. This was caused by a Databricks Azure East US service interruption (https://status.azuredatabricks.net/). If you're still seeing errors on your Databricks connection in Sigma, please continue monitoring: https://status.azuredatabricks.net/ We apologize for the disruption and thank you for your patience. --- [2026-09-14T21:19:26.330Z] (identified) Databricks Azure East US is degraded services which is affecting Sigma connections and causing query execution failures and timeouts on Databrick warehouse. We are investigating these errors owing to Databricks Azure East US service interruption (https://status.azuredatabricks.net/) and haven't detected an issue other warehouses at the moment. If your Databrick connection in Sigma is experiencing errors, please continue monitoring: https://status.azuredatabricks.net/ We apologize for the disruption and will keep this page updated. --- [2026-09-14T19:31:55.692Z] (identified) Databricks Azure East US is degraded services which is affecting Sigma connections and causing query execution failures and timeouts on Databrick warehouse. We are investigating these errors owing to Databricks Azure East US service interruption (https://status.azuredatabricks.net/) and haven't detected an issue other warehouses at the moment. If your Databrick connection in Sigma is experiencing errors, please continue monitoring: https://status.azuredatabricks.net/ Our apologies for any inconvenience caused.

Input Table Edits Failing if customer updated warehouse connectionResolved Sep 10, 2026 · 27h 37mResolved

The mitigation measures have proven effective, and the issue is resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days. --- [2026-09-11T17:51:23.619Z] (monitoring) We applied a mitigation and are monitoring its effect closely. Customers can now safely change warehouse connection auth method and make input table edits. We'll share our next update in 4 hours. Thanks for your patience. --- [2026-09-11T04:14:11.183Z] (monitoring) Our engineers have implemented mitigation measures to circumvent the issue and we are monitoring their effect closely. Customers can now safely change warehouse connection auth method and make input table edits. --- [2026-09-11T02:37:15.706Z] (identified) Customers can now safely change warehouse connection auth method. We are still restoring the impacted customers who are unable to make edits to input tables that were created prior to the auth method change. We will post another update once the input tables have been restored. We apologize for the inconvenience and will continue to update this page as we make progress. --- [2026-09-11T00:46:27.670Z] (identified) Customers can now change auth methods safely. However we are still restoring the affected customers who are unable to make edits to input tables. We will post another update once the input tables have been restored. We apologize for the inconvenience and will continue to update this page as we make progress! --- [2026-09-10T22:45:58.643Z] (identified) We've identified an issue causing edits to existing input tables to fail on certain connections using OAuth authentication when connection was changed from non-OAuth connection. Our engineering team is now testing a fix in internal environments. we will continue to update the page as we make progress. Thanks for your patience! --- [2026-09-10T19:18:04.110Z] (identified) We have reverted the issue, customers can now change their warehouse connection Auth Method without breaking input tables. We are still working to restore writeback on input tables for the affected connections. We will post another update once the input tables have been restored. We apologize for the inconvenience and will continue to update this page as we make progress! --- [2026-09-10T18:24:19.198Z] (identified) We've identified an issue causing edits to existing input tables to fail on certain connections using OAuth authentication when connection was changed from non-OAuth connection. Impact: Some customers are unable to save edits to existing input tables on affected connections. Next Steps: We are reverting the change that introduced this regression and are working to restore writeback on input tables for the affected connections. We will post another update once a fix has been deployed. We apologize for the inconvenience and will continue to update this page as we make progress!

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 history49 days observed

Aug 8100.00% average · 2 days with incidentsSep 25

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 99.97%. 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 a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

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 99.97%. 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 a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

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

2463+ 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