¿Quicknode está caído?

Parcialmente — Quicknode informa servicio degradado.

¿De dónde obtiene Uptimus el estado oficial de Quicknode?

Uptimus consulta la fuente oficial de Quicknode y normaliza incidencias, mantenimiento y estados de componentes. Los enlaces siguientes permiten verificar directamente la información del proveedor. Quicknode Status Page: https://status.quicknode.com Quicknode Home Page: https://www.quicknode.com

Quicknode indica que funciona, pero tengo problemas. ¿Qué puede ocurrir?

Es posible que la página oficial aún no refleje una incidencia nueva, que el problema afecte solo a algunas cuentas o regiones, o que sea local al dispositivo, red, software o proveedor de internet. Revisa los componentes y reportes, prueba otra conexión y contacta con el soporte de Quicknode si continúa.

¿Cómo puedo comprobar si Quicknode tiene problemas?

Compara el estado normalizado y las incidencias recientes de esta página con la fuente oficial. Uptimus reúne cambios de componentes, mantenimiento, reportes de la comunidad y detalles de incidencias para distinguir una interrupción general de un problema local.

¿Cómo recibir notificaciones sobre interrupciones de Quicknode?

Añade Quicknode a tu espacio de trabajo de Uptimus y elige los tipos de eventos y canales de entrega. Según el plan y la configuración, las alertas de interrupciones graves, problemas, mantenimiento y recuperación pueden enviarse por correo, push, webhook o integraciones configuradas. Si Quicknode publica componentes, puedes monitorearlos todos o limitar las alertas oficiales a los productos que utiliza tu equipo.

Last checked 12 ago, 9:03 p.m. UTC

Quicknode status

Blockchain infrastructure for secure, decentralized innovation.

Experiencing an issue?

¿Quicknode no funciona?

Degraded performance

Source: official status page

Having issues with Quicknode?

Share your experience to help others stay informed.

Quicknode service health graph

Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.

No problems detected
Possible problems
Problems detected
Early warning
Official incident

Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.

View chart data

15-minute report intervals · UTC
Start	End	Reports	Status

Latest activity

Last 24 hours

Official status checked
Quicknode is experiencing issues
Official provider status
12 ago, 9:03 p.m. UTC
Official incident active
Flare Mainnet Degraded Performance - Sporadic 503 Errors — We are continuing to monitor for any further issues.
Official provider status
12 ago, 8:35 p.m. UTC
Official maintenance active
[Standard] Hedera Mainnet & Testnet - Upgrade to Mirror Node v0.161.0 — We are upgrading our Hedera Mainnet and Testnet Mirror Node infrastructure to v0.161.0. This release focuses on security hardening, including vulnerable dependency updates, tightened input validation, and socket read bounds. The `/api/v1/network/fees` REST API now conditionally reads either the legacy fee schedule (0.0.111) or the new simple fees schedule (0.0.113) depending on the requested timestamp. During the maintenance window, brief interruptions to RPC availability may occur. RPC Changes: /api/v1/network/fees — Now conditionally serves the legacy fee schedule (0.0.111) or new simple fees schedule (0.0.113) based on the requested timestamp. https://github.com/hiero-ledger/hiero-mirror-node/releases/tag/v0.161.0
Official provider status
12 ago, 5:34 p.m. UTC
Official maintenance active
[Standard] OP Stack - Mainnets & Testnets - Upgrade to op-reth v2.4.1 & op-node v1.19.4 — We will be undergoing scheduled maintenance during this time.
Official provider status
12 ago, 5:02 p.m. UTC

Quicknode outage reports

0 outage reports in the last 24 hours.

No hay reportes recientes de fallas

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

Quicknode status history

Official status observations, not measured service uptime.

Last 60 daysDaily history

Loading history…

Operativo
Problemas
Falla
Mantenimiento
Sin datos

Quicknode components

Component name	Status

More components are available below.

Quicknode incident history

Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.

View more history

Incident name	Duration	StartedUTC	Acknowledged	Severity
Official statusMonitoring	643h 28mOngoing	12 ago 20263:42 p.m. UTC	Yes	Minor
Official statusResolved	16h 35m	12 ago 20264:00 a.m. UTC	Yes	Major
Official statusResolved	8h 54m	11 ago 20264:32 p.m. UTC	Yes	Minor
Official statusResolved	6h 48m	10 ago 202612:12 p.m. UTC	Yes	Minor
Official statusResolved	2h 34m	8 ago 20262:14 p.m. UTC	Yes	Minor
Official statusResolved	30m	8 ago 20266:30 a.m. UTC	Yes	Minor
Official statusResolved	54m	7 ago 202612:41 a.m. UTC	Yes	Unknown
Official statusResolved	2h 58m	6 ago 20269:19 p.m. UTC	Yes	Minor

Scheduled maintenance

Planned work published by the official provider.

[Standard] Hedera Mainnet & Testnet - Upgrade to Mirror Node v0.161.0
Maintenance
We are upgrading our Hedera Mainnet and Testnet Mirror Node infrastructure to v0.161.0. This release focuses on security hardening, including vulnerable dependency updates, tightened input validation, and socket read bounds. The `/api/v1/network/fees` REST API now conditionally reads either the legacy fee schedule (0.0.111) or the new simple fees schedule (0.0.113) depending on the requested timestamp. During the maintenance window, brief interruptions to RPC availability may occur. RPC Changes: /api/v1/network/fees — Now conditionally serves the legacy fee schedule (0.0.111) or new simple fees schedule (0.0.113) based on the requested timestamp. https://github.com/hiero-ledger/hiero-mirror-node/releases/tag/v0.161.0
Started Aug 20, 2026, 12:00 AM UTC · Ongoing
[Standard] Ethereum Mainnet and Testnets - Upgrade to Erigon v3.5.5 and Reth v2.5.0
Maintenance
We are upgrading our Ethereum Mainnet and Testnets infrastructure to Erigon v3.5.5 and Reth v2.5.0. These releases contain critical security fixes and corrections to data correctness bugs affecting RPC responses on archive nodes, particularly logIndex values. During the maintenance window, brief interruptions to RPC availability may occur. https://github.com/erigontech/erigon/releases/tag/v3.5.5 https://github.com/paradigmxyz/reth/releases/tag/v2.5.0
Started Aug 19, 2026, 02:00 PM UTC · Ongoing

Acerca del monitoreo de Quicknode en Uptimus

Uptimus monitorea Quicknode mediante su fuente oficial y normaliza incidentes, mantenimiento y componentes en un estado consistente.

Esta página incluye actualmente 594 componentes monitoreados, 86 incidentes, 148 mantenimientos y 57 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 monitorea 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 86 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Flare Mainnet Degraded Performance - Sporadic 503 Errors».

Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 594 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

Recibe alertas cuando Quicknode publica mantenimiento planificado, programado o activo. Uptimus ha indexado 148 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 57 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 86 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Flare Mainnet Degraded Performance - Sporadic 503 Errors».

Preguntas Frecuentes

Similar services

Comparison

Uptimus vs Downdetector para Quicknode
Criterios de comparación	Uptimus	Downdetector
Reportes de la comunidad sobre Quicknode

[Standard] Polkadot - Mainnet - Upgrade to v1.24.1

Maintenance

We are upgrading our Polkadot Mainnet infrastructure to v1.24.1 (polkadot-stable2606-1). This is a patch release containing bug fixes for a kvdb refcount leak, collator protocol PeerId handling, grandpa in-memory/DB synchronization, and incorrect dispatch class assignment for empty batch calls. A new curator-gated `increase_value` extrinsic has been added to pallet-multi-asset-bounties for managing bounty value increases. During the maintenance window, brief interruptions to RPC availability may occur. https://github.com/paritytech/polkadot-sdk/releases/tag/polkadot-stable2606-1

Started Aug 18, 2026, 02:00 PM UTC · Ongoing

[Standard] Gnosis - Mainnet - Upgrade to Nethermind v1.39.3

Maintenance

We are upgrading our Gnosis Mainnet infrastructure to Nethermind v1.39.3. This is a mandatory patch release that includes reliability and hardening fixes across block processing, networking, and request decoding. The upgrade hardens ABI decoding against malformed input, fixes memory cleanup issues in block processing and networking, and reduces allocations in EIP-6110 deposit-request decoding. During the maintenance window, brief interruptions to RPC availability may occur. https://github.com/NethermindEth/nethermind/releases/tag/1.39.3

Started Aug 13, 2026, 02:00 PM UTC · Ongoing

[Standard] Japan Open Chain - Nethermind v1.39.3

Maintenance

We are upgrading our Japan Open Chain infrastructure to Nethermind v1.39.3. This is a mandatory patch release that includes reliability and hardening fixes across block processing, networking, and request decoding. The upgrade hardens ABI decoding against malformed input, fixes memory cleanup issues in block processing and networking, and optimizes allocations in EIP-6110 deposit-request decoding. During the maintenance window, brief interruptions to RPC availability may occur. https://github.com/NethermindEth/nethermind/releases/tag/1.39.3

Started Aug 13, 2026, 02:00 PM UTC · Ongoing

[Urgent] Zcash Mainnet & Testnet - Zebra 6.3.0

Maintenance

We are upgrading our Zcash Mainnet infrastructure to Zebra 6.3.0. This release addresses security vulnerabilities in peer scoring and connection handling, along with stability improvements and new RPC functionality. The upgrade includes enhanced Prometheus metrics for better observability and new DNS seeders to improve network connectivity. During the maintenance window, brief interruptions to RPC availability may occur. RPC Changes: - getdeprecationinfo — New RPC method returning the block height and estimated time at which this release will halt for end of support, in zcashd's end_of_service format (Mainnet only). - getblocksubsidy — Now returns NU6-era funding stream metadata (recipient names and specification URLs) for NU6.1 and later upgrades. https://github.com/ZcashFoundation/zebra/releases/tag/v6.3.0

Started Aug 13, 2026, 11:00 AM UTC · Ongoing

Quicknode status

Having issues with Quicknode?

Quicknode service health graph

Quicknode activity

Latest activity

Quicknode outage reports

Mapa de fallas de Quicknode

Mapa de fallas de Quicknode

Quicknode status history

Quicknode components

Quicknode incident history

Scheduled maintenance

[Standard] Hedera Mainnet & Testnet - Upgrade to Mirror Node v0.161.0

[Standard] Ethereum Mainnet and Testnets - Upgrade to Erigon v3.5.5 and Reth v2.5.0

Discusión de la comunidad

Acerca del monitoreo de Quicknode en Uptimus

Cómo monitorea Uptimus Quicknode

Preguntas Frecuentes

Uptimus vs Downdetector para Quicknode

[Standard] Polkadot - Mainnet - Upgrade to v1.24.1

[Standard] Morph - Mainnet & Hoodi - Upgrade to morph-v2.2.5 & node-v0.6.1

[Standard] OP Stack - Mainnets & Testnets - Upgrade to op-reth v2.4.1 & op-node v1.19.4

[Standard] Gnosis - Mainnet - Upgrade to Nethermind v1.39.3

[Standard] Japan Open Chain - Nethermind v1.39.3

[Urgent] Zcash Mainnet & Testnet - Zebra 6.3.0

How would you rate Quicknode over the last month?