--- service: "Blockdaemon" status: "partial_outage" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 1 checked_at: "2026-10-31T18:36:57.903Z" url: "https://instatus.com/now/be/blockdaemon.com" official_status_page: "https://status.blockdaemon.com" website: "https://www.blockdaemon.com" --- # Blockdaemon не працуе? Часткова не працуе. 0 паведамленняў за апошнюю гадзіну. ## Афіцыйныя абнаўленні - **[Canton] - Mainnet Network-Wide Topology Freeze (Upstream Event)** (SCHEDULED, 2026-11-06T14:00:00.000Z): The Canton network is applying a topology freeze on Mainnet in preparation for the Logical Synchronizer Upgrade (LSU). This is a network-wide event coordinated by the Canton Foundation, not Blockdaemon maintenance. Window: November 06, 2026, 14:00 UTC to November 07, 2026, 14:00 UTC (until after the LSU completes; may extend slightly) Impact: Transactions continue to work normally. Topology-changing operations will not succeed during the window, including new contract deployments, validator onboarding, and DAR uploads. Action required: None. Customers should schedule any topology-changing operations outside this window. We'll update this notice when the freeze is lifted. If you have any questions or concerns please reach out to your account managers. - **[xLayer] - Mainnet upgrade to xlayer-reth v0.0.7.3 and op-node xlayer v0.1.7** (SCHEDULED, 2026-11-04T10:00:00.000Z): Blockdaemon will update xLayer mainnet nodes to xlayer-reth v0.0.7.3 and op-node xlayer v0.1.7 on 11/04/2026 between 10:00 UTC and 11:00 UTC. We are updating our nodes due to a release from the xLayer foundation. This update applies to all Blockdaemon xLayer mainnet nodes, there will be planned downtime of up to 15 minutes per node. We have tested the release and do not anticipate any unexpected downtime other than mentioned above as a result of the update. If you have any questions or concerns please reach out to your Account Manager. If you want additional information please review the release notes here: https://github.com/okx/xlayer-reth/releases/tag/v0.0.7.3 https://github.com/okx/optimism/releases/tag/xlayer%2Fv0.1.7 - **[Canton] - Testnet Network-Wide Topology Freeze (Upstream Event)** (SCHEDULED, 2026-11-03T14:00:00.000Z): The Canton network is applying a topology freeze on Testnet in preparation for the Logical Synchronizer Upgrade (LSU). This is a network-wide event coordinated by the Canton Foundation, not Blockdaemon maintenance. Window: November 03, 2026, 14:00 UTC to November 04, 2026, 14:00 UTC (until after the LSU completes; may extend slightly) Impact: Transactions continue to work normally. Topology-changing operations will not succeed during the window, including new contract deployments, validator onboarding, and DAR uploads. Action required: None. Customers should schedule any topology-changing operations outside this window. We'll update this notice when the freeze is lifted. If you have any questions or concerns please reach out to your account managers. - **[Near] - Upgrade to Nearcore v2.14.0** (SCHEDULED, 2026-11-03T10:00:00.000Z): Blockdaemon will update Near mainnet nodes to v2.14.0 on 11/03/2026. We are updating our nodes due to a release from the Near foundation. This update applies to all Blockdaemon Near mainnet nodes, there will be planned downtime of up to 15 minutes per node. We have tested the release and do not anticipate any unexpected downtime other than mentioned above as a result of the update. If you have any questions or concerns please reach out to your Account Manager. If you want additional information please review the release note here: https://github.com/near/nearcore/releases/tag/2.14.0 - **[Ubiquity] - Aegis Event Streaming Upgrade** (SCHEDULED, 2026-11-02T14:00:00.000Z): Blockdaemon will be carrying out a scheduled database upgrade for Aegis Event Streaming on 11/02/2026 between 14:00 and 15:00 UTC. During this maintenance, Aegis event streaming services will be impacted, with downtime of up to 1 hour approximately. We have tested this upgrade and do not anticipate any impact beyond what is described above. If you have any questions or concerns, please reach out to your Account Manager. ## Частыя пытанні пра збоі Blockdaemon ### Blockdaemon не працуе зараз? Часткова не працуе. 0 паведамленняў за апошнюю гадзіну. ### Blockdaemon не працуе для ўсіх ці толькі ў мяне? Падобна, праблема толькі ў вас. Паведамленняў пра Blockdaemon столькі ж, колькі звычайна, таму паспрабуйце перазагрузіць старонку, праверыць злучэнне або выйсці і ўвайсці зноў. ### Пра якія праблемы з Blockdaemon паведамляюць людзі? За апошнюю гадзіну ніхто не напісаў, што не працуе ў Blockdaemon. Калі ў вас нешта не працуе, абярыце гэта вышэй, каб іншыя бачылі. ### Калі быў апошні збой Blockdaemon? Паведамленні пра Blockdaemon не раслі за апошнія 30 дзён. ### Ці ёсць у Blockdaemon старонка статусу? Так. Blockdaemon публікуе абнаўленні на сваёй афіцыйнай старонцы статусу, дзе цяпер напісана: частковая недаступнасць. [Перайсці на старонку стану](https://status.blockdaemon.com/) ### Што рабіць, калі Blockdaemon не працуе? Сачыце за абнаўленнямі на гэтай старонцы і на старонцы статусу Blockdaemon, а перад новай спробай пачакайце колькі хвілін. Не пераўсталёўвайце: калі гэта збой, выпраўленне на іх баку. ### Як паведаміць пра праблему з Blockdaemon? Націсніце «У мяне таксама праблема» уверсе гэтай старонкі і выберыце, што не працуе. Ваша паведамленне з'явіцца на жывым графіку за хвіліну, а каментарый дапаможа расказаць іншым, што вы бачыце. ### Адкуль Instatus Now гэта ведае? Мы аб'ядноўваем паведамленні людзей на гэтай старонцы з афіцыйнай старонкай статусу Blockdaemon, якую правяраем кожную хвіліну.