Polygon mainnet : Network-wide issues with both Bor and Erigon node clients

All Polygon mainnet Bor and Erigon nodes have been fully restored and are operating normally. We will continue monitoring to ensure stability and address any potential issues.
Thank you for your patience.

Most of the Bor and Erigon nodes have recovered and are now serving requests. We are actively monitoring performance and working to restore service to full capacity.

We will provide the next update by 12:00 UTC or sooner.

The Bor nodes have been recovered, and the QuickNode team is working closely with the foundation to fully recover the Erigon nodes.
We will provide the next update by 07:00 UTC or sooner.

We are working closely with the Polygon Foundation and monitoring Erigon nodes as they re-sync.

Impact: Polygon API and Polygon Streams may return null responses or fail on some calls.
Customer Action: No action needed; retry affected calls with exponential backoff.

Next Update: By 03:30 UTC.

We have implemented Bor new release v2.2.11-beta2, our Bor nodes are recovered. We will continue to monitor the situation.
We expect to provide next update by 16:00 UTC.

Our Erigon nodes are showing signs of recovery; however, Bor nodes remain impacted at this time.

We’ve been informed that a new Heimdall and Bor release, which includes a Heimdall hardfork, is scheduled to go live in approximately 1 hour. The hardfork is expected to occur at 13:00 UTC. The Polygon Foundation will publish the new release once available, and we will begin deployment shortly thereafter.

We will provide the next update by 13:00 UTC.

Thank you for your patience.

Our engineers are closely listening to updates from the foundation.

As we progress toward a resolution, please expect the next update on or before 12:00 UTC.

https://status.polygon.technology/incidents/c8nc05x3qvmg

Our engineers are currently investigating issues with the Polygon mainnet node infrastructure (primarily impacting archive calls).

As we progress toward a resolution, expect the next update on or before 6:00 UTC.