[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[[["\u003cp\u003eBlockchain Node Engine undergoes maintenance for various reasons, including blockchain client upgrades, new features, bug fixes, routine upkeep, and GKE cluster updates.\u003c/p\u003e\n"],["\u003cp\u003eNode upgrades may cause downtime ranging from under a minute to as long as 40 minutes, but in some cases, no downtime is incurred.\u003c/p\u003e\n"],["\u003cp\u003eRegular maintenance updates occur during scheduled windows on the first Monday of each month in different regions, with times ranging from 9 AM to 12 PM PST.\u003c/p\u003e\n"],["\u003cp\u003eUpdates occurring on a holiday will be rescheduled to the following business day, for each respective region.\u003c/p\u003e\n"],["\u003cp\u003eProvisioning multiple nodes across different locations can help to avoid downtime during maintenance.\u003c/p\u003e\n"]]],[],null,["# Blockchain Node Engine node upgrades and maintenance\n\nThis page describes processes and requirements regarding Blockchain Node Engine\nupgrades and maintenance windows.\n\nNode maintenance\n----------------\n\nBlockchain node maintenance occurs when the Blockchain Node Engine instance is\nupdated. This includes:\n\n- Upgrades of blockchain client software itself (e.g. an Ethereum upgrade)\n- Updates to Blockchain Node Engine business logic. For example:\n - New features\n - Bug fixes\n - Routine maintenance\n - GKE cluster software updates\n- Maintenance updates on the underlying infrastructure\n\nNode downtime\n-------------\n\nAlthough it is not common, node upgrades can cause downtime from as little as\na minute or less to up to 40 minutes. In some cases, the node pod itself does\nnot need to be restarted and there is no downtime.\n| **Tip:** To avoid downtime, provision multiple nodes across multiple locations to distribute the load.\n\nMaintenance windows\n-------------------\n\nWe plan to provide updates during regular windows as follows; however, there\ncould also be unplanned urgent updates. We will provide as much notice as\npossible."]]
