-
Notifications
You must be signed in to change notification settings - Fork 9
heroku status
heroku-status
Heroku ステータスステータスはHerokuプラットフォームの現在のステータスとインシデントの履歴を提供します。Heroku ステータスは、Herokuプラットフォームのすべてのスタック(Aspen, Bamboo, Cedar)をカバーしています。また本番アプリケーションの円滑な運営のために必要な常用なアドオンのステータスもカバーしています。
現在のステータスや問題の履歴は以下で確認出来ます。
Heroku クライアントからも現在のHerokuプラットフォームのステータスを確認出来ます。
:::term
$ heroku status
=== Heroku Status
Development: No known issues at this time.
Production: No known issues at this time.
ステータスサイトではHerokuプラットフォームの現在のステータスは、ここ一ヶ月の稼働時間、最近のインシデント時間をProductionとDevelopmentに分けて表示しています。それらは自動アップデートされます。
Production には、少なくとも2つのweb dynosとProduction版データベース(もしくはまったくデータベースを利用していない)を利用した安定して稼働中のProductionアプリケーションに影響を与える問題が掲載されます。dynosやデータベース、キャッシュ機構(HTTPキャッシンクとmemcached)、また他のコンポーネント(DelayedJob workers, scheduler、など)やルーティングを含みます。
Development には、開発ワークフローとツールに影響を与える問題が掲載されます。開発環境(git push, gemインストール, slugコンパイルなどを含みます)一般的なgit活動や、コマンドライン gem api (スケーリングやコンフィグ設定など) や関連サービス (rake, console, TAPを利用 db push/pull など) またDevelopmentは1-dyno以下の本番環境ではないアプリケーションや共有データベースを含みます。
稼働時間の数値は、影響を受けるユーザーの割合に基づいた加重平均ですサードパーティアドオンのサイトに障害情報が掲載されている場合においてもHerokuの稼働時間の計算には含まれません。
プラットフォームに影響を与える問題のアラートを配信しているメールのサービスがあります。Herokuステータスサイト へアクセスし 通知を購読するをクリックして下さい。 また twitter の Herokuステータスアカウントをフォローしたり, RSS feedを購読して下さい。status APIから確認することもできます。
障害が疑われる場合は、ステータスサイトを参照してください。何も報告されていないか、または報告されているものとは異なる何かが発生している場合、(https://support.heroku.com/tickets/new)[サポートチケットの送信]からチケットを作成して下さい。
:::term
$ curl "https://status.heroku.com/api/v3/current-status"
{"status":{"Production":"green","Development":"green"},"issues":[]}
:::term
$ curl "https://status.heroku.com/api/v3/issues?since=2012-04-24&limit=1"
[{"created_at":"2012-04-24T14:02:39Z","id":336,"resolved":true,"title":"Custom Domains: Errors Adding / Updating","updated_at":"2012-04-24T15:24:58Z","updates":[{"contents":"The fix has been applied, and custom domains are functioning as expected.\r\n\r\nFurther investigation shows that custom domains created or updated after 4/23/2012 19:50 UTC were affected.","created_at":"2012-04-24T15:24:58Z","id":980,"incident_id":336,"status_dev":"green","status_prod":"green","update_type":"resolved","updated_at":"2012-04-24T15:24:58Z"},{"contents":"All previously malfunctioning custom domains are now online. Engineers are continuing to roll out the fix.","created_at":"2012-04-24T15:06:53Z","id":979,"incident_id":336,"status_dev":"green","status_prod":"green","update_type":"update","updated_at":"2012-04-24T15:06:53Z"},{"contents":"The issue has been identified and engineers are working to fix.","created_at":"2012-04-24T14:45:49Z","id":978,"incident_id":336,"status_dev":"green","status_prod":"green","update_type":"update","updated_at":"2012-04-24T14:45:49Z"},{"contents":"Engineers are still investigating the source of issues regarding custom domains. We have determined that only domains added or updated in the past 24 hours should be affected.\r\n\r\nWe'll continue to provide more information as it becomes available.","created_at":"2012-04-24T14:23:58Z","id":977,"incident_id":336,"status_dev":"green","status_prod":"green","update_type":"update","updated_at":"2012-04-24T15:08:53Z"},{"contents":"Engineers are investigating issues with custom domains around applications. We will provide more information as it becomes available.","created_at":"2012-04-24T14:02:39Z","id":976,"incident_id":336,"status_dev":"yellow","status_prod":"yellow","update_type":"issue","updated_at":"2012-04-24T14:02:50Z"}]}]
:::term
$ curl "https://status.heroku.com/api/v3/issues/336"
{"created_at":"2012-04-24T14:02:39Z","id":336,"resolved":true,"title":"Custom Domains: Errors Adding / Updating","updated_at":"2012-04-24T15:24:58Z","updates":[{"contents":"The fix has been applied, and custom domains are functioning as expected.\r\n\r\nFurther investigation shows that custom domains created or updated after 4/23/2012 19:50 UTC were affected.","created_at":"2012-04-24T15:24:58Z","id":980,"incident_id":336,"status_dev":"green","status_prod":"green","update_type":"resolved","updated_at":"2012-04-24T15:24:58Z"},{"contents":"All previously malfunctioning custom domains are now online. Engineers are continuing to roll out the fix.","created_at":"2012-04-24T15:06:53Z","id":979,"incident_id":336,"status_dev":"green","status_prod":"green","update_type":"update","updated_at":"2012-04-24T15:06:53Z"},{"contents":"The issue has been identified and engineers are working to fix.","created_at":"2012-04-24T14:45:49Z","id":978,"incident_id":336,"status_dev":"green","status_prod":"green","update_type":"update","updated_at":"2012-04-24T14:45:49Z"},{"contents":"Engineers are still investigating the source of issues regarding custom domains. We have determined that only domains added or updated in the past 24 hours should be affected.\r\n\r\nWe'll continue to provide more information as it becomes available.","created_at":"2012-04-24T14:23:58Z","id":977,"incident_id":336,"status_dev":"green","status_prod":"green","update_type":"update","updated_at":"2012-04-24T15:08:53Z"},{"contents":"Engineers are investigating issues with custom domains around applications. We will provide more information as it becomes available.","created_at":"2012-04-24T14:02:39Z","id":976,"incident_id":336,"status_dev":"yellow","status_prod":"yellow","update_type":"issue","updated_at":"2012-04-24T14:02:50Z"}]}