QuickNode outage, 13 November 2026

Moca Testnet Degraded Performance - Short-Notice Network Upgrade

Started
Resolved
13 Nov 2026, 12:44 UTC (after 1 h 26 min)
Impact
Not stated
Affected
Moca - Testnet

Is this still happening?

No. QuickNode marked this incident resolved on 13 Nov 2026, 12:44 UTC, 1 h 26 min after it began.

Right now: QuickNode reports all systems operational. (as of 13 Nov, 20:53 UTC) Live QuickNode status

At a glance

Our summary from the QuickNode incidents we have recorded since 24 Sept 2026 - how we count.

Last update from QuickNode

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.

13 Nov 2026, 12:44 UTC

Read the full incident on the official QuickNode status page

Similar QuickNode incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 2 h 39 min

    Polygon Amoy Testnet Network Stalled at Block 52,676,095

  2. , resolved after 13 h 1 min

    Injective Mainnet - Scheduled Network Upgrade Test

  3. , resolved after 2 h 15 min

    Polygon Amoy Testnet - Degraded Performance During Network Stress Test

  4. , resolved after 37 min

    XRPL EVM Mainnet Network Upgrade - Service Disruption

  5. , resolved after 12 h 21 min

    Solana Testnet: Planned network halt

Other recent QuickNode incidents

  1. Arc testnet : Block height stalled at 72189798

  2. Osmosis Mainnet - Network-Wide Stall at height 74,955,152

  3. Injective Mainnet - Nodes Out of Sync Ahead of Scheduled Upgrade

  4. Elysium Mainnet - Elevated Errors on eth_sendRawTransaction

  5. RPC Logs - Service Disruption

  6. Elysium Mainnet - Transaction Submission Errors

  7. Degraded Performance - HypeEVM Testnet

  8. Elevated Response Times and Timeouts - FRA Region

All recorded QuickNode incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from QuickNode's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.