Snapshot 311520

Document
Registry listing
URL
https://status.getdbt.com/api/v2/incidents.json
Fetched
HTTP status
200
Content type
application/json
Fetch mode
api
Size
57733 bytes
SHA-256 (raw)
7ae35f53b020fb1347c61cae20ae9733fd77e5d167fc7bd8832a5afb791a8854
SHA-256 (normalized text)
a361407fe4bdaa61691f249be584211604a568fda9b8c8e045feee24871bafe6

Raw (normalized text)

Scripts and page chrome removed; this is what change detection compares.

{
  "incidents": [
    {
      "created_at": "2026-11-20T05:25:04Z",
      "id": "01M7VPMP7Y4CH4ZXF3S6ZDN5MR",
      "impact": "major",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally as of 04:50:45 UTC. Between 03:20 UTC and 04:50:45 UTC an issue with the Semantic Layer Gateway and scheduled job dispatch authentication resulted in job run failures. Affected runs can be retried and are expected to succeed. We have put measures in place to prevent a recurrence and the affected systems have returned to normal. Please contact Support via email [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.",
          "created_at": "2026-11-20T05:55:33Z",
          "display_at": "2026-11-20T05:55:33Z",
          "id": "01M7VRCGHQ8CA4T3CD8Z8K978T",
          "incident_id": "01M7VPMP7Y4CH4ZXF3S6ZDN5MR",
          "status": "resolved",
          "updated_at": "2026-11-20T05:55:33Z"
        },
        {
          "body": "We’re investigating an issue with the Semantic Layer Gateway and scheduled job dispatch that is causing job run failures due to authentication errors. This issue has been occurring anytime after 03:20 UTC on November 20, 2026. The team is working on a resolution and we will provide updates as soon as new information becomes available.",
          "created_at": "2026-11-20T05:25:04Z",
          "display_at": "2026-11-20T05:25:04Z",
          "id": "01M7VPMP7Y1ZP4Z4N2NH2A8X5X",
          "incident_id": "01M7VPMP7Y4CH4ZXF3S6ZDN5MR",
          "status": "investigating",
          "updated_at": "2026-11-20T05:25:04Z"
        }
      ],
      "name": "Authentication Errors Affecting Semantic Layer and Scheduled Runs",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-20T05:55:33Z",
      "status": "resolved",
      "updated_at": "2026-11-20T05:55:33Z"
    },
    {
      "created_at": "2026-11-19T09:08:17Z",
      "id": "01M7SH0PTWMXV432VMWE60Q180",
      "impact": "major",
      "incident_updates": [
        {
          "body": "The issue has been resolved. An issue affecting SSO sign-in and password reset caused login failures for a number of users. This has been fixed, and we’ve put measures in place to prevent a recurrence. If you’re still unable to sign in, please contact Support at [support@getdbt.com](mailto:support@getdbt.com).",
          "created_at": "2026-11-19T23:52:12Z",
          "display_at": "2026-11-19T23:52:12Z",
          "id": "01M7V3K6F2C5MN5B0ZWGT0SF55",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "resolved",
          "updated_at": "2026-11-19T23:52:12Z"
        },
        {
          "body": "We’ve deployed a fix across all affected regions, and users who reset their password can now sign in normally. We’re monitoring to make sure sign-in stays stable. No action is needed on your side. If you still can’t sign in, contact [support@getdbt.com](mailto:support@getdbt.com) and include the time of your attempt.",
          "created_at": "2026-11-19T21:51:42Z",
          "display_at": "2026-11-19T21:51:42Z",
          "id": "01M7TWPHF29R04AWYTKDQZ9MG5",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "monitoring",
          "updated_at": "2026-11-19T21:51:42Z"
        },
        {
          "body": "We’re reopening this incident. SSO and email/password sign-ins are working normally for most users. However, some users may be unable to sign in after resetting their password.\n\nWe’ve identified the cause and are deploying a fix across affected regions. We’ll share another update as the rollout progresses.\n\nIf you’re unable to sign in, contact [support@getdbt.com](mailto:support@getdbt.com) and include the time of your attempt and whether you recently reset your password.",
          "created_at": "2026-11-19T19:11:37Z",
          "display_at": "2026-11-19T19:11:37Z",
          "id": "01M7TKHE808JYTRP2K6Y8K0JHZ",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "monitoring",
          "updated_at": "2026-11-19T19:11:37Z"
        },
        {
          "body": "This incident has been resolved. Between about 08:03 and 13:15 UTC on 19 November, customers  were unable to sign in to dbt platform through SSO or enterprise login. SSO sign-in, including logins started from your identity provider, has been fully restored, and we have confirmed that it has been working normally since then.\n\nNo action is needed on your side. If you still have trouble signing in, please contact [support@getdbt.com](mailto:support@getdbt.com).\n\nWe apologise for the disruption. We will share a root cause analysis with affected customers.",
          "created_at": "2026-11-19T14:46:38Z",
          "display_at": "2026-11-19T14:46:38Z",
          "id": "01M7T4C7EMP5A5N6GN1SK84B06",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "resolved",
          "updated_at": "2026-11-19T14:46:38Z"
        },
        {
          "body": "We have applied a fix for the remaining affected customers, and SSO sign-in has now been restored for customers. This includes logins started from your identity provider. We are continuing to monitor to make sure sign-in stays stable. No action is needed on your side.\n\nIf you still can’t sign in through SSO, please try a private browser window. If it still fails, contact [support@getdbt.com](mailto:support@getdbt.com) and include the time of your attempt.",
          "created_at": "2026-11-19T13:19:29Z",
          "display_at": "2026-11-19T13:19:29Z",
          "id": "01M7SZCNN5K9KE8PMHPY2PTD2B",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "monitoring",
          "updated_at": "2026-11-19T13:19:29Z"
        },
        {
          "body": "More affected customers can now sign in through SSO again, and we are continuing to restore access for the remaining customers. No action is needed on your side.",
          "created_at": "2026-11-19T12:29:10Z",
          "display_at": "2026-11-19T12:29:10Z",
          "id": "01M7SWGH072PZZQFXA660402TP",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "monitoring",
          "updated_at": "2026-11-19T12:30:03Z"
        },
        {
          "body": "We have started restoring SSO sign-in, and some affected customers can now log in again. We are continuing to restore access for the remaining customers. No action is needed on your side.\n\nIf you still can’t sign in through SSO, please try again shortly. We will post another update by 13:00 UTC, or sooner if things change.",
          "created_at": "2026-11-19T12:27:02Z",
          "display_at": "2026-11-19T12:27:02Z",
          "id": "01M7SWCM963RRFSJT2M63WEDKH",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "monitoring",
          "updated_at": "2026-11-19T12:27:02Z"
        },
        {
          "body": "We are continuing to work on restoring SSO sign-in for affected customers. No action is needed on your side.\n\nWe will post another update by 12:15 UTC, or sooner if things change.",
          "created_at": "2026-11-19T11:38:47Z",
          "display_at": "2026-11-19T11:38:47Z",
          "id": "01M7SSM8FVH58ECQE15E78ZVH0",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "identified",
          "updated_at": "2026-11-19T11:38:47Z"
        },
        {
          "body": "We have identified the cause of the SSO sign-in failures affecting customers, which began at about 08:03 UTC on 19 November. Users signing in through SSO or enterprise login, including logins started from your identity provider, may still see a “client not found” or “Server error” page.\n\nA change to our sign-in configuration disconnected customer SSO connections. Our engineers are now restoring those connections on each affected instance. Customers on other regions are not affected.\n\nWe will post another update by 11:30 UTC, or sooner if things change.",
          "created_at": "2026-11-19T10:45:01Z",
          "display_at": "2026-11-19T10:45:01Z",
          "id": "01M7SPHSZBSF70V5D569GS00HW",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "identified",
          "updated_at": "2026-11-19T10:45:01Z"
        },
        {
          "body": "We are continuing to investigate SSO sign-in failures affecting customers. Since about 08:03 UTC on 19 November, users signing in through SSO or enterprise login may see a “client not found” or “Server error” page.\n\nOur engineering teams are actively working on this, and we have paused related changes to our sign-in service while we investigate. Customers on other regions are not affected.\n\nWe will post another update by 10:45 UTC, or sooner if things change.",
          "created_at": "2026-11-19T10:04:36Z",
          "display_at": "2026-11-19T10:04:36Z",
          "id": "01M7SM7T522HVENTJVSBM8ZWQ4",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "investigating",
          "updated_at": "2026-11-19T10:05:06Z"
        },
        {
          "body": "We are investigating reports that some users can’t sign in to dbt platform through SSO (enterprise login). Since about 08:00 UTC on 19 November 2026, affected users may see a “client not found” or “Server error” page when signing in. Scheduled jobs and other running processes are not known to be affected.\n\nOur team is working on this now. We will post another update by 10:00 UTC, or sooner if things change.",
          "created_at": "2026-11-19T09:08:17Z",
          "display_at": "2026-11-19T09:08:17Z",
          "id": "01M7SH0PTWVZKQMFSVNGF417FQ",
          "incident_id": "01M7SH0PTWMXV432VMWE60Q180",
          "status": "investigating",
          "updated_at": "2026-11-19T09:08:17Z"
        }
      ],
      "name": "Some users unable to log in with SSO",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-19T14:46:38Z",
      "status": "resolved",
      "updated_at": "2026-11-19T23:52:12Z"
    },
    {
      "created_at": "2026-11-20T00:36:57Z",
      "id": "01M7V654RPH6ZQD194QV2PKHCA",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally as of 22:38 UTC. Between 22:05 UTC and 22:38 UTC an issue with managed GitHub repo integration resulted in failures when creating a new managed repo or downloading the archive for an existing managed repo. We have put measures in place to prevent a recurrence and the managed GitHub repo integration has returned to normal. Please contact Support via email [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.",
          "created_at": "2026-11-20T00:36:57Z",
          "display_at": "2026-11-19T22:05:00Z",
          "id": "01M7V654RP3NH7T3RJDRNRK55D",
          "incident_id": "01M7V654RPH6ZQD194QV2PKHCA",
          "status": "resolved",
          "updated_at": "2026-11-20T00:36:57Z"
        }
      ],
      "name": "Managed GitHub Repo Creation/Download Failures",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-19T22:05:00Z",
      "status": "resolved",
      "updated_at": "2026-11-20T00:36:57Z"
    },
    {
      "created_at": "2026-11-18T20:22:11Z",
      "id": "01M7R55XE91D0D5PW9SNS1W3FF",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "This incident has been resolved. Some customers experienced longer than usual job run times. We have taken steps to mitigate the impact for affected accounts. If you are still seeing longer than usual run times, please contact [support@getdbt.com](mailto:support@getdbt.com) with your account ID and example run IDs.",
          "created_at": "2026-11-18T21:56:11Z",
          "display_at": "2026-11-18T21:56:11Z",
          "id": "01M7RAJ1MA3ANTCQDSDQYTQ0H6",
          "incident_id": "01M7R55XE91D0D5PW9SNS1W3FF",
          "status": "resolved",
          "updated_at": "2026-11-18T21:56:11Z"
        },
        {
          "body": "We’ve identified an issue with job runs that is causing longer than usual run times. BigQuery jobs are particularly affected. The team is working on a resolution and we will provide updates as soon as new information becomes available.\n\nIf you are experiencing longer than usual run times, please reach out to [support@getdbt.com](mailto:support@getdbt.com) with your account ID and example run IDs.",
          "created_at": "2026-11-18T20:24:25Z",
          "display_at": "2026-11-18T20:24:25Z",
          "id": "01M7R5A0GPH11S4F8DKDK9CMSY",
          "incident_id": "01M7R55XE91D0D5PW9SNS1W3FF",
          "status": "identified",
          "updated_at": "2026-11-18T20:26:25Z"
        },
        {
          "body": "We’ve identified an issue with job runs that is causing longer than usual run times. BigQuery jobs are particularly affected. The team is working on a resolution and we will provide updates as soon as new information becomes available.\n\nIf you are experiencing longer than usual run times, please reach out to [support@getdbt.com](mailto:support@getdbt.com) with your account ID and example run IDs.",
          "created_at": "2026-11-18T20:22:11Z",
          "display_at": "2026-11-18T20:22:11Z",
          "id": "01M7R55XE9BKD5DG3S21BC92FA",
          "incident_id": "01M7R55XE91D0D5PW9SNS1W3FF",
          "status": "identified",
          "updated_at": "2026-11-18T20:22:11Z"
        }
      ],
      "name": "Increased job run times for some accounts",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-18T21:56:11Z",
      "status": "resolved",
      "updated_at": "2026-11-18T21:56:11Z"
    },
    {
      "created_at": "2026-11-16T19:15:21Z",
      "id": "01M7JWJ3NK850RQ3TXVSAPZH8B",
      "impact": "major",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems have been functioning normally since 21:30 UTC. Between 20:41 UTC and 21:30 UTC, an issue with dbt State caused some scheduled jobs to fail with the error “Cannot determine the account ID. Please make sure dbt State is enabled in your account.” We have put measures in place to prevent a recurrence, and jobs have returned to normal.\n\nIf you disabled dbt State on your jobs as a workaround, you can re-enable it. If you continue to experience job failures and are unsure of the root cause, please contact Support at [support@getdbt.com](mailto:support@getdbt.com).",
          "created_at": "2026-11-16T23:52:11Z",
          "display_at": "2026-11-16T23:52:11Z",
          "id": "01M7KCCZZZG0HFWHHZB2XSDMV9",
          "incident_id": "01M7JWJ3NK850RQ3TXVSAPZH8B",
          "status": "resolved",
          "updated_at": "2026-11-16T23:52:11Z"
        },
        {
          "body": "We have deployed a fix for dbt State that was causing jobs to fail. \n\nAffected runs were failing with the error “Cannot determine the account ID. Please make sure dbt State is enabled in your account.”\n\nRuns on previously failing accounts are now completing successfully. We are continuing to monitor.\n\nIf you disabled dbt State on your jobs as a workaround, you can re-enable it. If you still see this error after re-enabling, please contact support.",
          "created_at": "2026-11-16T22:12:05Z",
          "display_at": "2026-11-16T22:12:05Z",
          "id": "01M7K6NQ11P1MBS94BS102QQ0J",
          "incident_id": "01M7JWJ3NK850RQ3TXVSAPZH8B",
          "status": "monitoring",
          "updated_at": "2026-11-16T22:12:05Z"
        },
        {
          "body": "We have identified an issue causing some scheduled dbt jobs to fail for customers using dbt State. Affected runs fail with the error “Cannot determine the account ID. Please make sure dbt State is enabled in your account.” Our team has been alerted and is actively working to resolve the issue.\n\nUsers can resolve this issue by temporarily disabling dbt State on their jobs.",
          "created_at": "2026-11-16T20:27:14Z",
          "display_at": "2026-11-16T20:27:14Z",
          "id": "01M7K0NQ89B02HRB1SJGWBW6EJ",
          "incident_id": "01M7JWJ3NK850RQ3TXVSAPZH8B",
          "status": "identified",
          "updated_at": "2026-11-16T20:27:14Z"
        },
        {
          "body": "We are currently investigating an issue causing some scheduled dbt jobs to fail for customers using dbt State. Affected runs fail with the error “Cannot determine the account ID. Please make sure dbt State is enabled in your account.” Our team has been alerted and is actively working to understand the scope and resolve the issue",
          "created_at": "2026-11-16T19:15:21Z",
          "display_at": "2026-11-16T19:15:21Z",
          "id": "01M7JWJ3NK25SCR0HQYSSP9P0E",
          "incident_id": "01M7JWJ3NK850RQ3TXVSAPZH8B",
          "status": "investigating",
          "updated_at": "2026-11-16T19:15:21Z"
        }
      ],
      "name": "dbt Jobs failing for some accounts with dbt State",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-16T23:52:11Z",
      "status": "resolved",
      "updated_at": "2026-11-16T23:52:11Z"
    },
    {
      "created_at": "2026-11-16T19:47:27Z",
      "id": "01M7JYCWX3RFDNYCE0M6HMH5Q4",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally as of 19:48 UTC. Customers were reporting 500 errors when attempting to access dbt Studio or when linking Github accounts due to an external issue with IP allowlist rules. Please contact Support via email [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.",
          "created_at": "2026-11-16T20:37:18Z",
          "display_at": "2026-11-16T20:37:18Z",
          "id": "01M7K18603J4KTCV9RSP7NX9DV",
          "incident_id": "01M7JYCWX3RFDNYCE0M6HMH5Q4",
          "status": "resolved",
          "updated_at": "2026-11-16T20:37:18Z"
        },
        {
          "body": "We’re investigating an issue with the Github integration that is causing 500 errors when attempting to access dbt Studio or linking Github accounts. The team is working on a resolution and we will provide updates as soon as new information becomes available.",
          "created_at": "2026-11-16T19:47:27Z",
          "display_at": "2026-11-16T19:47:27Z",
          "id": "01M7JYCWX3P6BP0KX02YK5C4C0",
          "incident_id": "01M7JYCWX3RFDNYCE0M6HMH5Q4",
          "status": "investigating",
          "updated_at": "2026-11-16T19:47:27Z"
        }
      ],
      "name": "500 errors when attempting to access Studio and link Github account",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-16T20:37:18Z",
      "status": "resolved",
      "updated_at": "2026-11-16T20:37:19Z"
    },
    {
      "created_at": "2026-11-14T06:58:52Z",
      "id": "01M7CDM4DQN2Y0Z9X376CVWACB",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause. ",
          "created_at": "2026-11-14T07:56:28Z",
          "display_at": "2026-11-14T07:56:28Z",
          "id": "01M7CGXKTXD8MFEZPYSYBYQPCK",
          "incident_id": "01M7CDM4DQN2Y0Z9X376CVWACB",
          "status": "resolved",
          "updated_at": "2026-11-14T07:56:28Z"
        },
        {
          "body": "We have released a fix for the issue with the spark-utils package. Version 0.3.5 is now available on the dbt Hub and restores the previous working behaviour.\n\nProjects that resolve the latest version of spark-utils will pick up 0.3.5 automatically on their next run, and no action is required. If your `package-lock.yml` was updated to spark-utils 0.3.4, run `dbt deps --upgrade` to update it, or pin spark-utils to 0.3.5.\n\nWe are continuing to monitor. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues.",
          "created_at": "2026-11-14T07:30:06Z",
          "display_at": "2026-11-14T07:30:06Z",
          "id": "01M7CFDAM39PR4W7ZZH0Y1736H",
          "incident_id": "01M7CDM4DQN2Y0Z9X376CVWACB",
          "status": "monitoring",
          "updated_at": "2026-11-14T07:30:06Z"
        },
        {
          "body": "We have identified an issue with a new release (`0.3.4`) of the dbt package `spark-utils`. Jobs fail with the following compilation error:\n`In dispatch: No macro named 'assert_not_null' found within namespace: 'dbt'`\nThis affects projects that depend on `spark-utils`, either directly or through another package (for example, Fivetran source packages), on adapters other than Databricks/Spark. Projects that use a `package-lock` file are not affected unless the lock file was updated after the new release.\nAs a workaround, pin `spark-utils` to version `0.3.3` in your `packages.yml`, then run `dbt deps`. We are working on a fix to resolve the issue and will provide an update as soon as it is available. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues.",
          "created_at": "2026-11-14T06:58:52Z",
          "display_at": "2026-11-14T06:58:52Z",
          "id": "01M7CDM4DQZGD0ZMS7GJCT99P7",
          "incident_id": "01M7CDM4DQN2Y0Z9X376CVWACB",
          "status": "identified",
          "updated_at": "2026-11-14T06:58:52Z"
        }
      ],
      "name": "Update to spark-utils package causing job run failures",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-14T07:56:28Z",
      "status": "resolved",
      "updated_at": "2026-11-14T07:56:28Z"
    },
    {
      "created_at": "2026-11-13T15:15:26Z",
      "id": "01M7AQMMQ8ZCVHECJZH83E7HPQ",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "This incident has been resolved. Between approximately 10:00 and 16:40 UTC on 13 November, some Wizard agent conversations using Anthropic models returned an error on every new message. We deployed a fix to address the issue. We apologise for the disruption. A post-incident review is underway.",
          "created_at": "2026-11-13T16:57:32Z",
          "display_at": "2026-11-13T16:57:32Z",
          "id": "01M7AXFK4EYTX1GN6VY34AJ97P",
          "incident_id": "01M7AQMMQ8ZCVHECJZH83E7HPQ",
          "status": "resolved",
          "updated_at": "2026-11-13T16:57:32Z"
        },
        {
          "body": "A fix has been deployed and we are monitoring the results. If you continue to experience issues, please contact support. Next update by 20:15 UTC or sooner if the status changes.",
          "created_at": "2026-11-13T16:15:41Z",
          "display_at": "2026-11-13T16:15:41Z",
          "id": "01M7AV2ZF6AFW1YT5PCTKTA1GN",
          "incident_id": "01M7AQMMQ8ZCVHECJZH83E7HPQ",
          "status": "monitoring",
          "updated_at": "2026-11-13T16:15:41Z"
        },
        {
          "body": "We have identified the cause of the current issue affecting Wizard agent conversations. Some conversations using Anthropic models may return an error on every new message. Our team is actively working on a fix. In the meantime, switching to an OpenAI model restores functionality. You can start a new conversation, or continue an affected conversation after switching the model.",
          "created_at": "2026-11-13T15:15:26Z",
          "display_at": "2026-11-13T15:15:26Z",
          "id": "01M7AQMMQ8R8ZZR4EHQRDVJ5Z2",
          "incident_id": "01M7AQMMQ8ZCVHECJZH83E7HPQ",
          "status": "identified",
          "updated_at": "2026-11-13T15:15:26Z"
        }
      ],
      "name": "Wizard agent conversations returning errors",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-13T16:57:32Z",
      "status": "resolved",
      "updated_at": "2026-11-13T16:57:32Z"
    },
    {
      "created_at": "2026-11-11T18:39:26Z",
      "id": "01M75YGQW5MEDZ0Q2DW8QSJ7EY",
      "impact": "none",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally as of 17:47 UTC. Between 11:24 UTC and 17:47 UTC an issue with a long running CLI worker node resulted in indefinite load times in the IDE. We have put measures in place to prevent a recurrence and IDE behavior has returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause. ",
          "created_at": "2026-11-11T18:47:35Z",
          "display_at": "2026-11-11T18:47:35Z",
          "id": "01M75YZNHWR855J23B7X1CJ3BW",
          "incident_id": "01M75YGQW5MEDZ0Q2DW8QSJ7EY",
          "status": "resolved",
          "updated_at": "2026-11-11T18:47:35Z"
        }
      ],
      "name": "Cloud IDE sessions failed to load",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-11T18:47:35Z",
      "status": "resolved",
      "updated_at": "2026-11-11T18:47:35Z"
    },
    {
      "created_at": "2026-11-10T07:34:44Z",
      "id": "01M7262YDV1BAB961R1MYB2D6C",
      "impact": "none",
      "incident_updates": [
        {
          "body": "This incident has been resolved. Between 02:05 and 04:13 UTC on November 10, 2026, the dbt State service had intermittent availability problems and timeouts. During this window, some dbt platform runs couldn’t reach dbt State and ran without it. Those runs completed normally and produced correct results, but they didn’t get the State-based optimizations, such as reusing prior results and making clone decisions. As a result, some runs may have taken longer than usual. Apologies for the inconveniences caused. Please contact us at support@getdbt.com with any questions or concerns.",
          "created_at": "2026-11-10T07:34:44Z",
          "display_at": "2026-11-10T02:05:00Z",
          "id": "01M7262YDVP87YA9Z67AKBAMBA",
          "incident_id": "01M7262YDV1BAB961R1MYB2D6C",
          "status": "resolved",
          "updated_at": "2026-11-10T07:39:07Z"
        }
      ],
      "name": "Degraded run performance due to dbt State service disruption",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-10T02:05:00Z",
      "status": "resolved",
      "updated_at": "2026-11-10T07:34:44Z"
    },
    {
      "created_at": "2026-11-04T20:00:02Z",
      "id": "01M6M2B9R2AN31M69SFX4DFCS5",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally as of 20:57 UTC. We have put measures in place to prevent a recurrence and the API has returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com) if you continue to experience delays and are unsure of the root cause.",
          "created_at": "2026-11-04T23:24:40Z",
          "display_at": "2026-11-04T23:24:40Z",
          "id": "01M6ME1ZR8X7QJVEEBCJYASGG0",
          "incident_id": "01M6M2B9R2AN31M69SFX4DFCS5",
          "status": "resolved",
          "updated_at": "2026-11-04T23:24:40Z"
        },
        {
          "body": "We have deployed a fix for the issue affecting the Jobs page, Project and Environment pages, and run logs, and these pages returned to normal as of 2026-11-04 20:57 UTC. We are continuing to monitor. Some scheduled and API-triggered runs during the incident did not start and may need to be re-triggered manually.",
          "created_at": "2026-11-04T21:25:37Z",
          "display_at": "2026-11-04T20:57:00Z",
          "id": "01M6M780XSMM3MCRWW0AVK1NMK",
          "incident_id": "01M6M2B9R2AN31M69SFX4DFCS5",
          "status": "monitoring",
          "updated_at": "2026-11-04T23:15:22Z"
        },
        {
          "body": "We have identified an issue with the Jobs page, Project and Environment pages, and run logs that was caused by a recent deployment. Some accounts may see an empty jobs list or errors when loading these pages. Scheduled jobs continue to run as expected and there is no impact to pipelines or data. A fix is being implemented and we will provide an update shortly.",
          "created_at": "2026-11-04T20:44:55Z",
          "display_at": "2026-11-04T20:44:55Z",
          "id": "01M6M4XFDV95K1SBYB8C9JP4RH",
          "incident_id": "01M6M2B9R2AN31M69SFX4DFCS5",
          "status": "identified",
          "updated_at": "2026-11-04T20:44:55Z"
        },
        {
          "body": "We began investigating at 2026-11-04 19:06 UTC an issue affecting the Jobs page, Project and Environment pages, and run logs for some accounts. Affected users may see an empty jobs list or an error when loading these pages, and may be unable to view, edit, create, or manually trigger jobs. Scheduled jobs continue to run as expected and there is no impact to pipelines or data. The team is working on a resolution and we will provide updates as soon as new information becomes available.",
          "created_at": "2026-11-04T20:00:02Z",
          "display_at": "2026-11-04T19:06:00Z",
          "id": "01M6M2B9R2089K4481TEZ3ZS7K",
          "incident_id": "01M6M2B9R2AN31M69SFX4DFCS5",
          "status": "investigating",
          "updated_at": "2026-11-04T23:12:13Z"
        }
      ],
      "name": "Jobs list and Environment pages failing to load ",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-04T23:24:40Z",
      "status": "resolved",
      "updated_at": "2026-11-04T23:24:40Z"
    },
    {
      "created_at": "2026-11-04T12:50:16Z",
      "id": "01M6K9RC8K3RCZZ9FBVSZCNYC4",
      "impact": "major",
      "incident_updates": [
        {
          "body": "This incident has been resolved. Between 09:37 and 11:23 UTC, an incident at GitHub caused some job runs and dbt Studio git actions to fail with \"Permission denied (publickey)\" for projects that use a dbt-managed repository or connect to GitHub with a deploy key. Git operations have been stable since GitHub's fix. Any job run that failed with this error during that window can be re-run.",
          "created_at": "2026-11-04T12:51:59Z",
          "display_at": "2026-11-04T11:50:00Z",
          "id": "01M6K9VGJZ4HTZFY41VAC08NNJ",
          "incident_id": "01M6K9RC8K3RCZZ9FBVSZCNYC4",
          "status": "resolved",
          "updated_at": "2026-11-04T13:37:56Z"
        },
        {
          "body": "GitHub has mitigated the issue, and we're no longer seeing these errors in job runs or dbt Studio. We're monitoring to confirm things stay stable. Job runs that failed with this error can be re-run.",
          "created_at": "2026-11-04T12:51:12Z",
          "display_at": "2026-11-04T11:30:00Z",
          "id": "01M6K9T3A4PYEQK837D58S3S0A",
          "incident_id": "01M6K9RC8K3RCZZ9FBVSZCNYC4",
          "status": "monitoring",
          "updated_at": "2026-11-04T13:37:44Z"
        },
        {
          "body": "We've identified the cause as an incident at GitHub affecting Git operations (\u003chttps://www.githubstatus.com/incidents/smtdswd1h2w4\u003e). Until GitHub resolves it, job runs and dbt Studio git actions may fail intermittently with \"Permission denied (publickey)\" for projects that use a dbt-managed repository or connect to GitHub with a deploy key. Accounts with repository caching enabled may see affected runs continue from the cached copy of the repository. We'll provide another update as GitHub makes progress.",
          "created_at": "2026-11-04T12:50:55Z",
          "display_at": "2026-11-04T10:07:00Z",
          "id": "01M6K9SJK9X6HK7MQZ8Z1GRB1V",
          "incident_id": "01M6K9RC8K3RCZZ9FBVSZCNYC4",
          "status": "identified",
          "updated_at": "2026-11-04T13:37:29Z"
        },
        {
          "body": "We're investigating an issue with git operations that is causing job runs to fail at the \"Clone git repository\" step and dbt Studio git actions to fail with \"Permission denied (publickey)\". This is impacting Scheduled Jobs and the IDE for projects that use a dbt-managed repository or connect to GitHub with a deploy key, across multi-tenant regions on AWS, Azure and GCP, anytime after 09:37 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Projects that connect through the native GitHub integration or use other git providers are not impacted and should be running as expected.",
          "created_at": "2026-11-04T12:50:16Z",
          "display_at": "2026-11-04T09:37:00Z",
          "id": "01M6K9RC8KCM5J9GYEH9AFBGY1",
          "incident_id": "01M6K9RC8K3RCZZ9FBVSZCNYC4",
          "status": "investigating",
          "updated_at": "2026-11-04T13:35:13Z"
        }
      ],
      "name": "Git errors for projects connected to GitHub over SSH",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-04T11:50:00Z",
      "status": "resolved",
      "updated_at": "2026-11-04T12:51:59Z"
    },
    {
      "created_at": "2026-11-03T17:44:07Z",
      "id": "01M6H85Q77SH4C75X895YH8B01",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning. We have put measures in place to prevent a recurrence and the Studio IDE has returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause. ",
          "created_at": "2026-11-03T19:09:56Z",
          "display_at": "2026-11-03T19:09:56Z",
          "id": "01M6HD2VHGDV8YX7HJYKYZXMJ6",
          "incident_id": "01M6H85Q77SH4C75X895YH8B01",
          "status": "resolved",
          "updated_at": "2026-11-03T19:09:56Z"
        },
        {
          "body": "We have deployed a fix for Studio IDE that was causing a restart loop on dbt Project Environments utilizing dbt versions 1.6 and 1.7. Studio IDE has returned to its normal state and we are continuing to monitor.",
          "created_at": "2026-11-03T18:21:25Z",
          "display_at": "2026-11-03T18:21:25Z",
          "id": "01M6HAA0CHM53G4ZVWG7ZBB4N2",
          "incident_id": "01M6H85Q77SH4C75X895YH8B01",
          "status": "monitoring",
          "updated_at": "2026-11-03T18:21:25Z"
        },
        {
          "body": "We have identified an issue with recent release that resulted in the dbt Studio restart loop on dbt Project Environments running on version 1.6 and 1.7. A rollback of this release is being implemented, and we will provide an update shortly.",
          "created_at": "2026-11-03T18:04:30Z",
          "display_at": "2026-11-03T18:04:30Z",
          "id": "01M6H9B1PVT6SS6KR95FES8NMR",
          "incident_id": "01M6H85Q77SH4C75X895YH8B01",
          "status": "identified",
          "updated_at": "2026-11-03T18:04:30Z"
        },
        {
          "body": "We're investigating reports of an issue with dbt Studio/IDE that is causing an error loop (dbt Studio prompts to be restarted, resulting in a loop). \n\nThe currently identified scope of impact is Projects running on legacy v1.6 and 1.7 anytime after 1:00 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available.",
          "created_at": "2026-11-03T17:50:24Z",
          "display_at": "2026-11-03T17:50:24Z",
          "id": "01M6H8H7GA6PWJEPFV98R5D6GP",
          "incident_id": "01M6H85Q77SH4C75X895YH8B01",
          "status": "investigating",
          "updated_at": "2026-11-03T17:50:24Z"
        },
        {
          "body": "We're investigating an issue with dbt Studio/IDE that is causing an error loop (restart dbt Studio). This is impacting projects running v1.6 and 1.7 in multi-tenant anytime after 1:00 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available.",
          "created_at": "2026-11-03T17:44:07Z",
          "display_at": "2026-11-03T17:44:07Z",
          "id": "01M6H85Q77NPM7JY7TDJNX1S92",
          "incident_id": "01M6H85Q77SH4C75X895YH8B01",
          "status": "investigating",
          "updated_at": "2026-11-03T17:44:07Z"
        }
      ],
      "name": "dbt Studio error loop with restarting dbt Studio",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-03T19:09:56Z",
      "status": "resolved",
      "updated_at": "2026-11-03T19:09:56Z"
    },
    {
      "created_at": "2026-11-03T12:24:26Z",
      "id": "01M6GNWBNPA7B6M4KVXDJR9A1E",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally . Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause. ",
          "created_at": "2026-11-03T14:15:01Z",
          "display_at": "2026-11-03T14:15:01Z",
          "id": "01M6GW6VCVQZZHX2K19C7D2FHG",
          "incident_id": "01M6GNWBNPA7B6M4KVXDJR9A1E",
          "status": "resolved",
          "updated_at": "2026-11-03T14:15:01Z"
        },
        {
          "body": "We have identified an issue with Gitlab project access tokens not being refreshed. Our engineers are working on  a fix for this, and we will provide an update shortly.",
          "created_at": "2026-11-03T13:24:37Z",
          "display_at": "2026-11-03T13:24:37Z",
          "id": "01M6GSAHXD7C7WS9G9N0T8X32C",
          "incident_id": "01M6GNWBNPA7B6M4KVXDJR9A1E",
          "status": "identified",
          "updated_at": "2026-11-03T13:24:37Z"
        },
        {
          "body": "We’re investigating an issue with the GitLab integration that is causing CI job commit statuses to not post back to GitLab. This is **limited to existing projects with a GitLab integration whose project access token has expired and was not refreshed.** It is impacting a small number of customers on the EU2 (Azure) region anytime after 06:00 UTC (01:00 AM Eastern) on 3 November. Affected customers may see missing pipeline statuses on merge requests, which can block merges that require passing statuses.\n**New project configurations and new GitLab integrations are not impacted.** There is currently no known workaround for affected existing projects, and reconnecting the repository does not resolve it. Our engineers are working on a resolution and we will provide updates approximately every 30 minutes, or as soon as new information becomes available. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you believe you are affected.",
          "created_at": "2026-11-03T12:24:26Z",
          "display_at": "2026-11-03T12:24:26Z",
          "id": "01M6GNWBNP1KQX209EKEEKD83T",
          "incident_id": "01M6GNWBNPA7B6M4KVXDJR9A1E",
          "status": "investigating",
          "updated_at": "2026-11-03T12:24:26Z"
        }
      ],
      "name": "Expired GitLab project access tokens not refreshing causing failures in posting commit statuses",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-11-03T14:15:01Z",
      "status": "resolved",
      "updated_at": "2026-11-03T14:15:01Z"
    },
    {
      "created_at": "2026-10-29T17:10:37Z",
      "id": "01M64A8S6SXM6DRV6QPA5YSHT2",
      "impact": "major",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally as of 5:50pm UTC.\nPlease contact Support via email [support@getdbt.com](http://support@getdbt.com) if you continue to experience delays and are unsure of the root cause.",
          "created_at": "2026-10-29T18:38:06Z",
          "display_at": "2026-10-29T18:38:06Z",
          "id": "01M64F8Z917ZF96TVXNRH188AR",
          "incident_id": "01M64A8S6SXM6DRV6QPA5YSHT2",
          "status": "resolved",
          "updated_at": "2026-10-29T18:38:06Z"
        },
        {
          "body": "We have deployed a fix for dbt wizard that was causing failed parsing of semantic layer's QueryResult response. dbt Wizard has returned to its normal state and we are continuing to monitor.",
          "created_at": "2026-10-29T17:52:23Z",
          "display_at": "2026-10-29T17:49:00Z",
          "id": "01M64CN88V4394J34NRWMB00QP",
          "incident_id": "01M64A8S6SXM6DRV6QPA5YSHT2",
          "status": "monitoring",
          "updated_at": "2026-10-29T17:52:59Z"
        },
        {
          "body": "We have identified an issue with dbt Wizard that resulted in failed parsing of semantic layer's QueryResult response. A fix is being implemented, and we will provide an update shortly.",
          "created_at": "2026-10-29T17:27:20Z",
          "display_at": "2026-10-29T17:22:00Z",
          "id": "01M64B7CDA9QXY3K8JM4Y6W8XX",
          "incident_id": "01M64A8S6SXM6DRV6QPA5YSHT2",
          "status": "identified",
          "updated_at": "2026-10-29T17:29:09Z"
        },
        {
          "body": "We’re investigating an issue with dbt Wizard that is causing requests that run SQL or Semantic Layer queries to fail with an error. This is impacting dbt Wizard in all multi-tenant regions  anytime after 16:32 UTC (12:32 PM Eastern Time). The team is working on a resolution and we will provide updates as soon as new information becomes available.\n\ndbt platform jobs, and the Studio IDE are not impacted and should be running as expected.",
          "created_at": "2026-10-29T17:10:37Z",
          "display_at": "2026-10-29T16:32:00Z",
          "id": "01M64A8S6SPHS9ESCHN3R49N13",
          "incident_id": "01M64A8S6SXM6DRV6QPA5YSHT2",
          "status": "investigating",
          "updated_at": "2026-10-29T18:22:20Z"
        }
      ],
      "name": "dbt Wizard SQL execution failing",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-29T18:38:06Z",
      "status": "resolved",
      "updated_at": "2026-10-29T18:38:06Z"
    },
    {
      "created_at": "2026-10-28T20:34:51Z",
      "id": "01M623J1D87HS00J4XE8AMF6GY",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally as of 19:35 UTC. \n\nBetween 19:18- 19:35 UTC on 28 October, an issue with the dbt platform services resulted in errors for customers loading dbt Studio, running jobs, or using the API. We have put measures in place to prevent a recurrence and the platform has returned to normal. \n\nPlease contact Support via email at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause",
          "created_at": "2026-10-29T00:56:27Z",
          "display_at": "2026-10-29T00:56:27Z",
          "id": "01M62JH0PKSN1KH35Z4ZEK9KRR",
          "incident_id": "01M623J1D87HS00J4XE8AMF6GY",
          "status": "resolved",
          "updated_at": "2026-10-29T00:56:27Z"
        },
        {
          "body": "We’ve deployed a fix and services are returning to normal.\n\nCustomers should no longer see errors when loading dbt Studio, running jobs, or using the API. We’re continuing to monitor closely and will confirm here once the issue is fully resolved.",
          "created_at": "2026-10-28T21:33:28Z",
          "display_at": "2026-10-28T21:33:28Z",
          "id": "01M626XBQEH2653CW7P32CW5EG",
          "incident_id": "01M623J1D87HS00J4XE8AMF6GY",
          "status": "monitoring",
          "updated_at": "2026-10-29T00:44:46Z"
        },
        {
          "body": "We’re investigating an issue affecting dbt platform services. Customers may experience errors or slow responses when loading dbt Studio, running jobs, or using the API.\n\nThe team is actively working on a resolution and we’ll share updates as soon as we know more.",
          "created_at": "2026-10-28T20:34:51Z",
          "display_at": "2026-10-28T20:20:00Z",
          "id": "01M623J1D8AY0R5AYC7A54J8ZH",
          "incident_id": "01M623J1D87HS00J4XE8AMF6GY",
          "status": "investigating",
          "updated_at": "2026-10-29T01:32:21Z"
        }
      ],
      "name": "Degraded performance across dbt platform",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-29T00:56:27Z",
      "status": "resolved",
      "updated_at": "2026-10-29T00:56:27Z"
    },
    {
      "created_at": "2026-10-22T17:21:10Z",
      "id": "01M5JA320K691B3002C81GSH5Z",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause. ",
          "created_at": "2026-10-23T05:27:10Z",
          "display_at": "2026-10-23T05:27:10Z",
          "id": "01M5KKMDQ938QAY41SFNEN5XGM",
          "incident_id": "01M5JA320K691B3002C81GSH5Z",
          "status": "resolved",
          "updated_at": "2026-10-23T05:27:10Z"
        },
        {
          "body": "We have deployed a fix and are continuing to monitor. Please contact us at support@getdbt.com if you're still experiencing any issues and are unsure of the root cause.",
          "created_at": "2026-10-22T23:49:34Z",
          "display_at": "2026-10-22T23:49:34Z",
          "id": "01M5K0A7TSSKRQYZA4QGDR6ZBT",
          "incident_id": "01M5JA320K691B3002C81GSH5Z",
          "status": "monitoring",
          "updated_at": "2026-10-22T23:49:34Z"
        },
        {
          "body": "We've identified an issue affecting dbt deps for projects in Studio and in some job runs, and our engineering team is rolling back the change we believe caused it. We will provide an update shortly.",
          "created_at": "2026-10-22T17:34:27Z",
          "display_at": "2026-10-22T13:02:00Z",
          "id": "01M5JAVD3TZJZ3QQ2V1EWJPRZX",
          "incident_id": "01M5JA320K691B3002C81GSH5Z",
          "status": "identified",
          "updated_at": "2026-10-22T18:43:23Z"
        },
        {
          "body": "We're investigating an issue with dbt invocations that is causing dbt deps failures. The team is working on a resolution and we will provide updates as soon as new information becomes available.",
          "created_at": "2026-10-22T17:21:10Z",
          "display_at": "2026-10-22T11:16:00Z",
          "id": "01M5JA320KA85VQF2E3SZ1FPYQ",
          "incident_id": "01M5JA320K691B3002C81GSH5Z",
          "status": "investigating",
          "updated_at": "2026-10-22T18:33:24Z"
        }
      ],
      "name": "dbt deps failures in dbt job runs and Studio",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-23T05:27:10Z",
      "status": "resolved",
      "updated_at": "2026-10-23T05:27:10Z"
    },
    {
      "created_at": "2026-10-20T06:55:39Z",
      "id": "01M5C1G9A94RM2V1D864GCFHRP",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "**Update posted at 15:05 UTC:** This incident has been resolved. Between about 06:00 and 12:10 UTC, an incident with our cloud provider (GCP) affected services in EMEA. Some customers saw stuck or delayed job runs, failed run cancellations, delayed notifications, out-of-date information in dbt Explorer and intermittent Semantic Layer errors. All services have recovered and are working as expected.\n\nIf you still see any issues, please contact support.",
          "created_at": "2026-10-20T15:07:04Z",
          "display_at": "2026-10-20T15:07:04Z",
          "id": "01M5CXM30YA6R78QG24GWZ28YB",
          "incident_id": "01M5C1G9A94RM2V1D864GCFHRP",
          "status": "resolved",
          "updated_at": "2026-10-20T15:07:04Z"
        },
        {
          "body": "**Update posted at 12:27 UTC:** Services in EMEA are returning to normal. Job runs, run cancellations, notifications and metadata ingestion should now be working as expected. We are monitoring to confirm full recovery.",
          "created_at": "2026-10-20T12:27:58Z",
          "display_at": "2026-10-20T12:27:58Z",
          "id": "01M5CMGS1E9023X8RDWHRP4TW9",
          "incident_id": "01M5C1G9A94RM2V1D864GCFHRP",
          "status": "monitoring",
          "updated_at": "2026-10-20T12:27:58Z"
        },
        {
          "body": "**Update posted at 10:20 UTC:** This issue is related to an ongoing incident with our cloud provider (GCP).\n\nMetadata ingestion in EMEA is now also affected, so some customers may see out-of-date information in dbt Explorer.",
          "created_at": "2026-10-20T10:21:35Z",
          "display_at": "2026-10-20T10:21:35Z",
          "id": "01M5CD9BBW61YCFBCHC033NKWA",
          "incident_id": "01M5C1G9A94RM2V1D864GCFHRP",
          "status": "identified",
          "updated_at": "2026-10-20T10:23:51Z"
        },
        {
          "body": "**Update posted at 08:20 UTC:** This issue is related to an ongoing incident with our cloud provider (GCP).\n\nWe have cleared the runs that were stuck in “Running”. Until the provider incident is resolved, some run cancellations may still fail.",
          "created_at": "2026-10-20T08:21:31Z",
          "display_at": "2026-10-20T08:21:31Z",
          "id": "01M5C6DFSTN0TQK9JNFX1EGX3A",
          "incident_id": "01M5C1G9A94RM2V1D864GCFHRP",
          "status": "identified",
          "updated_at": "2026-10-20T08:21:31Z"
        },
        {
          "body": "**Update posted at 07:56 UTC:** We are continuing to investigate the issue causing delayed and stuck job runs in EMEA. Our engineering team is working to restore normal service.\n\nWe will post another update within 60 minutes.",
          "created_at": "2026-10-20T07:58:17Z",
          "display_at": "2026-10-20T07:58:17Z",
          "id": "01M5C52YTHKR7KNX96PVF37QRB",
          "incident_id": "01M5C1G9A94RM2V1D864GCFHRP",
          "status": "investigating",
          "updated_at": "2026-10-20T07:58:17Z"
        },
        {
          "body": "We are investigating an issue affecting a small number of dbt platform accounts in our EMEA region. Starting around 06:00 UTC, some job runs may be stuck in a “Running” state and can’t be cancelled. Stuck runs may count against your account’s run concurrency, so new runs may start late.\n\nOur engineering team is working on a fix. We will post another update within 60 minutes.",
          "created_at": "2026-10-20T06:55:39Z",
          "display_at": "2026-10-20T06:55:39Z",
          "id": "01M5C1G9A9H08FZM33NJ2C9FN3",
          "incident_id": "01M5C1G9A94RM2V1D864GCFHRP",
          "status": "investigating",
          "updated_at": "2026-10-20T06:55:39Z"
        }
      ],
      "name": "Delayed and stuck job runs in EMEA",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-20T15:07:04Z",
      "status": "resolved",
      "updated_at": "2026-10-20T15:07:04Z"
    },
    {
      "created_at": "2026-10-15T13:09:47Z",
      "id": "01M4ZTXQSKV3AJ09T9NKS87DN4",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally as of 16:10 UTC. We have put measures in place to prevent a recurrence and dbt package installations have returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause.",
          "created_at": "2026-10-15T19:29:30Z",
          "display_at": "2026-10-15T16:10:00Z",
          "id": "01M50GN180PW57SX64D4HPDMKF",
          "incident_id": "01M4ZTXQSKV3AJ09T9NKS87DN4",
          "status": "resolved",
          "updated_at": "2026-10-15T19:30:46Z"
        },
        {
          "body": "The package download failures have stopped, and we’re monitoring the service to confirm the issue remains resolved. We’ll share another update if the symptoms return or as more information becomes available.",
          "created_at": "2026-10-15T15:10:30Z",
          "display_at": "2026-10-15T15:10:30Z",
          "id": "01M501TSAF3C411BW5DAB8R9D0",
          "incident_id": "01M4ZTXQSKV3AJ09T9NKS87DN4",
          "status": "monitoring",
          "updated_at": "2026-10-15T15:10:30Z"
        },
        {
          "body": "We’re continuing to investigate intermittent package download failures affecting dbt Cloud jobs. Some runs may fail during `dbt deps` with a “not a gzip file” error. Our Engineering team is investigating the issue, and we’ll share another update as more information becomes available.",
          "created_at": "2026-10-15T13:56:09Z",
          "display_at": "2026-10-15T13:56:09Z",
          "id": "01M4ZXJM4G514PVNE76WH04DG5",
          "incident_id": "01M4ZTXQSKV3AJ09T9NKS87DN4",
          "status": "investigating",
          "updated_at": "2026-10-15T13:56:09Z"
        },
        {
          "body": "We’re investigating intermittent failures during `dbt deps` that prevent some dbt Cloud jobs from downloading and installing packages. Affected runs receive a response that is not a valid gzip archive. The issue has been observed across multiple customer accounts, packages, and regions. Our findings point to the package CDN delivery path, but the root cause is not yet confirmed. Engineering is investigating, and we’ll provide updates as we learn more.",
          "created_at": "2026-10-15T13:09:47Z",
          "display_at": "2026-10-15T13:09:47Z",
          "id": "01M4ZTXQSKDNYRJ0HGRHCSNG1E",
          "incident_id": "01M4ZTXQSKV3AJ09T9NKS87DN4",
          "status": "investigating",
          "updated_at": "2026-10-15T13:09:47Z"
        }
      ],
      "name": "Intermittent dbt package download failures",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-15T16:10:00Z",
      "status": "resolved",
      "updated_at": "2026-10-15T19:29:31Z"
    },
    {
      "created_at": "2026-10-15T05:38:09Z",
      "id": "01M4Z12S75HMTAAWAHSMH3RZWX",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally. Between 00:51 AM UTC and 01:20 AM UTC some scheduled runs were cancelled . We have put measures in place to prevent a recurrence and the scheduled runs have returned to normal. \nIf you are still experiencing issues, please contact us at [support@getdbt.com](mailto:support@getdbt.com).",
          "created_at": "2026-10-15T05:38:09Z",
          "display_at": "2026-10-14T16:51:00Z",
          "id": "01M4Z12S75ZDHX7BBV8PHBJSC6",
          "incident_id": "01M4Z12S75HMTAAWAHSMH3RZWX",
          "status": "resolved",
          "updated_at": "2026-10-15T05:55:59Z"
        }
      ],
      "name": "Some scheduled job runs cancelled in US region",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-14T16:51:00Z",
      "status": "resolved",
      "updated_at": "2026-10-15T05:38:09Z"
    },
    {
      "created_at": "2026-10-14T12:14:34Z",
      "id": "01M4X5BX0V08MVHM444C7FMQ3A",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "**Resolved:** The Discovery API issue affecting customers on prod-us-c3 has been resolved. Customers may have experienced sporadic errors between approximately 11:30 and 11:54 UTC on October 14. We increased API gateway capacity, and the service has recovered. Other components and regions were not affected.",
          "created_at": "2026-10-14T12:15:46Z",
          "display_at": "2026-10-14T10:54:00Z",
          "id": "01M4X5E3DJ269Z23W8CHKY37WQ",
          "incident_id": "01M4X5BX0V08MVHM444C7FMQ3A",
          "status": "resolved",
          "updated_at": "2026-10-14T12:16:04Z"
        },
        {
          "body": "We’re investigating an issue with the Discovery API that caused sporadic errors for customers on prod-us-c3 from approximately 11:30 to 11:54 UTC on October 14. The team increased API gateway capacity, and the service has recovered. We’ll provide further updates if new information becomes available.\n\nOther components and regions are not impacted and are operating as expected.",
          "created_at": "2026-10-14T12:14:34Z",
          "display_at": "2026-10-14T10:30:00Z",
          "id": "01M4X5BX0VGAGYK57MT7VKAZVH",
          "incident_id": "01M4X5BX0V08MVHM444C7FMQ3A",
          "status": "investigating",
          "updated_at": "2026-10-14T12:14:53Z"
        }
      ],
      "name": "Codex API: intermittent metadata access",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-14T10:54:00Z",
      "status": "resolved",
      "updated_at": "2026-10-14T12:15:46Z"
    },
    {
      "created_at": "2026-10-13T22:28:22Z",
      "id": "01M4VP33REQMCYNC5K4W21C1C6",
      "impact": "critical",
      "incident_updates": [
        {
          "body": "This incident has been resolved. A fix was deployed for the dbt platform issue that was causing problems with access to the web application and the Admin API. Both are now operating normally.\n\nIf you are still experiencing issues, please contact us at [support@getdbt.com](mailto:support@getdbt.com).",
          "created_at": "2026-10-14T04:33:26Z",
          "display_at": "2026-10-14T04:33:26Z",
          "id": "01M4WAZJ0WMBR7H6GA5JTCXCPQ",
          "incident_id": "01M4VP33REQMCYNC5K4W21C1C6",
          "status": "resolved",
          "updated_at": "2026-10-14T04:33:26Z"
        },
        {
          "body": "We are continuing to monitor the recovery following the fix we deployed for the dbt Platform. Access to the web application is improving, and we have not seen any new issues since the fix went out. \n\nIf you are still experiencing issues on your end, please contact us at [support@getdbt.com](mailto:support@getdbt.com).",
          "created_at": "2026-10-14T00:50:59Z",
          "display_at": "2026-10-14T00:50:59Z",
          "id": "01M4VY881Y487D38YR1NZ6QN12",
          "incident_id": "01M4VP33REQMCYNC5K4W21C1C6",
          "status": "monitoring",
          "updated_at": "2026-10-14T00:50:59Z"
        },
        {
          "body": "We have deployed a fix for the dbt Platform that was causing access issues to the web application. We are seeing recovery and are continuing to monitor.",
          "created_at": "2026-10-14T00:14:17Z",
          "display_at": "2026-10-14T00:14:17Z",
          "id": "01M4VW51QPGR5EJNF2RA9CWPWB",
          "incident_id": "01M4VP33REQMCYNC5K4W21C1C6",
          "status": "monitoring",
          "updated_at": "2026-10-14T00:14:17Z"
        },
        {
          "body": "We have identified an issue with the web application that has resulted in users being unable to access the dbt Platform. A fix is being implemented, and we will provide an update shortly.",
          "created_at": "2026-10-13T23:30:28Z",
          "display_at": "2026-10-13T23:30:28Z",
          "id": "01M4VSMT87JHRH5C41BKCZYM4E",
          "incident_id": "01M4VP33REQMCYNC5K4W21C1C6",
          "status": "identified",
          "updated_at": "2026-10-13T23:30:28Z"
        },
        {
          "body": "We're investigating an issue with dbt Platform that is causing the web application to not load. This is impacting logins and access the web application anytime after 6 PM Eastern. The team is working on a resolution and we will provide updates as soon as new information becomes available.",
          "created_at": "2026-10-13T22:28:22Z",
          "display_at": "2026-10-13T22:28:22Z",
          "id": "01M4VP33RE4A95KN24E48MX9HR",
          "incident_id": "01M4VP33REQMCYNC5K4W21C1C6",
          "status": "investigating",
          "updated_at": "2026-10-13T22:28:22Z"
        }
      ],
      "name": "Unable to Access dbt Platform",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-14T04:33:26Z",
      "status": "resolved",
      "updated_at": "2026-10-14T04:33:26Z"
    },
    {
      "created_at": "2026-10-08T16:19:29Z",
      "id": "01M4E501MYFDEM331C59HE3KST",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally as of 1:20 PM Eastern on October 8. Between 11:30 AM and 1:20 PM Eastern, an issue with run artifact and log storage in US Cell 3 (GCP) resulted in some job runs completing without their logs and artifacts (such as manifest.json and run_results.json) being available, and some runs that use deferral failing. We have put measures in place to prevent a recurrence and run artifact and log storage has returned to normal. Please contact Support via email at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.",
          "created_at": "2026-10-09T22:56:21Z",
          "display_at": "2026-10-09T22:56:21Z",
          "id": "01M4HE3EP4AYF19ADWVXN4ZSVJ",
          "incident_id": "01M4E501MYFDEM331C59HE3KST",
          "status": "resolved",
          "updated_at": "2026-10-09T22:56:21Z"
        },
        {
          "body": "GCP has completed mitigations on their end that were causing some job runs to complete without their logs and artifacts (such as [manifest.json](https://manifest.json) and [run_results.json](https://run_results.json)) being available. Scheduled jobs and metadata ingestion have returned to their normal state and we are continuing to monitor.",
          "created_at": "2026-10-08T20:12:35Z",
          "display_at": "2026-10-08T20:12:35Z",
          "id": "01M4EJAWNER1TK8TXV6DTNXCMG",
          "incident_id": "01M4E501MYFDEM331C59HE3KST",
          "status": "monitoring",
          "updated_at": "2026-10-08T20:26:45Z"
        },
        {
          "body": "We're investigating an issue with run artifact and log storage that is causing some job runs to complete without their logs and artifacts (such as manifest.json and run_results.json) being available. This is impacting some runs in the US Cell 3 (GCP) region anytime after 11:30 AM Eastern. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.\nOther dbt Cloud components are not impacted and should be running as expected. Job runs that use deferral and depend on artifacts from affected runs may fail.",
          "created_at": "2026-10-08T16:19:29Z",
          "display_at": "2026-10-08T16:19:29Z",
          "id": "01M4E501MYS6RE13N67SG8G3M3",
          "incident_id": "01M4E501MYFDEM331C59HE3KST",
          "status": "investigating",
          "updated_at": "2026-10-08T16:19:29Z"
        }
      ],
      "name": "Run logs and artifacts missing for some runs (US Cell 3, GCP)",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-09T22:56:21Z",
      "status": "resolved",
      "updated_at": "2026-10-09T22:56:21Z"
    },
    {
      "created_at": "2026-10-12T19:21:28Z",
      "id": "01M4RS04Q4NE80WEAC25DEG2TZ",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "A rate-limit change being previewed by GitLab caused failures for some customers using the native GitLab integration with [GitLab.com](http://GitLab.com). This impacted IDE pull and fetch operations and job run clone steps between 2026-10-07 15:23 UTC and 2026-10-07 16:03 UTC. Git operations returned to normal at the end of that window, and we have since seen only isolated rate-limit errors. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.",
          "created_at": "2026-10-12T19:21:28Z",
          "display_at": "2026-10-07T08:03:00Z",
          "id": "01M4RS04Q492815JQEANFNDCM2",
          "incident_id": "01M4RS04Q4NE80WEAC25DEG2TZ",
          "status": "resolved",
          "updated_at": "2026-10-12T19:28:00Z"
        },
        {
          "body": "We identified that a rate-limit change being previewed by GitLab was causing Git fetch and clone requests from the native GitLab integration to fail for some customers. This affected IDE pull and fetch operations and job run clone steps.",
          "created_at": "2026-10-12T19:21:28Z",
          "display_at": "2026-10-07T07:23:00Z",
          "id": "01M4RS04Q4YY69BVHTN983BBAH",
          "incident_id": "01M4RS04Q4NE80WEAC25DEG2TZ",
          "status": "identified",
          "updated_at": "2026-10-12T19:21:28Z"
        }
      ],
      "name": "Git failures for GitLab-integrated accounts",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-07T08:03:00Z",
      "status": "resolved",
      "updated_at": "2026-10-12T19:21:28Z"
    },
    {
      "created_at": "2026-10-02T11:05:59Z",
      "id": "01M3Y4NPGFFTX4Q9MPFVVQSPZ7",
      "impact": "minor",
      "incident_updates": [
        {
          "body": "The issue has been resolved, and all affected systems are now functioning normally as of 12:30 UTC. We have put measures in place to prevent a recurrence and the system has returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com \"support@getdbt.com\") if you continue to experience delays and are unsure of the root cause.",
          "created_at": "2026-10-02T12:34:45Z",
          "display_at": "2026-10-02T12:34:45Z",
          "id": "01M3Y9R7MDW0ZN3C1P9Y28BXZ2",
          "incident_id": "01M3Y4NPGFFTX4Q9MPFVVQSPZ7",
          "status": "resolved",
          "updated_at": "2026-10-02T12:38:43Z"
        },
        {
          "body": "We've identified the cause of the increased errors affecting Wizard CLI requests to Anthropic models — introduced during a recent inference endpoint upgrade. A fix has been prepared and is being deployed. We have not yet confirmed full recovery and will provide another update once that's verified.\n\nAll other dbt Cloud functionality is not impacted and should be running as expected.",
          "created_at": "2026-10-02T11:50:30Z",
          "display_at": "2026-10-02T11:50:30Z",
          "id": "01M3Y777JW7ES5DMNZHQBRTMXR",
          "incident_id": "01M3Y4NPGFFTX4Q9MPFVVQSPZ7",
          "status": "identified",
          "updated_at": "2026-10-02T11:50:30Z"
        },
        {
          "body": "We've identified the cause of the increased errors affecting Wizard CLI requests to Anthropic models — introduced during a recent inference endpoint upgrade. A fix has been prepared and is being deployed. We have not yet confirmed full recovery and will provide another update once that's verified.\n\nAll other dbt Cloud functionality is not impacted and should be running as expected.",
          "created_at": "2026-10-02T11:46:51Z",
          "display_at": "2026-10-02T11:46:51Z",
          "id": "01M3Y70HM6DXFR5VWYPYZ1AF2E",
          "incident_id": "01M3Y4NPGFFTX4Q9MPFVVQSPZ7",
          "status": "identified",
          "updated_at": "2026-10-02T11:47:20Z"
        },
        {
          "body": "We're investigating an issue with Wizard CLI requests to Anthropic models that is causing increased errors for affected customers. This is impacting AI-assisted CLI functionality in our multi-tenant US production environment this morning. The team is working on a resolution and we will provide updates as soon as new information becomes available.\nAll other dbt Cloud functionality is not impacted and should be running as expected.",
          "created_at": "2026-10-02T11:05:59Z",
          "display_at": "2026-10-02T11:05:59Z",
          "id": "01M3Y4NPGFGF9BM6XTY1YY978C",
          "incident_id": "01M3Y4NPGFFTX4Q9MPFVVQSPZ7",
          "status": "identified",
          "updated_at": "2026-10-02T11:05:59Z"
        }
      ],
      "name": "Increased errors for Wizard CLI requests using Anthropic models",
      "page_id": "01JBH53RGT63T7EM45RY826C4H",
      "resolved_at": "2026-10-02T12:34:45Z",
      "status": "resolved",
      "updated_at": "2026-10-02T12:34:45Z"
    }
  ],
  "page": {
    "id": "01JBH53RGT63T7EM45RY826C4H",
    "name": "dbt Cloud",
    "updated_at": "2026-11-20T05:55:33Z",
    "url": "https://status.getdbt.com/"
  }
}