--- service: "Blockdaemon" status: "partial_outage" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 1 checked_at: "2026-10-31T18:30:19.183Z" url: "https://instatus.com/now/pt/blockdaemon.com" official_status_page: "https://status.blockdaemon.com" website: "https://www.blockdaemon.com" --- # O Blockdaemon está inativo? Está parcialmente inativo. 0 relatórios na última hora. ## Atualizações oficiais - **[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. ## Perguntas frequentes sobre falhas do Blockdaemon ### O Blockdaemon está inativo agora? Está parcialmente inativo. 0 relatórios na última hora. ### O Blockdaemon está inativo para todos ou só para mim? Parece que é só consigo. Os relatos do Blockdaemon estão no nível habitual, por isso experimente recarregar, verificar a ligação ou terminar sessão e entrar de novo. ### Que problemas as pessoas estão a relatar com o Blockdaemon? Ninguém disse o que está com problemas no Blockdaemon na última hora. Se algo não funciona consigo, escolha acima para os outros verem. ### Quando foi a última falha do Blockdaemon? Os relatos do Blockdaemon não tiveram picos nos últimos 30 dias. ### O Blockdaemon tem uma página de estado? Sim. O Blockdaemon publica atualizações na página de estado oficial, que neste momento indica: interrupção parcial. [Ir para a página de estado](https://status.blockdaemon.com/) ### O que posso fazer se o Blockdaemon não funciona? Consulte esta página e a página de estado do Blockdaemon para novidades e aguarde alguns minutos antes de tentar de novo. Não reinstale: se for uma falha, a correção é do lado deles. ### Como reporto um problema do Blockdaemon? Toque em “eu também tenho um problema” no topo desta página e escolha o que não funciona. O seu relato aparece no gráfico em direto em menos de um minuto, e pode deixar um comentário para dizer aos outros o que está a ver. ### Como sabe o Instatus Now? Combinamos os relatos de quem está nesta página com a página de estado oficial do Blockdaemon, que verificamos a cada minuto.