dbt Cloud Outage History

dbt Cloud is up right now

Pingoru has recorded 767 incidents for dbt Cloud: 767 in the last 12 months and 201 in the last 90 days.

Source: status.getdbt.com

767incidents recorded
767last 12 months
201last 90 days
7 hourstypical duration
Incidents per month
0100200AprMayJunJulAugSepOct44
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct12%
Pingoru began tracking dbt Cloud in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20268270 of 720 (10%)
May 2026126155 of 744 (21%)
June 20265540 of 720 (6%)
July 20268129 of 744 (4%)
August 20267822 of 744 (3%)
September 20267753 of 720 (7%)
October 20264469 of 596 (12%)

Incidents, newest first

Minor February 26, 2026 [EMEA Cell 1 AZURE] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 26, 2026 [EU Cell 1 GCP] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 26, 2026 [EU4 Cell 1 GCP] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 26, 2026 [JP Cell 1 AWS] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 26, 2026 [US AWS] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 26, 2026 [US Cell 1 AWS] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 26, 2026 [US Cell 1 AZURE] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 26, 2026 [US Cell 1 GCP] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 26, 2026 [US Cell 2 AWS] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 26, 2026 [US Cell 3 AWS] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 26, 2026 [US Cell 4 AWS] dbt Insights Returning Errors 1h 3m

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

  1. investigating Feb 26, 2026, 03:17 PM UTC

    We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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. monitoring Feb 26, 2026, 04:00 PM UTC

    We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

  3. resolved Feb 26, 2026, 04:20 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 →

Minor February 25, 2026 [US AWS] Gitlab 403 and 429 Errors 1h 31m

Started Feb 25, 2026, 07:49 PM UTC· resolved Feb 25, 2026, 09:20 PM UTC

  1. identified Feb 25, 2026, 07:49 PM UTC

    There is currently a GitLab outage that may have some impact on git operations. We are monitoring on our end, please refer to the following statuspage for any more information and to stay up to date: https://status.gitlab.com/

  2. monitoring Feb 25, 2026, 07:52 PM UTC

    It appears that a fix has been shipped and GitLab and will continue to provide updates. More information: https://status.gitlab.com/

  3. resolved Feb 25, 2026, 09:20 PM UTC

    This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Minor February 25, 2026 [US Cell 1 AWS] Gitlab 403 and 429 Errors 1h 31m

Started Feb 25, 2026, 07:49 PM UTC· resolved Feb 25, 2026, 09:20 PM UTC

  1. identified Feb 25, 2026, 07:49 PM UTC

    There is currently a GitLab outage that may have some impact on git operations. We are monitoring on our end, please refer to the following statuspage for any more information and to stay up to date: https://status.gitlab.com/

  2. monitoring Feb 25, 2026, 07:52 PM UTC

    It appears that a fix has been shipped and GitLab and will continue to provide updates. More information: https://status.gitlab.com/

  3. resolved Feb 25, 2026, 09:20 PM UTC

    This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Minor February 25, 2026 [US Cell 2 AWS] Gitlab 403 and 429 Errors 1h 31m

Started Feb 25, 2026, 07:49 PM UTC· resolved Feb 25, 2026, 09:20 PM UTC

  1. identified Feb 25, 2026, 07:49 PM UTC

    There is currently a GitLab outage that may have some impact on git operations. We are monitoring on our end, please refer to the following statuspage for any more information and to stay up to date: https://status.gitlab.com/

  2. monitoring Feb 25, 2026, 07:52 PM UTC

    It appears that a fix has been shipped and GitLab and will continue to provide updates. More information: https://status.gitlab.com/

  3. resolved Feb 25, 2026, 09:20 PM UTC

    This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Minor February 25, 2026 [US Cell 3 AWS] Gitlab 403 and 429 Errors 1h 31m

Started Feb 25, 2026, 07:49 PM UTC· resolved Feb 25, 2026, 09:20 PM UTC

  1. identified Feb 25, 2026, 07:49 PM UTC

    There is currently a GitLab outage that may have some impact on git operations. We are monitoring on our end, please refer to the following statuspage for any more information and to stay up to date: https://status.gitlab.com/

  2. monitoring Feb 25, 2026, 07:52 PM UTC

    It appears that a fix has been shipped and GitLab and will continue to provide updates. More information: https://status.gitlab.com/

  3. resolved Feb 25, 2026, 09:20 PM UTC

    This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Minor February 25, 2026 [US Cell 4 AWS] Gitlab 403 and 429 Errors 1h 31m

Started Feb 25, 2026, 07:49 PM UTC· resolved Feb 25, 2026, 09:20 PM UTC

  1. identified Feb 25, 2026, 07:49 PM UTC

    There is currently a GitLab outage that may have some impact on git operations. We are monitoring on our end, please refer to the following statuspage for any more information and to stay up to date: https://status.gitlab.com/

  2. monitoring Feb 25, 2026, 07:52 PM UTC

    It appears that a fix has been shipped and GitLab and will continue to provide updates. More information: https://status.gitlab.com/

  3. resolved Feb 25, 2026, 09:20 PM UTC

    This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/

Read the full incident report →

Minor February 24, 2026 [APAC AWS] Compare changes job step failing for Databricks users 20h 19m

Started Feb 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

  1. investigating Feb 24, 2026, 10:27 PM UTC

    We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. identified Feb 24, 2026, 11:07 PM UTC

    We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

  3. resolved Feb 25, 2026, 06:46 PM UTC

    The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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.

Read the full incident report →

Minor February 24, 2026 [EMEA AWS] Compare changes job step failing for Databricks users 20h 19m

Started Feb 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

  1. investigating Feb 24, 2026, 10:27 PM UTC

    We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. identified Feb 24, 2026, 11:07 PM UTC

    We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

  3. resolved Feb 25, 2026, 06:46 PM UTC

    The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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.

Read the full incident report →

Minor February 24, 2026 [EMEA Cell 1 AZURE] Compare changes job step failing for Databricks users 20h 19m

Started Feb 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

  1. investigating Feb 24, 2026, 10:27 PM UTC

    We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. identified Feb 24, 2026, 11:07 PM UTC

    We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

  3. resolved Feb 25, 2026, 06:46 PM UTC

    The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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.

Read the full incident report →

Minor February 24, 2026 [EU Cell 1 GCP] Compare changes job step failing for Databricks users 20h 19m

Started Feb 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

  1. investigating Feb 24, 2026, 10:27 PM UTC

    We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. identified Feb 24, 2026, 11:07 PM UTC

    We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

  3. resolved Feb 25, 2026, 06:46 PM UTC

    The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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.

Read the full incident report →

Minor February 24, 2026 [EU4 Cell 1 GCP] Compare changes job step failing for Databricks users 20h 19m

Started Feb 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

  1. investigating Feb 24, 2026, 10:27 PM UTC

    We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. identified Feb 24, 2026, 11:07 PM UTC

    We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

  3. resolved Feb 25, 2026, 06:46 PM UTC

    The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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.

Read the full incident report →

Minor February 24, 2026 [JP Cell 1 AWS] Compare changes job step failing for Databricks users 20h 19m

Started Feb 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

  1. investigating Feb 24, 2026, 10:27 PM UTC

    We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. identified Feb 24, 2026, 11:07 PM UTC

    We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

  3. resolved Feb 25, 2026, 06:46 PM UTC

    The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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.

Read the full incident report →

Minor February 24, 2026 [US AWS] Compare changes job step failing for Databricks users 20h 19m

Started Feb 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

  1. investigating Feb 24, 2026, 10:27 PM UTC

    We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. identified Feb 24, 2026, 11:07 PM UTC

    We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

  3. resolved Feb 25, 2026, 06:46 PM UTC

    The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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.

Read the full incident report →

Minor February 24, 2026 [US Cell 1 AWS] Compare changes job step failing for Databricks users 20h 19m

Started Feb 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

  1. investigating Feb 24, 2026, 10:27 PM UTC

    We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. identified Feb 24, 2026, 11:07 PM UTC

    We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

  3. resolved Feb 25, 2026, 06:46 PM UTC

    The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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.

Read the full incident report →

Minor February 24, 2026 [US Cell 1 AZURE] Compare changes job step failing for Databricks users 20h 19m

Started Feb 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

  1. investigating Feb 24, 2026, 10:27 PM UTC

    We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. identified Feb 24, 2026, 11:07 PM UTC

    We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

  3. resolved Feb 25, 2026, 06:46 PM UTC

    The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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.

Read the full incident report →