We've completed an hour of monitoring with no further issues. Gas estimates on Polygon Mainnet are now fully aligned with the Chicago hardfork, and the paymaster verification gas limits are returning expected values. This incident is resolved. We apologize for any disruption and appreciate your patience while we worked through the fix.

We've released a fix that aligns the execution gas cost with the new hard fork. We're monitoring the situation.

Update: We've released a second fix that adjusts the verification gas limits returned by the paymaster. We're monitoring the situation.

Polygon Mainnet has undergo a Chicago Hardfork.

The HF updates gas costs for selected EVM opcodes and precompiles. We're now working on updating our services to align with the execution cost.

https://forum.polygon.technology/t/bor-v2-8-0-and-erigon-v3-6-0/21875

We've detected errors in gas estimates on polygon. We're investigating the root cause and will return back with updates asap.

Incident: All three price-feed sources for the XAUT paymaster failed simultaneously, preventing live quotes.

Cause: Suspected regional infrastructure failure. External price providers rely on the Cloudflare Frankfurt node, which reported downtime during the incident.

Action Plan: We are diversifying our oracle infrastructure to remove regional dependencies.

Our Paymaster Gas Sponsorship Service experienced intermittent downtime on the networks mentioned above on October 31st from approximately 06:50 AM UTC to 08:43 AM UTC. This caused some users attempting sponsored gas transactions to receive error messages. The issue was identified, and the service is now fully operational.

When the issue occurred, sponsored transactions failed, showing a calldata revert error. Our team quickly found the root cause of a configuration error. We deployed a fix, and all services are now stable.

We apologize for the inconvenience and appreciate your patience. We are maintaining heightened monitoring to ensure ongoing stability. If you run into any more issues, please let us know immediately.

• The issue has been resolved.

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

• The Polygon core team introduced a hot fix, which introduced a performance degradation in both Bor and Erigon execution layer clients. As a result, node synchronization is adversely affected. Further updates will be shared we monitor the node updates.

• We are currently observing a protocol-wide halt on the Polygon mainnet at block height 74,592,238. This disruption is impacting transaction finalization, block propagation, and all dependent network operations.

• All services are now fully operational and the gnosis chain issue has been resolved

• We've resolved the issue with Gnosis chain where user operations were processing correctly. We've deployed the fix and now monitoring the situation closely.

• We've spotted a particular issue with Gnosis chain where user operations aren't processing correctly. We're on it and investigating now. Will keep you posted.

• We've identified an general outage across our services.