A fix has been implemented and we are monitoring the results.
Posted Nov 22, 2025 - 07:24 UTC
Identified
Our team has identified a bug in the latest release of the Polygon-Amoy client that is causing node instability. This issue has been brought to the attention of the Foundation, and we are actively working on a solution. While our work toward full recovery continues, the previously mentioned trace methods will remain disabled. Customers may also experience sporadic 503 errors.
We will provide another update by 6:00 UTC, or sooner.
Posted Nov 20, 2025 - 22:37 UTC
Monitoring
Our nodes are back at the chain tip, healthy, and 503 errors have cleared. To accelerate stabilization, we have temporarily blocked the following high-load methods: • trace_filter • debug_traceBlockByNumber • debug_traceBlockByHash • debug_traceTransaction • debug_traceCall We will provide another update by 23:00 UTC, or sooner.
Posted Nov 20, 2025 - 05:52 UTC
Identified
Our nodes are in the process of recovering, and 503 error rate is dropping. To expedite recovery, we have temporarily blocked the following resource-intensive methods: trace_filter debug_traceBlockByNumber debug_traceBlockByHash debug_traceTransaction debug_traceCall
We will provide another update by 03:30 UTC
Posted Nov 19, 2025 - 22:50 UTC
Investigating
We are currently experiencing elevated 503 errors on Polygon-Amoy. Our team is working to restore nodes fully, but customers may encounter an increased 503 error rate in the meantime. We will share another update by 23:30 UTC
Posted Nov 19, 2025 - 22:31 UTC
This incident affected: Polygon (Polygon - Amoy Testnet).