Partially — Quicknode is reporting degraded service.

Where does Uptimus get the official Quicknode status?

Uptimus reads the official Quicknode status source and normalizes its incidents, maintenance windows and component states. The links below let you verify the provider information directly. Quicknode Status Page: https://status.quicknode.com Quicknode Home Page: https://www.quicknode.com

Quicknode says it is up, but I am having issues. What could be wrong?

The official page may not yet reflect a new incident, the problem may affect only a small group of accounts or one region, or it may be local to your device, network, software or ISP. Check the affected components and community reports above, test another connection or device, and contact Quicknode support if the problem continues.

How can I check whether Quicknode is having issues?

Compare the normalized status and recent incidents on this page with the official provider source. Uptimus keeps official component changes, maintenance, community reports and recent incident details together so you can distinguish a broad outage from a local problem.

How to get notified about Quicknode outages?

Add Quicknode to your Uptimus workspace, then choose the event types and delivery channels you want to use. Depending on your plan and configuration, alerts can be sent by email, push, webhook or configured integrations for major outages, smaller issues, maintenance and recovery. If Quicknode exposes components, you can monitor all of them or restrict official alerts to the products your team uses.

Last checked Aug 12, 9:03 PM UTC

Quicknode status

Blockchain infrastructure for secure, decentralized innovation.

Experiencing an issue?

Is Quicknode down?

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
Aug 12, 9:03 PM UTC
Official incident active
Flare Mainnet Degraded Performance - Sporadic 503 Errors — We are continuing to monitor for any further issues.
Official provider status
Aug 12, 8:35 PM 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
Aug 12, 5:34 PM 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
Aug 12, 5:02 PM UTC

Quicknode outage reports

0 outage reports in the last 24 hours.

No recent outage reports

No community outage reports have been submitted for this service in the last 24 hours.

Quicknode status history

Official status observations, not measured service uptime.

Last 60 daysDaily history

Loading history…

Operational
Issues
Outage
Maintenance
No data

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	634h 36mOngoing	Aug 12, 20263:42 PM UTC	Yes	Minor
Official statusResolved	16h 35m	Aug 12, 20264:00 AM UTC	Yes	Major
Official statusResolved	8h 54m	Aug 11, 20264:32 PM UTC	Yes	Minor
Official statusResolved	6h 48m	Aug 10, 202612:12 PM UTC	Yes	Minor
Official statusResolved	2h 34m	Aug 8, 20262:14 PM UTC	Yes	Minor
Official statusResolved	30m	Aug 8, 20266:30 AM UTC	Yes	Minor
Official statusResolved	54m	Aug 7, 202612:41 AM UTC	Yes	Unknown
Official statusResolved	2h 58m	Aug 6, 20269:19 PM 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

About Quicknode monitoring on Uptimus

Uptimus monitors Quicknode through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.

This page currently includes 594 monitored components, 86 indexed incidents, 148 maintenance windows and 57 days of known history.

Uptimus is an independent monitoring service and is not affiliated with Quicknode. A healthy status does not guarantee that every user, device or region is unaffected.

How Uptimus monitors Quicknode

Get notified when Quicknode or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 86 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “Flare Mainnet Degraded Performance - Sporadic 503 Errors”.

Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 594 Quicknode components. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.

Maintenance notifications

Receive alerts when Quicknode publishes planned, scheduled or active maintenance affecting the service. Uptimus has indexed 148 maintenance windows from the available Quicknode history. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.

Recovery notifications

Know when Quicknode or an affected component returns to healthy operation after an issue or outage. The current page contains 57 days of known status history, while resolved events remain available for later review. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.

Status messages

Uptimus stores the incident headline published by Quicknode and presents it with the normalized service status. The available history contains 86 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “Flare Mainnet Degraded Performance - Sporadic 503 Errors”.

Fair questions, straight answers.

Similar services

Comparison

Uptimus vs Downdetector for Quicknode
Comparison criteria	Uptimus	Downdetector
Community outage reports for 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

Quicknode outage map

Quicknode outage map

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

Community Discussion

About Quicknode monitoring on Uptimus

How Uptimus monitors Quicknode

Fair questions, straight answers.

Uptimus vs Downdetector for 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?