VulnPulse

最新のセキュリティ情報

9月24日(木)

8月26日(水)

8月19日(水)

8月11日(火)

  • 解決済み00:26障害・メンテナンスHerokuHeroku Status

    Resolved: Heroku Feature Degradation

    We are aware of an issue that affected the ability to provision new Heroku Data add-ons. To remediate, we completed a rollback of a recent change and validated that all services have been restored. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

8月7日(金)

  • 解決済み01:17障害・メンテナンスHerokuHeroku Status

    Resolved: Heroku Retroactive Feature Degradation

    Between 11:01 UTC on August 6, 2026 and 13:10 UTC on August 6, 2026, we identified a performance issue affecting Heroku release phase deploys. During this time, some customers experienced delayed completion of release phase commands during deploys, with some remaining in an release phase executing state longer than expected. We have confirmed that the issue is resolved. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat i…

7月6日(月)

6月20日(土)

  • 解決済み03:47障害・メンテナンスHerokuHeroku Status

    Resolved: Heroku Retroactive Service Disruption

    We noted an issue that impacted Heroku Platform API services in all regions. Customers may have experienced broken pipeline API calls to ‘pipelines/:id/latest-builds’, and issues viewing the pipeline dashboard. We confirmed this incident was due to a recently deployed change, and have reverted this change to resolve the issue. We will continue to monitor the environment to ensure stability and prevent a recurrence. We will also thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and any preventive action to avoid a repeat in the future.

6月10日(水)

5月22日(金)

5月8日(金)

  • 解決済み12:55障害・メンテナンスHerokuHeroku Status

    Resolved: Heroku Service Disruption

    We have successfully applied the fix to all remaining affected customers. Heroku databases and web applications are now fully operational for all customers. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

5月5日(火)

  • 解決済み23:57障害・メンテナンスHerokuHeroku Status

    Resolved: Heroku Feature Disruption

    Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

4月30日(木)

3月13日(金)

2月24日(火)

  • 解決済み07:28障害・メンテナンスHerokuHeroku Status

    Resolved: Heroku Retroactive Feature Degradation

    Customers using Heroku in the Common Runtime may have experienced intermittent dyno disruptions earlier today between 17:50 UTC and 20:24 UTC. The issue has been resolved after we disabled a related service and rolled back a recent change. We’re validating the update in lower environments and will continue monitoring for stability.

2月22日(日)