Live  /  Quicknode  /  Incident

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

Quicknode · quicknode.comMinor incidentResolved2026-11-12 18:54 UTC
Public — what happened

Summary

Quicknode said its Polygon Amoy Testnet service appeared to stop advancing at block 52,676,095, and it began investigating at 16:14 UTC on 2026-11-12. About an hour later it said it had found the cause, noting that users might see outdated block data and a higher number of 503 errors, while the Amoy network itself was still producing blocks normally. By 18:13 UTC Quicknode said a fix was in place and its endpoints were again returning current data, and it kept watching for stability. The incident was marked resolved at 18:54 UTC.

Affected

Polygon - Amoy Testnet

As listed on Quicknode’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Quicknode against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Quicknode: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Quicknode report →

More from Quicknode

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Quicknode status & history page.

Related: Quicknode status & history. SquidGrid is not affiliated with Quicknode.