De onde o Uptimus obtém o status oficial do Quicknode?

O Uptimus consulta a fonte oficial do Quicknode e normaliza incidentes, manutenções e estados dos componentes. Os links abaixo permitem verificar diretamente as informações do provedor. Quicknode Status Page: https://status.quicknode.com Quicknode Home Page: https://www.quicknode.com

O Quicknode informa que está funcionando, mas tenho problemas. O que pode ser?

A página oficial pode ainda não mostrar um incidente novo, o problema pode afetar poucas contas ou uma região, ou ser local ao dispositivo, rede, software ou provedor de internet. Confira componentes e relatos, teste outra conexão e procure o suporte do Quicknode se continuar.

Como verificar se o Quicknode está com problemas?

Compare o status normalizado e os incidentes recentes com a fonte oficial. O Uptimus reúne mudanças de componentes, manutenção, relatos da comunidade e detalhes dos incidentes para diferenciar uma falha ampla de um problema local.

Como receber notificações sobre interrupções do Quicknode?

Adicione Quicknode ao workspace do Uptimus e escolha os tipos de evento e canais de entrega. Conforme o plano e a configuração, alertas de falhas, problemas, manutenção e recuperação podem ser enviados por e-mail, push, webhook ou integrações configuradas. Se o Quicknode publicar componentes, você pode monitorar todos ou limitar os alertas oficiais aos produtos usados pela equipe.

Last checked 12 de ago., 21:03 UTC

Quicknode status

Q: Quicknode está fora do ar?

Parcialmente — Quicknode relata serviço degradado.

Blockchain infrastructure for secure, decentralized innovation.

Experiencing an issue?

Quicknode está fora do ar?

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 de ago., 21:03 UTC
Official incident active
Flare Mainnet Degraded Performance - Sporadic 503 Errors — We are continuing to monitor for any further issues.
Official provider status
12 de ago., 20:35 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 de ago., 17:34 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 de ago., 17:02 UTC

Quicknode outage reports

0 outage reports in the last 24 hours.

Nenhum relato recente de indisponibilidade

A comunidade não enviou relatos de indisponibilidade para este serviço nas últimas 24 horas.

Quicknode status history

Official status observations, not measured service uptime.

Last 60 daysDaily history

Loading history…

Operacional
Problemas
Indisponibilidade
Manutenção
Sem dados

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 de ago. de 202615:42 UTC	Yes	Minor
Official statusResolved	16h 35m	12 de ago. de 202604:00 UTC	Yes	Major
Official statusResolved	8h 54m	11 de ago. de 202616:32 UTC	Yes	Minor
Official statusResolved	6h 48m	10 de ago. de 202612:12 UTC	Yes	Minor
Official statusResolved	2h 34m	8 de ago. de 202614:14 UTC	Yes	Minor
Official statusResolved	30m	8 de ago. de 202606:30 UTC	Yes	Minor
Official statusResolved	54m	7 de ago. de 202600:41 UTC	Yes	Unknown
Official statusResolved	2h 58m	6 de ago. de 202621:19 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 20 Eost 2026, 00:00 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 19 Eost 2026, 14:00 UTC · Ongoing

Sobre o monitoramento de Quicknode no Uptimus

O Uptimus monitora Quicknode pela fonte oficial e normaliza incidentes, manutenções e componentes em um status consistente.

Esta página inclui atualmente 594 componentes monitorados, 86 incidentes, 148 manutenções e 57 dias de histórico conhecido.

O Uptimus é um serviço independente e não é afiliado ao Quicknode. Um status saudável não garante que todos os usuários, dispositivos ou regiões estejam sem problemas.

Como o Uptimus monitora Quicknode

Receba alertas quando Quicknode ou um componente monitorado informar uma falha grave ou crítica. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas. O histórico disponível contém 86 incidentes indexados e oferece contexto além do status atual. Um incidente recente indexado foi “Flare Mainnet Degraded Performance - Sporadic 503 Errors”.

Receba alertas sobre desempenho degradado, impacto parcial e incidentes que não representam uma falha completa. O Uptimus monitora atualmente 594 componentes do Quicknode. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.

Notificações de manutenção

Receba alertas quando Quicknode publicar manutenção planejada, programada ou ativa. O Uptimus indexou 148 janelas de manutenção do histórico disponível do Quicknode. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.

Notificações de recuperação

Saiba quando Quicknode ou um componente afetado voltar ao funcionamento saudável. A página contém 57 dias de histórico conhecido e mantém eventos resolvidos para análise. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.

Mensagens de status

O Uptimus armazena o título do incidente publicado por Quicknode e o mostra com o status normalizado. O histórico disponível contém 86 incidentes indexados e oferece contexto além do status atual. Um incidente recente indexado foi “Flare Mainnet Degraded Performance - Sporadic 503 Errors”.

Detalhes do status

As atualizações de incidentes e manutenção são preservadas para acompanhar investigação, mitigação e recuperação. Uma atualização oficial recente preservada pelo Uptimus diz: “We are continuing to monitor for any further issues.”.

Filtro de componentes

Escolha todos os componentes ou apenas os produtos Quicknode usados. Os alertas oficiais respeitam essa seleção. O Uptimus monitora atualmente 594 componentes do Quicknode. O filtro altera os alertas oficiais entregues, mas não remove eventos do histórico público.

Perguntas frequentes

Similar services

Comparison

Uptimus vs Downdetector para Quicknode
Critérios de comparação	Uptimus	Downdetector
Relatos da comunidade 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 18 Eost 2026, 14:00 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 13 Eost 2026, 14:00 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 13 Eost 2026, 14:00 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 13 Eost 2026, 11:00 UTC · Ongoing

Quicknode status

Having issues with Quicknode?

Quicknode service health graph

Quicknode activity

Latest activity

Quicknode outage reports

Mapa de interrupções do Quicknode

Mapa de interrupções do 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

Discussão da comunidade

Sobre o monitoramento de Quicknode no Uptimus

Como o Uptimus monitora Quicknode

Perguntas frequentes

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?