--- service: "Blockdaemon" status: "partial_outage" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 1 checked_at: "2026-10-31T18:50:41.531Z" url: "https://instatus.com/now/pl/blockdaemon.com" official_status_page: "https://status.blockdaemon.com" website: "https://www.blockdaemon.com" --- # Czy Blockdaemon nie działa? Częściowo nie działa. 0 raportów w ostatniej godzinie. ## Oficjalne aktualizacje - **[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 – awarie: FAQ ### Czy Blockdaemon jest teraz wyłączony? Częściowo nie działa. 0 raportów w ostatniej godzinie. ### Czy Blockdaemon nie działa u wszystkich, czy tylko u mnie? Wygląda na to, że problem jest tylko u Ciebie. Zgłoszenia dla Blockdaemon są na zwykłym poziomie, więc spróbuj odświeżyć stronę, sprawdzić połączenie albo wylogować się i zalogować ponownie. ### Jakie problemy zgłaszają ludzie z Blockdaemon? W ostatniej godzinie nikt nie napisał, co nie działa w Blockdaemon. Jeśli u Ciebie coś nie działa, wybierz to powyżej, żeby inni to zobaczyli. ### Kiedy była ostatnia awaria Blockdaemon? Zgłoszenia dla Blockdaemon nie nasiliły się w ciągu ostatnich 30 dni. ### Czy Blockdaemon ma stronę statusu? Tak. Blockdaemon publikuje aktualizacje na oficjalnej stronie statusu, która obecnie podaje: częściowa awaria. [Przejdź do strony statusu](https://status.blockdaemon.com/) ### Co mogę zrobić, jeśli Blockdaemon nie działa? Sprawdź tę stronę i stronę statusu Blockdaemon, żeby poznać aktualizacje, i odczekaj kilka minut przed kolejną próbą. Nie instaluj ponownie: jeśli to awaria, naprawa leży po ich stronie. ### Jak zgłosić problem z Blockdaemon? Kliknij „Ja też mam problem” u góry tej strony i wybierz, co nie działa. Twoje zgłoszenie pojawi się na wykresie na żywo w ciągu minuty, a komentarzem możesz dać znać innym, co widzisz. ### Skąd Instatus Now to wie? Łączymy zgłoszenia osób z tej strony z oficjalną stroną statusu Blockdaemon, którą sprawdzamy co minutę.