Service Disruption on Heroku
This summary is created by Generative AI and may differ from the actual content.
Overview
A service disruption impacted the majority of the Heroku platform, including US and EU apps and data, for several hours. The incident was triggered by a DNS-related issue on the database side of a third-party cloud infrastructure vendor. The Salesforce Technology team identified a broader service disruption impacting multiple Salesforce clouds, including Heroku, due to this same third-party vendor issue. The issue was resolved after the vendor implemented a fix.
Impact
The incident caused a service disruption across the majority of the Heroku platform. Heroku US Apps and Data were impacted for 5 hours, 52 minutes. Heroku EU Apps and Data were impacted for 13 hours, 37 minutes. Heroku Tools were impacted for 5 hours, 52 minutes. The Salesforce Technology team also identified a service disruption impacting multiple other Salesforce clouds (Commerce Cloud, Core services, Hyperforce, MuleSoft, Marketing Cloud Engagement, Marketing Cloud Account Engagement, Slack, and Tableau) due to the same third-party vendor issue.
Trigger
The issue was triggered by a DNS-related problem on the database side of a third-party cloud infrastructure vendor.
Detection
The Salesforce Technology team identified the service disruption impacting multiple clouds, including Heroku, through monitoring.
Resolution
The third-party cloud infrastructure vendor implemented a "fix forward" for the DNS-related issue. Heroku engineers collaborated with the vendor, leading to the restoration of all impacted Heroku platform services.
Root Cause
The root cause was a DNS-related issue on the database side of a third-party cloud infrastructure vendor.