Investigating issues with dyno formations and autoscaling

Triage and remediation of DNS and Applications states have been completed.

Engineers have resolved the issues related to dyno scaling and domain changes. Affected applications should now reflect the correct state. We are currently focused on remediating add-on plan changes, ensuring the actual configurations are consistent with what's displayed in the Dashboard.

We will continue to share updates as remediation progresses.

We are currently experiencing issues affecting a small number of apps with customer-initiated actions between June 10, 06:00, and June 11, 05:50, during incident [#2822](https://status.heroku.com/incidents/2822). These apps may be affected in the following ways:

- **Dyno Scaling:** Scaling changes made during the incident may not have been applied correctly. The number of dynos running could differ from what’s shown in the Dashboard/API.
- **Domain Changes:** DNS updates made during the incident may not have completed, causing affected apps to display the "No Such App" error page.
- **Add-on Plan Changes:** Changes to add-on plans may not have fully taken effect. While the Dashboard may show the updated plan, the actual add-on may not reflect these changes.

Our team is actively working on remediating these issues to ensure apps reflect their intended state. We will provide an update on progress within the next hour.

Engineers are investigating an issue with the Heroku platform. Customers may see inconsistencies in the number of dynos running in their applications, and apps may fail to autoscale appropriately.