QuickNode Status

Resolved: This incident has been resolved.

Investigating: The Osmosis network stopped producing blocks at 22:57 UTC (block 74,955,152), affecting all providers, and Quicknode endpoints will resume serving new blocks as soon as the network restarts.

Resolved: Moca Testnet has been fully restored following a short-notice network upgrade to v1.5.0. All nodes are back online and operating normally. We apologize for any disruption experienced during this window.

Investigating: We are investigating degraded performance affecting Moca Testnet. A short-notice network upgrade has caused our nodes to halt, resulting in 503 errors for endpoint requests. The Quicknode team is actively working to restore service. The chain itself is healthy and the public RPC is at tip. We will provide updates as more information becomes available.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: Our engineers are upgrading to https://github.com/circlefin/arc-node/releases/tag/v0.8.5

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been applied and Quicknode Polygon Amoy Testnet endpoints are serving current block data again. We are monitoring to make sure the service stays stable.

Identified: We have identified the cause of the issue affecting Polygon Amoy Testnet endpoints. Users may be experiencing stale block data and elevated 503 errors. The Amoy network itself is producing blocks normally. Our team is actively applying a fix and we will provide further updates as work progresses.

Investigating: Polygon Amoy Testnet appears to have stalled at block 52,676,095 - The Quicknode team is investigating and will update with more information once it is available.

Resolved: Injective mainnet nodes have caught up to the chain tip and endpoints are operating normally. Thanks for your patience while we worked on this.

Monitoring: A fix has been applied and Injective mainnet nodes are now catching up to the chain tip. Endpoints may still return slightly delayed data until they're fully synced. We're monitoring closely and will post an update once everything is back to normal.

Investigating: Ahead of the scheduled Injective network upgrade (Nov 11, 12:00–14:00 UTC), our Injective mainnet nodes fell behind the chain tip and endpoints may return stale data. A fix is being applied and nodes will resync once it's in place. We'll post an update when service is fully restored.

Resolved: This incident has been resolved.

Investigating: Injective is conducting a scheduled mainnet upgrade test in coordination with its validators, as part of preparations for an upcoming network upgrade. During this window, block production on Injective mainnet may be paused or delayed, and requests to Injective endpoints may return stale data or errors.

This is a chain-wide event and is not related to Quicknode infrastructure. We are in contact with the Injective team and will post an update once normal network operations resume.

Resolved: The issue affecting RPC Logs has been resolved. Transaction and error logs are now operating normally. Please note that log data may show inaccuracies roughly between 15:10 UTC - 16:25 UTC. We apologize for any inconvenience caused.

Investigating: We are investigating an issue affecting transaction and error log serving. Our engineers are actively working on a fix and will provide updates as more information becomes available.

Resolved: This incident has been resolved.

Monitoring: An upstream stall on Hyperliquid's HyperEVM testnet caused transaction submissions to fail from about 03:00 UTC. The upstream recovered at about 12:00 UTC, and transaction submission through Quicknode HyperEVM testnet endpoints has been operating normally since then. We are monitoring to make sure it stays stable.

Investigating: The Quicknode team is investigating the degraded performance of HypeEVM testnet nodes. Customers may experience a high TX drop rate. We will provide an update as more information becomes available.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are investigating elevated response times and timeouts affecting endpoints in the FRA region. Our team is actively investigating and will provide updates as more information becomes available.