Snapshot 14775
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"pages": [
{
"end_time": "2026-09-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "vj4whfqnfhsl",
"impact": "major",
"message": "We've identified the root cause and applied a fix, and we're now monitoring the resolution.\n\nScheduled exports should resume as expected, and users on orgs with password authentication should now be able to sign in. \n\nOur preliminary investigations indicate the following:\nImpacted Cloud Regions: Azure, AWS, GCP\nIncident Start Time: Approximately September 26, 2026, at 11:24 AM UTC",
"name": "Export Failures Incident",
"timestamp": "Sep \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e15:25\u003c/var\u003e - \u003cvar data-var='time'\u003e16:11\u003c/var\u003e UTC"
},
{
"code": "s4z1tnxb3mz3",
"impact": "none",
"message": "The issue has now been fixed and users should be able to change the scheduled export email messages successfully now.",
"name": "Unable to change email message in scheduled exports inside Sigma reports",
"timestamp": "Sep \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e16:34\u003c/var\u003e - \u003cvar data-var='time'\u003e18:29\u003c/var\u003e UTC"
},
{
"code": "2hs2qc5jpdc6",
"impact": "major",
"message": "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. \n\nThis 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. \n\nWe apologize for the disruption and thank you for your patience.",
"name": "Databricks Azure East US query timeout",
"timestamp": "Sep \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e19:31\u003c/var\u003e - \u003cvar data-var='time'\u003e22:53\u003c/var\u003e UTC"
},
{
"code": "jqwn9m2bh02k",
"impact": "none",
"message": "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.",
"name": "Input Table Edits Failing if customer updated warehouse connection",
"timestamp": "Sep \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e18:24\u003c/var\u003e - Sep \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e22:01\u003c/var\u003e UTC"
},
{
"code": "dc3xdgdz224t",
"impact": "none",
"message": "We received reports of errors causing scheduled materializations and exports to fail.\nThis has been resolved now. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days.\n\nImpacted Cloud Regions \u0026amp; Services: azure:production:eastus2 and aws:us-west-2\n\nUser Experience: For organizations hosted in the affected regions (aws:us-west-2 and azure:production:eastus2), scheduled materializations and scheduled exports did not run for the duration of the incident. Exports and materializations have since returned to normal operation. Organizations with a high volume of scheduled exports may experience some delayed processing as queued jobs catch up.\n\nIncident Start Time: Approximately 12:02 PM UTC\nIncident End Time: Approximately 1:01PM UTC",
"name": "Scheduled Materialization and Export Failures",
"timestamp": "Sep \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e13:37\u003c/var\u003e - \u003cvar data-var='time'\u003e13:37\u003c/var\u003e UTC"
},
{
"code": "8ttp4ncqt8lp",
"impact": "critical",
"message": "This incident has been resolved. Our engineers are seeing services have returned to normal. Multiple customers have confirmed that they can load Sigma successfully. We apologize for the inconvenience and will continue monitoring the service closely. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days.\n\nImpacted Cloud Regions \u0026amp; Services: Sigma users hosted on GCP\n\nUser Experience: GCP-hosted users will be able to load Sigma, open workbooks, or render reports without any issues.\n\nIncident Start Time: Approximately 02:46 PM UTC Sep 1, 2026\nIncident End Time: Approximately 05:29 PM UTC Sep1, 2026",
"name": "Widespread failures are preventing Sigma from loading for GCP-hosted organizations.",
"timestamp": "Sep \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e15:34\u003c/var\u003e - \u003cvar data-var='time'\u003e16:55\u003c/var\u003e UTC"
},
{
"code": "d33g04w6z61d",
"impact": "none",
"message": "Between August 28 at approximately 11:47 PM UTC and September 1 at approximately 4:09 PM UTC, scheduled and direct exports displayed some number and date columns as text when opened in Excel and Google Sheets. \n\nThe cause has been identified and 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.\n\nTimeline\nIncident start time: August 28, approximately 11:47 PM UTC\nIncident end time: September 1, approximately 4:09 PM UTC",
"name": "Exports displayed number and date columns as text in Excel and Google Sheets",
"timestamp": "Sep \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e04:00\u003c/var\u003e - \u003cvar data-var='time'\u003e04:00\u003c/var\u003e UTC"
}
],
"name": "September",
"year": 2026
},
{
"incidents": [
{
"code": "r5dwj58sjypv",
"impact": "none",
"message": "Status: Resolved\n\nThe issue has been resolved and audit logs and usage data are fully up to date. All previously delayed records have been backfilled. No data was lost at any point during this incident.\n\n\nIncident Start Time: Aug 5, 2026, 15:37 UTC\nIncident End Time: Aug 11, 2026, 14:47 UTC",
"name": "Delayed audit logs and usage data in AWS US West",
"timestamp": "Aug \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e18:37\u003c/var\u003e - Aug \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e17:32\u003c/var\u003e UTC"
},
{
"code": "33zcbl39ns0z",
"impact": "none",
"message": "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.\n\nImpacted Cloud Regions \u0026amp; Services: Sigma users hosted on AWS US-West-2 using materialization\n\nUser Experience: Customers using materializations on AWS US-West-2 should no longer see the previously reported table accumulation.\n\nIncident Start Time: Approximately August 3, 2026, at 2:44 PM UTC\nIncident End Time: Approximately August 5, 2026, at 02:40 AM UTC",
"name": "Materialization cleanup delayed for Sigma users on AWS US-West-2",
"timestamp": "Aug \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e23:58\u003c/var\u003e - Aug \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e03:19\u003c/var\u003e UTC"
},
{
"code": "ts1g9646dwy9",
"impact": "none",
"message": "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.\n\nImpacted Cloud Regions \u0026amp; Services: All Regions\nUser Experience: Workbooks should now load normally after a hard refresh or browser restart.\n\nIncident Start Time: Approximately 08:30 UTC, August 4, 2026\nIncident End Time: Approximately 10:42 UTC, August 4, 2026",
"name": "Workbooks containing Snowflake Semantic Views fail to load",
"timestamp": "Aug \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e10:37\u003c/var\u003e - \u003cvar data-var='time'\u003e11:11\u003c/var\u003e UTC"
},
{
"code": "l7pn7gk76l0z",
"impact": "none",
"message": "Resolved - Query Timeouts for Snowflake Connections\n\nSnowflake has updated their status page to indicate that a fix was pushed to resolve the previously reported incident.\nHence, based on Snowflake’s latest status update, this issue has now been resolved.\n\nIncident end time: 16:36 UTC August 03, 2026",
"name": "Query Timeouts for Snowflake Connections",
"timestamp": "Aug \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e14:55\u003c/var\u003e - \u003cvar data-var='time'\u003e18:07\u003c/var\u003e UTC"
}
],
"name": "August",
"year": 2026
},
{
"incidents": [],
"name": "July",
"year": 2026
}
],
"start_time": "2026-07-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-06-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "740bw4v8050m",
"impact": "minor",
"message": "The mitigation measures have proven effective, and our monitoring indicates that this issue is resolved. We will continue monitoring closely this incident for any recurrence in the next hours. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in the coming days.\n\nImpacted Cloud Regions \u0026amp; Services: AWS US-WEST-2\n\nUser Experience: We expect users to no longer experience delayed scheduled exports and materializations. Users should have received previously delayed scheduled exports and delayed materializations should have ran. \n\nIncident Start Time: Approximately 05:00 UTC June 24, 2026\n\nIncident End Time: Approximately 17:30 UTC June 24, 2026",
"name": "Scheduled exports and materializations are delayed",
"timestamp": "Jun \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e13:30\u003c/var\u003e - \u003cvar data-var='time'\u003e19:35\u003c/var\u003e UTC"
},
{
"code": "f8h23zwcrs78",
"impact": "minor",
"message": "We identified a higher than usual spike in CPU usage during the timeframe below on our AWS instance. We scaled our infrastructure accordingly to accommodate this and the mitigation measures have proven effective, and our monitoring indicates that this issue is resolved.\n\nWe will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in the coming days.\n\nImpacted Cloud Regions \u0026amp; Services: AWS US-WEST-2\n\nUser Experience: We expect users to no longer experience workbook errors.\n\nIncident Start Time: Approximately 17:30 UTC June 22, 2026\nIncident End Time: Approximately 18:14 UTC June 22, 2026",
"name": "High errors showing being displayed in workbooks",
"timestamp": "Jun \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e18:11\u003c/var\u003e - \u003cvar data-var='time'\u003e18:52\u003c/var\u003e UTC"
}
],
"name": "June",
"year": 2026
},
{
"incidents": [
{
"code": "2dy3wpg31fjx",
"impact": "none",
"message": "This incident has been resolved.",
"name": "Errors on pivot table export",
"timestamp": "May \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e01:21\u003c/var\u003e - \u003cvar data-var='time'\u003e13:49\u003c/var\u003e UTC"
}
],
"name": "May",
"year": 2026
},
{
"incidents": [
{
"code": "pc8bws5yny7m",
"impact": "none",
"message": "This incident has been resolved.",
"name": "Permission Denied Errors on Elements Sourced from Custom SQL Tables",
"timestamp": "Apr \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e23:30\u003c/var\u003e - \u003cvar data-var='time'\u003e23:39\u003c/var\u003e UTC"
},
{
"code": "tthws4yfsrk2",
"impact": "none",
"message": "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.\n\nImpacted Cloud Regions \u0026amp; Services: All regions\n\nUser Experience: Google Sheets integration and related exports should now be functioning as expected.\n\nIncident Start Time: Approximately 19:15 UTC March 31, 2026\n\nIncident End Time: Approximately 22:12 UTC March 31, 2026",
"name": "Experiencing issues with Google sheets Integration",
"timestamp": "Mar \u003cvar data-var='date'\u003e31\u003c/var\u003e, \u003cvar data-var='time'\u003e21:08\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e03:30\u003c/var\u003e UTC"
}
],
"name": "April",
"year": 2026
}
],
"start_time": "2026-04-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-03-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "t4509ttw587q",
"impact": "major",
"message": "Issue with Burst Email Exports are resolved\n\nWe previously re-enabled Burst Email Exports after deploying a fix for the issue impacting this feature. Since re-enabling, our team has closely monitored system performance and error rates, and we have not observed any recurring problems.\n\nAt this time, the incident is considered fully resolved, and Burst Email Exports are operating as expected.\n\nIf you encounter any new or unexpected behavior with Burst Email Exports, please contact our support team via live chat so we can investigate promptly.",
"name": "Issue with Burst email exports are resolved",
"timestamp": "Mar \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e20:50\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e17:31\u003c/var\u003e UTC"
}
],
"name": "March",
"year": 2026
},
{
"incidents": [],
"name": "February",
"year": 2026
},
{
"incidents": [
{
"code": "b98pjtb6rfr6",
"impact": "major",
"message": "Our 3rd party vendor has updated their incident marking it as now resolved. We have confirmed that our chat support system is fully operational and our technical support engineers are available there. \nWe will mark this incident as resolved as well.\n\nAgain we apologize for the inconvenience this has caused, and appreciate your understanding.",
"name": "Chat Support experiencing 3rd party outage",
"timestamp": "Jan \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e20:33\u003c/var\u003e - \u003cvar data-var='time'\u003e22:23\u003c/var\u003e UTC"
},
{
"code": "ys5j4xh9xxhs",
"impact": "major",
"message": "This incident has been resolved. The queued tasks should start recovering automatically",
"name": "Scheduled Backend Tasks not running on AWS US",
"timestamp": "Jan \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e21:38\u003c/var\u003e - \u003cvar data-var='time'\u003e23:33\u003c/var\u003e UTC"
}
],
"name": "January",
"year": 2026
}
],
"start_time": "2026-01-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2025-12-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "mc5vwfcfymr7",
"impact": "minor",
"message": "We have identified that PDF export failures were impacting a small percentage of our users. We applied mitigation steps and our monitoring indicates that this issue has been resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in the coming days.\n\nImpacted Cloud Regions \u0026amp; Services: AWS US and GCP US regions, PDF Exports \n\nUser Experience: We expect impacted users' scheduled exports to succeed without the errors seen previously\n\nIncident Start Time: Approximately 13:00 UTC on 2025-12-11\n\nIncident End Time: Approximately 17:50 UTC on 2025-12-11",
"name": "Degraded performance on PDF Exports",
"timestamp": "Dec \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e16:21\u003c/var\u003e - \u003cvar data-var='time'\u003e18:17\u003c/var\u003e UTC"
},
{
"code": "b6nwqzw4qkqv",
"impact": "none",
"message": "At 08:56 UTC Cloudflare's scheduled maintenance to their Web Application Firewalls failed and an incident was declared. At 09:12 UTC a fix was deployed and traffic was restored.\n\nSigma's service was impacted by this incident, as this did not allow traffic to reach our servers.\n\nOur internal monitoring matches the incident timeline and indicated that customers may have experienced failures when using our services during this brief incident.",
"name": "Sigma Service Disruption Due to Cloudflare Incident",
"timestamp": "Dec \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e - \u003cvar data-var='time'\u003e09:00\u003c/var\u003e UTC"
}
],
"name": "December",
"year": 2025
},
{
"incidents": [],
"name": "November",
"year": 2025
},
{
"incidents": [
{
"code": "6qf0t4hbgfnr",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Service disruption affecting Azure-hosted customers",
"timestamp": "Oct \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e16:57\u003c/var\u003e - \u003cvar data-var='time'\u003e22:29\u003c/var\u003e UTC"
},
{
"code": "28rrh3vnlwy3",
"impact": "none",
"message": "Starting at 7:11 UTC, AWS reported increased error rates and latencies for multiple services in the US-EAST-1 Region. At 10:35 UTC, AWS declared the incident in the US-EAST-1 region mitigated. While Sigma's service was not impacted by the incident, third party services that Sigma uses were impacted. Customers may have experienced intermittent delays or failures when accessing or using cloud data warehouse services during the incident. Contacting Sigma Support via Live Chat or email was disrupted during the incident.\n\nIncident Start Time: 7:11 UTC\nIncident End Time: 10:35 UTC",
"name": "Error rates and latencies in the AWS US-EAST-1 Region impacting third party services",
"timestamp": "Oct \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e07:00\u003c/var\u003e - \u003cvar data-var='time'\u003e07:00\u003c/var\u003e UTC"
}
],
"name": "October",
"year": 2025
}
],
"start_time": "2025-10-01T00:00:00Z",
"time_zone": "UTC"
}
]
}