dbt Cloud Outage History

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. 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.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. 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.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. 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.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. 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.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. 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.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. 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.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 18, 2026, 11:31 PM UTC· resolved Sep 19, 2026, 02:30 PM UTC

1. investigating Sep 18, 2026, 11:31 PM UTC

   We're investigating an issue with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. This is currently impacting scheduled jobs and the Studio IDE for environments on version Fusion Stable. 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.

2. identified Sep 19, 2026, 12:03 AM UTC

   We have identified an issue with with scheduled jobs and the Studio IDE that is causing error No schema found for get columns in relation call. A fix is being implemented, and we will provide an update shortly.

3. identified Sep 19, 2026, 03:20 AM UTC

   We are continuing to work on a fix. Impacted environments can currently work around this issue by switching to Fusion Extended version temporarily while a fix is in progress. Please reach out to Support at [email protected] "[email protected]": mailto:[email protected] if you are unsure of impact or have any questions.

4. identified Sep 19, 2026, 05:31 AM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

5. identified Sep 19, 2026, 01:00 PM UTC

   We are continuing to work on and validate a fix. Impacted environments can temporarily work around this issue by switching to the Fusion Extended release track. Please reach out to Support at [email protected]: mailto:[email protected] if you are unsure whether your environment is impacted or have any questions.

6. monitoring Sep 19, 2026, 01:40 PM UTC

   Our engineers have deployed a fix for this issue. The fix has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended as a workaround. We're continuing to monitor for any further reports. If you have any questions relating to this issue please contact us using [email protected]

7. resolved Sep 19, 2026, 02:30 PM UTC

   This issue has been resolved. Our engineers deployed a fix, and it has been promoted to the Latest and Stable release tracks. Customers on Fusion Stable no longer need to remain on Fusion Extended. Thank you for your patience while we worked on this.

Read the full incident report →

Started Sep 10, 2026, 04:39 PM UTC· resolved Sep 10, 2026, 06:00 PM UTC

1. investigating Sep 10, 2026, 04:39 PM UTC

   We have identified an issue affecting dbt Copilot on single-tenant deployments hosted on Azure. Conversations are not retaining context, which means the assistant may be unable to continue a conversation or complete a request. A fix is being implemented and we will provide an update shortly.

Read the full incident report →

Started Sep 10, 2026, 04:39 PM UTC· resolved Sep 10, 2026, 06:00 PM UTC

1. investigating Sep 10, 2026, 04:39 PM UTC

   We have identified an issue affecting dbt Copilot on single-tenant deployments hosted on Azure. Conversations are not retaining context, which means the assistant may be unable to continue a conversation or complete a request. A fix is being implemented and we will provide an update shortly.

Read the full incident report →

Started Sep 10, 2026, 04:39 PM UTC· resolved Sep 10, 2026, 06:00 PM UTC

1. investigating Sep 10, 2026, 04:39 PM UTC

   We have identified an issue affecting dbt Copilot on single-tenant deployments hosted on Azure. Conversations are not retaining context, which means the assistant may be unable to continue a conversation or complete a request. A fix is being implemented and we will provide an update shortly.

Read the full incident report →

Started Sep 10, 2026, 02:28 PM UTC· resolved Sep 10, 2026, 04:45 PM UTC

1. monitoring Sep 10, 2026, 02:28 PM UTC

   We've deployed a fix for an issue affecting the Discovery API that caused intermittent errors for some job run and metadata queries. This impacted customers on our North America multi-tenant deployment between approximately 9:03 AM and 9:35 AM ET. EU and Single Tenant deployments were not affected. The Discovery API has returned to normal operation and we're continuing to monitor before marking this resolved.

2. resolved Sep 10, 2026, 04:45 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 10, 2026, 02:28 PM UTC· resolved Sep 10, 2026, 04:45 PM UTC

1. monitoring Sep 10, 2026, 02:28 PM UTC

   We've deployed a fix for an issue affecting the Discovery API that caused intermittent errors for some job run and metadata queries. This impacted customers on our North America multi-tenant deployment between approximately 9:03 AM and 9:35 AM ET. EU and Single Tenant deployments were not affected. The Discovery API has returned to normal operation and we're continuing to monitor before marking this resolved.

2. resolved Sep 10, 2026, 04:45 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 10, 2026, 02:28 PM UTC· resolved Sep 10, 2026, 04:45 PM UTC

1. monitoring Sep 10, 2026, 02:28 PM UTC

   We've deployed a fix for an issue affecting the Discovery API that caused intermittent errors for some job run and metadata queries. This impacted customers on our North America multi-tenant deployment between approximately 9:03 AM and 9:35 AM ET. EU and Single Tenant deployments were not affected. The Discovery API has returned to normal operation and we're continuing to monitor before marking this resolved.

2. resolved Sep 10, 2026, 04:45 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Sep 10, 2026, 01:46 PM UTC· resolved Sep 10, 2026, 02:27 PM UTC

1. investigating Sep 10, 2026, 01:46 PM UTC

   We're currently investigating an increase in errors related to dbt MCP and Wizard. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. monitoring Sep 10, 2026, 02:08 PM UTC

   We have deployed a fix to mitigate the issue and are currently monitoring.

3. resolved Sep 10, 2026, 02:27 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 1:57 PM UTC

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →

Started Sep 10, 2026, 08:02 AM UTC· resolved Sep 10, 2026, 09:14 AM UTC

1. investigating Sep 10, 2026, 08:02 AM UTC

   We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.

2. identified Sep 10, 2026, 08:14 AM UTC

   We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.

3. monitoring Sep 10, 2026, 08:52 AM UTC

   A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.

4. resolved Sep 10, 2026, 09:14 AM UTC

   This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience

Read the full incident report →