dbt Cloud Outage History
dbt Cloud is up right nowPingoru has recorded 767 incidents for dbt Cloud: 767 in the last 12 months and 201 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 82 | 70 of 720 (10%) |
| May 2026 | 126 | 155 of 744 (21%) |
| June 2026 | 55 | 40 of 720 (6%) |
| July 2026 | 81 | 29 of 744 (4%) |
| August 2026 | 78 | 22 of 744 (3%) |
| September 2026 | 77 | 53 of 720 (7%) |
| October 2026 | 44 | 69 of 598 (11%) |
Incidents, newest first
Minor April 18, 2026 [EMEA AWS] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [EMEA Cell 1 AZURE] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [EU Cell 1 GCP] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [EU4 Cell 1 GCP] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [JP Cell 1 AWS] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [US AWS] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [US Cell 1 AWS] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [US Cell 1 AZURE] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [US Cell 1 GCP] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [US Cell 2 AWS] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [US Cell 3 AWS] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 18, 2026 [US Cell 4 AWS] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.
Minor April 16, 2026 Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
No vendor updates were posted for this incident.
Minor April 16, 2026 [APAC AWS] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [EMEA AWS] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [EMEA Cell 1 AZURE] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [EU Cell 1 GCP] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [EU4 Cell 1 GCP] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [JP Cell 1 AWS] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [US AWS] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [US Cell 1 AWS] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [US Cell 1 AZURE] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [US Cell 1 GCP] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [US Cell 2 AWS] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.
Minor April 16, 2026 [US Cell 3 AWS] Latest versions of files not showing recent commits in Studio 2h 19m
Started Apr 16, 2026, 05:04 PM UTC· resolved Apr 16, 2026, 07:24 PM UTC
- investigating Apr 16, 2026, 05:04 PM UTC
We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 16, 2026, 06:26 PM UTC
We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly.
- monitoring Apr 16, 2026, 06:58 PM UTC
We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied.
- resolved Apr 16, 2026, 07:24 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio has returned to normal. 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.