---
service: "Blockdaemon"
status: "partial_outage"
reports_last_hour: 0
reports_last_12_hours: 0
baseline_reports_per_hour: 1
checked_at: "2026-10-31T03:48:46.047Z"
url: "https://instatus.com/now/es-mx/blockdaemon.com"
official_status_page: "https://status.blockdaemon.com"
website: "https://www.blockdaemon.com"
---

# ¿Está Blockdaemon caído?

Está caído en parte. 0 informes en la última hora.

## Actualizaciones oficiales

- **[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.

## Preguntas frecuentes sobre caídas de Blockdaemon

### ¿Blockdaemon está inactivo en este momento?

Está caído en parte. 0 informes en la última hora.

### ¿Blockdaemon está caído para todos o solo para mí?

Parece que solo te pasa a ti. Los informes de Blockdaemon están en su nivel habitual, así que intenta recargar, revisar tu conexión o cerrar sesión y volver a entrar.

### ¿Qué problemas está reportando la gente de Blockdaemon?

Nadie ha dicho qué falla en Blockdaemon en la última hora. Si algo no te funciona, elígelo arriba para que lo vean los demás.

### ¿Cuándo fue la última caída de Blockdaemon?

Los informes de Blockdaemon no se han disparado en los últimos 30 días.

### ¿Blockdaemon tiene página de estado?

Sí. Blockdaemon publica novedades en su página de estado oficial, que ahora mismo indica: interrupción parcial.

[Ir a la página de estado](https://status.blockdaemon.com/)

### ¿Qué puedo hacer si Blockdaemon no funciona?

Revisa esta página y la página de estado de Blockdaemon para ver novedades, y espera unos minutos antes de volver a intentarlo. No lo reinstales: si es una caída, la solución está de su lado.

### ¿Cómo informo de un problema de Blockdaemon?

Pulsa «Yo también tengo un problema» en la parte superior de esta página y elige qué falla. Tu informe aparece en el gráfico en vivo en menos de un minuto, y puedes dejar un comentario para contar a los demás lo que ves.

### ¿Cómo lo sabe Instatus Now?

Combinamos los informes de las personas en esta página con la página de estado oficial de Blockdaemon, que revisamos cada minuto.
