Maintenance
Maintenance维护事件
- complete
The maintenance is now complete. Thanks for your patience.
18 Hirefire incidents · 2023年6月 — official updates, affected components, duration and resolution details.
The maintenance is now complete. Thanks for your patience.
The system remains stable. Marking as resolved.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
Autoscaling has been fully restored following the restoration of Heroku's API. However, some Heroku customers on X.com have reported intermittent errors. If you are still experiencing autoscaling issues, please contact us at [email protected], and we will investigate promptly. Heroku status page reference: https://status.heroku.com/incidents/2822
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete. Thanks for your patience.
We encountered a 15-minute disruption with our Logdrain system, impacting metric accuracy and resulting in unintended dyno manager scaling adjustments. The issue has been addressed, and we are investigating solutions to prevent future occurrences. We apologize for any inconvenience caused.
The maintenance is now complete. Thanks for your patience.
The issues affecting our services have been resolved, and everything is now operating normally. While we do not have a definitive understanding of the root cause, we believe the issue may have occurred at a lower level, potentially related to networking. We have reached out to Heroku for further insights into this matter. We sincerely apologize for any inconvenience this disruption may have caused and appreciate your patience. We will continue to monitor our systems closely.
The maintenance is now complete. Thanks for your patience.
All systems remain operational without issues.
The maintenance is now complete. Thanks for your patience.
The maintenance is now complete.
On January 11, at 15:00 (UTC), web dynos being autoscaled using the New Relic strategies experienced issues in retrieving metric data from New Relic's API. Upon investigation, it appears that New Relic has increased the processing time for metric data, delaying its availability through their API. Previously, metric data would become available approximately 2 minutes after receipt. Now, it seems to take about 5 minutes. We have applied a patch that accesses data, which, based on our observations, should be consistently available at each checkup. Unfortunately, the downside is that data retrieved from New Relic is now 5 minutes delayed. This might pose an issue depending on the nature of your application and use case. If this delay is problematic and you wish to continue using either the Response Time or Requests Per Minute strategies, we recommend considering a switch to the "Logplex - Response Time" or "Logplex - Requests Per Minute" strategies. Our Logdrain system, integrating with Heroku Logplex, ingests and makes data available within 5 seconds, compared to the current 5-minute delay on New Relic.
The maintenance is now complete. Thanks for your patience.
The issue with our Heroku OAuth integration has now been fully resolved. We sincerely apologize for any inconvenience this may have caused.
The maintenance is now complete. Thanks for your patience.