Is Polygon Down?

The issue is now resolved. --- [2026-07-30T08:12:40Z] (monitoring) Monitoring — Wallet values restored on Polygon Portal A fix has been applied and the issue is resolved. Polygon Portal is once again displaying correct USD wallet values and per-token prices. The price feed is successfully fetching data again, and confirmed wallets now show accurate totals. Recap: For a period earlier today, the Portal displayed $0.00 wallet values because our price service was temporarily unable to retrieve token prices from an upstream market-data provider. This was a display-only issue — token balances and on-chain funds were never affected. We're now monitoring the price feed for the next ~30 minutes to confirm full stability before marking this fully resolved. What you should see: correct wallet values across all tokens. If you still see $0, a hard refresh should clear it.If you still see issue persist create a support ticket. Thanks for your patience --- [2026-07-30T05:00:44Z] (identified) Polygon Portal is currently displaying $0.00 total wallet value, with every token priced at $0, for users on mainnet. This is a display issue only your funds are safe and balances are accurate. What's happening Our balance service's price feed is temporarily unable to retrieve token prices from an upstream market-data provider, which is rate-limiting our requests. When prices come back empty, the Portal renders them as $0. This affects all tokens (e.g. USDC, USDT, WETH, POL), not any specific asset. What is not affected - Your actual token balances are correct and fully intact. - On-chain funds are safe — nothing has moved or changed. - Wallet connectivity and RPC across all supported chains are healthy. - Only the USD price/value display is currently incorrect. What you can do No action needed. Balances will show correct values automatically once the price feed recovers. You can verify holdings independently on a block explorer (e.g. PolygonScan) in the meantime.

The issue affecting the OMS X dashboard, caused by a global CloudFront outage, has been resolved. Dashboard functionality is back to normal, and we've confirmed there's no ongoing impact. For further details, you can refer to the incident here: <https://status.frontegg.com/incidents/7l2gprx3y1fr> Thank you for your patience while we worked through this. --- [2026-07-16T10:15:35Z] (monitoring) We identified the issue affecting the OMSX dashboard as a global CloudFront outage that occurred a few minutes ago. The root cause has been isolated and we are currently monitoring the situation to confirm full recovery. You can follow further updates here: <https://status.frontegg.com/incidents/7l2gprx3y1fr> We'll continue to provide updates until this is resolved. --- [2026-07-16T09:58:13Z] (investigating) 🔴 Investigating — OMSX Dashboard Unavailable We're currently experiencing an outage affecting the OMSX dashboard. Users may be unable to load or access the dashboard at this time. Our team is actively investigating the cause and working to restore service as quickly as possible. We'll post another update within the next 30 minutes, or sooner if the situation changes. Thank you for your patience.

**Date:** June 24–25, 2025**Time:** **19:00 UTC \(June 24\) – 02:30 UTC \(June 25\)Status:** Resolved**Affected Services:** • Amoy Heimdall Services \(Validator Sync, APIs\) • Amoy Staking Dashboard **Summary** On June 24–25, 2025 \(UTC\), the Polygon Labs team conducted a planned upgrade of the **Heimdall layer on the Amoy testnet**, migrating from **V1 to V2**. This served as a full test run ahead of the Mainnet deployment. During the 7.5-hour window, Heimdall on Amoy was paused. This temporarily affected validator syncing, checkpoint processing, and Heimdall-dependent APIs. **Bor continued block production throughout** with no chain downtime. **Technical Overview** • Heimdall V1 was halted at the final testnet checkpoint. • State was exported and used to generate a V2 `genesis.json`. • Nodes were upgraded to Heimdall V2 and re-initialized on `heimdallv2-amoy`. • APIs and dashboards resumed after V2 sync completed. **Resolution** By **02:30 UTC on June 25**, Heimdall V2 was fully deployed and synced across Amoy validators. Testnet services were verified operational and stable. --- [2026-07-16T06:06:39Z] (resolved) Planned Migration – Heimdall V1 → V2(Amoy)