Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    1. Inicio
    2. Servicios
    3. Quicknode

    Última comprobación 26 oct, 23:53 UTC

    Estado de Quicknode

    Blockchain infrastructure for secure, decentralized innovation.

    ¿Tienes algún problema?

    Logotipo de Quicknode

    ¿Quicknode está caído?

    Rendimiento degradado

    ¿Tienes problemas con Quicknode?

    Comparte tu experiencia para mantener informados a los demás.

    Estado actualGráfico de estadoReportes de problemasMapa de interrupcionesSeñales socialesHistorial de estadoComponentesHistorial de incidentesMantenimientoComunidadReseñasAcerca dePreguntas frecuentesMonitorizar servicioServicios similaresComparación

    Actividad reciente

    Últimas 24 horas
    1. Estado oficial verificado

      Quicknode is experiencing issues

      Estado oficial del proveedor
      26 oct, 23:53 UTC
    2. Mantenimiento oficial activo

      [Urgent] NEAR - Mainnet - Upgrade to 2.14.0 — We are upgrading our NEAR Mainnet infrastructure to nearcore 2.14.0 on 2026-10-30. This is a mandatory protocol upgrade (protocol version 86 to 88) introducing consensus-breaking changes, new action validation rules, and improved cryptographic support. Validators must upgrade before protocol version 87 voting begins on November 4th. Brief interruptions to RPC availability may occur on that date. RPC Changes: - view_access_key_list now supports pagination with after_key and limit parameters, returning a last_key field. Accounts with more than 100 access keys must use pagination; unpaginated requests for these accounts will fail. - tx, send_tx, and broadcast_tx_commit responses now include an optional cause field on TIMEOUT_ERROR, describing transaction progress (NOT_OBSERVED, PENDING, DOES_NOT_TRACK_SHARD, or ERROR). - tx_status is now the stable method name for what was EXPERIMENTAL_tx_status. Both names work identically; Quicknode documentation for tx_status is in progress. https://github.com/near/nearcore/releases/tag/2.14.0

      Estado oficial del proveedor
      26 oct, 20:12 UTC
    3. Mantenimiento oficial activo

      [Urgent] Stacks Mainnet - Upgrade to v9.7.0 — We are upgrading our Stacks Mainnet infrastructure to v9.7.0 on 2026-11-02. This release patches recent Node.js security vulnerabilities and introduces new v3 API endpoints for block and transaction data, along with enhanced transaction metadata. A brief database migration will occur during the upgrade, and brief interruptions to RPC availability may occur on that date. RPC Changes: - GET /extended/v3/blocks — New cursor-paginated endpoint for Stacks block summaries, including tenure_height, tx_count, and Bitcoin anchor block reference. - GET /extended/v3/blocks/{height_or_hash} — New endpoint providing Stacks block details, including parent block hash, block size, and execution cost. - GET /extended/v3/bitcoin-blocks — New cursor-paginated endpoint for Bitcoin block summaries with header time and associated Stacks/transaction counts. - GET /extended/v3/bitcoin-blocks/{height_or_hash} — New endpoint providing Bitcoin block details with header time and associated block/transaction counts. - GET /extended/v3/bitcoin-blocks/{height_or_hash}/blocks — New endpoint listing Stacks blocks anchored to a specific Bitcoin block. - event_count — Added to v3 transaction summaries across all v3 endpoints (transactions list, batch, block transactions, principal transactions, and search). - /v2 RPC proxy — Simplified to a plain passthrough; custom fee estimation and transaction endpoint configuration are no longer available. https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v9.7.0

      Estado oficial del proveedor
      26 oct, 15:45 UTC
    4. Incidente oficial activo

      Solana Testnet: Planned network halt — Solana testnet has been halted by Anza as part of their planned stabilization process. Block production is paused network-wide until the cluster restarts. We're following Anza's restart process and will bring our nodes back online as soon as the network resumes. Solana mainnet and devnet are not affected.

      Estado oficial del proveedor
      26 oct, 14:07 UTC

    Reportes de problemas de Quicknode

    0 reportes individuales en las últimas 24 horas. Esta lista incluye importaciones históricas; los agregados de fuentes externas se muestran en el gráfico.

    No hay reportes recientes de interrupciones

    La comunidad no ha enviado reportes de interrupciones para este servicio en las últimas 24 horas.

    Recibe notificaciones cuando cambie el estado de Quicknode

    Notificaciones por correo, push y webhook.

    Empezar a monitorizar

    Mapa de Interrupciones

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Ver mapa completo

    Mapa de Interrupciones

    Loading report locations…

    Historial de estado de Quicknode

    Observaciones del estado oficial, no mediciones directas de disponibilidad.

    Componentes de Quicknode

    Nombre del componenteEstado

    Hay más componentes disponibles abajo.

    Historial de incidentes de Quicknode

    Los incidentes oficiales, las alertas tempranas y los reportes de la comunidad se identifican por separado. Las alertas tempranas abarcan las últimas 24 horas. Las fechas usan tu zona horaria.

    Ver más historial
    Nombre del incidenteDuraciónInicioUTCConfirmación oficialGravedad
    Estado oficial·Sin resolver10h 25mEn curso26 oct 202614:07 UTCSíLeve
    Estado oficial·Resuelto30m25 oct 202623:57 UTCSíLeve
    Estado oficial·Resuelto1h 5m23 oct 20268:00 UTCSíDesconocido
    Estado oficial·Resuelto1h 21m19 oct 20269:38 UTCSíLeve
    Estado oficial·Resuelto53m13 oct 202615:23 UTCSíDesconocido
    Estado oficial·Resuelto13h 29m10 oct 20268:50 UTCSíGrave
    Estado oficial·Resuelto2h10 oct 20262:00 UTCSíLeve
    Estado oficial·Resuelto10m9 oct 202613:21 UTCSíDesconocido

    Acerca de la supervisión de Quicknode en Uptimus

    Uptimus supervisa Quicknode mediante su fuente oficial y normaliza incidencias, mantenimiento y componentes en un estado coherente.

    Esta página incluye actualmente 231 componentes supervisados, 152 incidencias, 293 mantenimientos y 78 días de historial conocido.

    Uptimus es un servicio independiente y no está afiliado con Quicknode. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.

    Cómo supervisa Uptimus Quicknode

    Recibe alertas cuando Quicknode o uno de sus componentes supervisados informa de una interrupción grave o crítica. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas. El historial disponible contiene 152 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Solana Testnet: Planned network halt».

    Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 231 componentes de Quicknode. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.

    Notificaciones de mantenimiento

    Mantenimiento programado

    Trabajos programados publicados por el proveedor oficial.

    1. ✓

      [Standard] Morph - Hoodi Mainnet - Upgrade to v0.6.4 & morph-v2.2.7 (Celadon Fork)

      Mantenimiento

      We are upgrading our Morph Mainnet infrastructure to node v0.6.4 and morph-v2.2.7 ahead of the mandatory Celadon network upgrade, which activates on Hoodi Testnet at 2026-10-28 06:00 UTC. Celadon introduces MorphTx v2, which lets users pay gas with an alternative token and delegate their EOA to contract code (EIP-7702) in a single transaction. It also corrects the rounding of alt-token fee refunds, so users are charged the precisely rounded net fee. All existing transaction types, including MorphTx v0/v1 and standard 0x04 SetCode transactions, remain fully supported. During the maintenance window, brief interruptions to RPC availability may occur. RPC changes: - eth_sendRawTransaction — MorphTx v2 (type 0x7F, version 0x02) is accepted once Celadon activates. Before activation, v2 transactions are rejected. - Transaction-building requests (e.g. eth_sendTransaction, eth_estimateGas) — The MorphTx version no longer needs to be specified and is derived from the request. A non-empty authorizationList combined with feeTokenID, reference, or memo builds a v2 transaction. Otherwise, v1 is used. - eth_getTransactionByHash — Now returns authorizationList for MorphTx v2 transactions. - MorphTx v2 transactions with a non-empty authorizationList cannot create contracts (same rule as EIP-7702). - Fees for transactions paying gas in an alternative token may differ slightly from previous values due to the corrected refund rounding. https://github.com/morph-l2/morph/releases/tag/v0.6.4 https://github.com/morph-l2/go-ethereum/releases/tag/morph-v2.2.7

      Inicio 2 nov 2026, 00:00 UTC · En curso

    2. ✓

      [Urgent] Stacks Mainnet - Upgrade to v9.7.0

      Mantenimiento

      We are upgrading our Stacks Mainnet infrastructure to v9.7.0 on 2026-11-02. This release patches recent Node.js security vulnerabilities and introduces new v3 API endpoints for block and transaction data, along with enhanced transaction metadata. A brief database migration will occur during the upgrade, and brief interruptions to RPC availability may occur on that date. RPC Changes: - GET /extended/v3/blocks — New cursor-paginated endpoint for Stacks block summaries, including tenure_height, tx_count, and Bitcoin anchor block reference. - GET /extended/v3/blocks/{height_or_hash} — New endpoint providing Stacks block details, including parent block hash, block size, and execution cost. - GET /extended/v3/bitcoin-blocks — New cursor-paginated endpoint for Bitcoin block summaries with header time and associated Stacks/transaction counts. - GET /extended/v3/bitcoin-blocks/{height_or_hash} — New endpoint providing Bitcoin block details with header time and associated block/transaction counts. - GET /extended/v3/bitcoin-blocks/{height_or_hash}/blocks — New endpoint listing Stacks blocks anchored to a specific Bitcoin block. - event_count — Added to v3 transaction summaries across all v3 endpoints (transactions list, batch, block transactions, principal transactions, and search). - /v2 RPC proxy — Simplified to a plain passthrough; custom fee estimation and transaction endpoint configuration are no longer available. https://github.com/hirosystems/stacks-blockchain-api/releases/tag/v9.7.0

      Inicio 2 nov 2026, 00:00 UTC · En curso

    3. ✓

      [Urgent] NEAR - Mainnet - Upgrade to 2.14.0

      Mantenimiento

      We are upgrading our NEAR Mainnet infrastructure to nearcore 2.14.0 on 2026-10-30. This is a mandatory protocol upgrade (protocol version 86 to 88) introducing consensus-breaking changes, new action validation rules, and improved cryptographic support. Validators must upgrade before protocol version 87 voting begins on November 4th. Brief interruptions to RPC availability may occur on that date. RPC Changes: - view_access_key_list now supports pagination with after_key and limit parameters, returning a last_key field. Accounts with more than 100 access keys must use pagination; unpaginated requests for these accounts will fail. - tx, send_tx, and broadcast_tx_commit responses now include an optional cause field on TIMEOUT_ERROR, describing transaction progress (NOT_OBSERVED, PENDING, DOES_NOT_TRACK_SHARD, or ERROR). - tx_status is now the stable method name for what was EXPERIMENTAL_tx_status. Both names work identically; Quicknode documentation for tx_status is in progress. https://github.com/near/nearcore/releases/tag/2.14.0

      Inicio 30 oct 2026, 00:00 UTC · En curso

    4. ✓

      [Standard] Bitcoin Mainnet - Upgrade ord to 0.29.1

      Mantenimiento

      We are upgrading our Bitcoin Mainnet Ordinals infrastructure from ord 0.23.2 to 0.29.1. This release rolls up several versions of indexer improvements, including richer inscription metadata in API responses, new gallery and bulk lookup endpoints, a new recursive endpoint for raw block data, and a fix for indexing transactions that include pay-to-anchor outputs. During the maintenance window, brief interruptions to Ordinals API availability may occur. RPC Changes: - Inscription JSON responses — added. Inscription responses now include a properties object (attributes, traits, title, and gallery items) along with the metaprotocol field. - Inscription parents — fixed. Invalid parents are now filtered out and no longer returned for inscriptions. - /children routes — added. Child inscription routes now support JSON responses. - /gallery — added. New JSON endpoint for retrieving gallery inscriptions, with paginated gallery items. - /galleries and /collections — changed. /collections now returns results in reverse order, and hidden inscriptions are excluded from both /collections and /galleries. - /missing — added. New endpoint to check whether a batch of inscriptions exists in a single request. - /r/block/ — added. New recursive endpoint that returns the raw block hex for a given block hash or height. - Block inscriptions pagination — changed. Requests for an out-of-range page now return an empty page instead of an error. - Outpoint and TXID lookups — fixed. Outpoints and TXIDs made up entirely of decimal digits now resolve correctly instead of being misrouted. - Sat lookups — fixed. "Not found" sat index responses are no longer cached, so subsequent lookups return current data. - Rune amounts — fixed. Decimal amounts with excessive precision or values that would overflow now return a proper error. - Pay-to-anchor outputs — fixed. Transactions containing pay-to-anchor (P2A) outputs are now indexed correctly. Prior versions could return incorrect inscription and output data for these transactions. https://github.com/ordinals/ord/releases/tag/0.29.1

      Inicio 28 oct 2026, 00:00 UTC · En curso

    5. ✓

      [Standard] Hedera Mainnet - Upgrade to Mirror Node v0.165.0 & RPC Relay v0.80.2

      Mantenimiento

      We are upgrading our Hedera Mainnet infrastructure to Mirror Node v0.165.0 and RPC Relay v0.80.2 on 2026-10-28. This release prepares the mirror node for the Nova/TSS 3.22.0 consensus-layer transition, introduces cryptographic improvements to block proof handling, and adds new REST and gRPC endpoints with enhanced security hardening. Brief interruptions to RPC availability may occur on that date. RPC Changes: Block proof hashing — Block proof hashing is transitioning to a new format. Dual support for both block proof formats is maintained during the rollout period to enable gradual operator deployment. https://github.com/hiero-ledger/hiero-mirror-node/releases/tag/v0.165.0

      Inicio 28 oct 2026, 00:00 UTC · En curso

    6. ✓

      Standard Fluent - Mainnet & Testnet - Upgrade to v1.5.1

      Mantenimiento

      We are upgrading our Fluent infrastructure to v1.5.1 on 2026-10-28. This release introduces native Ethereum precompiles (0x01–0x11 and P256VERIFY) via revm for significantly faster cryptographic operations, upgrades the rWasm runtime to 0.7.2 for improved consensus safety, and enforces a protocol-level transaction gas cap. Brief interruptions to RPC availability may occur on that date. RPC Changes: eth_sendTransaction / eth_sendRawTransaction — Transactions exceeding 100 Mgas will be rejected by the network (EIP-7825 with Fluent-specific limit); clients sending such transactions will receive rejection errors. Precompile execution (ecrecover, keccak256, sha256, ripemd160, bigModExp, bn256Add, bn256ScalarMul, bn256Pairing, blake2f, KZG, BLS12-381) — All Ethereum precompiles now execute via native revm implementations at the same addresses with identical gas costs and results, but with several times faster performance. https://github.com/fluentlabs-xyz/fluentbase/releases/tag/v1.5.1

      Inicio 28 oct 2026, 00:00 UTC · En curso

    7. ✓

      [Standard] Morph - Hoodi Testnet - Upgrade to v0.6.4 & morph-v2.2.7 (Celadon Fork)

      Mantenimiento

      We are upgrading our Morph Hoodi Testnet infrastructure to node v0.6.4 and morph-v2.2.7 ahead of the mandatory Celadon network upgrade, which activates on Hoodi Testnet at 2026-10-28 06:00 UTC. Celadon introduces MorphTx v2, which lets users pay gas with an alternative token and delegate their EOA to contract code (EIP-7702) in a single transaction. It also corrects the rounding of alt-token fee refunds, so users are charged the precisely rounded net fee. All existing transaction types, including MorphTx v0/v1 and standard 0x04 SetCode transactions, remain fully supported. During the maintenance window, brief interruptions to RPC availability may occur. RPC changes: - eth_sendRawTransaction — MorphTx v2 (type 0x7F, version 0x02) is accepted once Celadon activates. Before activation, v2 transactions are rejected. - Transaction-building requests (e.g. eth_sendTransaction, eth_estimateGas) — The MorphTx version no longer needs to be specified and is derived from the request. A non-empty authorizationList combined with feeTokenID, reference, or memo builds a v2 transaction. Otherwise, v1 is used. - eth_getTransactionByHash — Now returns authorizationList for MorphTx v2 transactions. - MorphTx v2 transactions with a non-empty authorizationList cannot create contracts (same rule as EIP-7702). - Fees for transactions paying gas in an alternative token may differ slightly from previous values due to the corrected refund rounding. https://github.com/morph-l2/morph/releases/tag/v0.6.4 https://github.com/morph-l2/go-ethereum/releases/tag/morph-v2.2.7

      Inicio 27 oct 2026, 00:00 UTC · En curso

    8. ✓

      [Standard] Gravity Mainnet - Upgrade to v1.10.1

      Mantenimiento

      We are upgrading our Gravity Mainnet infrastructure to v1.10.1 on 2026-10-27. This release contains bugfixes and optimizations, including improvements to RPC block-replay endpoints, consensus recovery at epoch boundaries, and startup stability. There is no hardfork and no new activation time. Brief interruptions to RPC availability may occur on that date. RPC Changes: - debug_trace*, trace_*, eth_callMany — Block replay now follows Gravity's execution rules, including system/user precompile sets, Alpha gas exemption, activation-block state changes, EIP-2935 handling, and onBlockStart logic. Requests targeting pending blocks will now fail; only committed blocks can be replayed. debug_executionWitness* — This endpoint is now refused for all blocks. https://github.com/Galxe/gravity-sdk/releases/tag/v1.10.1

      Inicio 27 oct 2026, 00:00 UTC · En curso

    Recibe alertas cuando Quicknode publica mantenimiento planificado, programado o activo. Uptimus ha indexado 293 ventanas de mantenimiento del historial disponible de Quicknode. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
    Notificaciones de recuperación
    Entérate cuando Quicknode o un componente afectado vuelve a funcionar correctamente. La página contiene 78 días de historial conocido y conserva los eventos resueltos para su revisión. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
    Mensajes de estado
    Uptimus conserva el título de la incidencia publicado por Quicknode y lo muestra con el estado normalizado. El historial disponible contiene 152 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Solana Testnet: Planned network halt».
    Detalles del estado
    Las actualizaciones de incidencias y mantenimiento se conservan para seguir la investigación, mitigación y recuperación. Una actualización oficial reciente conservada por Uptimus dice: «Solana testnet has been halted by Anza as part of their planned stabilization process. Block production is paused network-wide until the cluster restarts. We're following Anza's restart process and will bring our nodes back online as soon as the network res…».
    Filtrado de componentes
    Elige todos los componentes o solo los productos de Quicknode que utilizas. Las alertas oficiales respetan esa selección. Uptimus supervisa actualmente 231 componentes de Quicknode. El filtrado modifica las alertas oficiales entregadas, pero no elimina los eventos del historial público.

    Preguntas Frecuentes

    Recibe notificaciones cuando cambie el estado de Quicknode

    Empezar a monitorizar
    Servicios similares
    Comparación

    Uptimus vs Downdetector para Quicknode

    Las páginas públicas de Downdetector se centran en los reportes de usuarios. Uptimus combina esa actividad con incidentes oficiales, mantenimientos y salud de componentes cuando el proveedor los publica.

    Uptimus vs Downdetector para Quicknode
    Criterios de comparaciónUptimusDowndetector
    Reportes de la comunidad sobre QuicknodeIncluidoIncluido
    Línea base adaptativa que separa casos aislados de una interrupción ampliaIncluidoIncluido
    Actividad de reportes de 24 horas y vista regional de interrupcionesIncluidoIncluido
    Un espacio para sitios web, proveedores de estado, juegos de Steam y aplicaciones y juegos AndroidIncluidoProducto separado
    Alertas por correo, push y webhook desde el mismo espacioIncluidoProducto separado
    Actualizaciones oficiales de incidentes y cronología de QuicknodeIncluidoBasado en reportes
    Salud de componentes y mantenimientos mostrados por separadoIncluidoLimitado en páginas públicas
    IncluidoBasado en reportes · Limitado en páginas públicasProducto separado

    La página oficial de estado de Quicknode comunica rendimiento degradado. Hay un incidente oficial sin resolver: «Solana Testnet: Planned network halt». Componentes reportados como afectados: Solana - Testnet. Se registraron 0 reportes de Quicknode en las últimas 24 horas. Última comprobación oficial: 26 oct, 23:53 UTC.

    Más servicios para monitorear

    Descubre otros servicios populares y su estado actual

    Ver todos los servicios
    Character.aiCall of Duty®GportalDerivCoverallsActivtrakEmburseCsis Security GroupMakeiCloud

    Califica este servicio

    ¿Cómo calificarías Quicknode durante el último mes?

    Aún no hay reseñas

    (Límite de una reseña por mes)

    Discusión de la Comunidad

    Comparte tus pensamientos sobre Quicknode

    A
    Aún no hay comentarios

    ¡Sé el primero en comentar!