Is Figment down?

**Affected components:** API Services Figment's core APIs are experiencing intermittent errors and slow response times. Service briefly returned to normal shortly after the issue began, but degraded performance has since recurred. Our team is actively working to restore full stability and will post the next update as soon as we have more to share..

All services are fully restored and running normally following the incident resolution..

**Incident Summary:** The Ethereum indexer stopped due to sustained request timeouts on a third-party RPC provider's Beacon REST API, causing Figment APIs and Rated APIs to fall behind on Ethereum data. The issue has since been resolved. **Status:** Resolved **Impact:** Customers using the Rewards, Reward Rates, and Rated APIs experienced missing or delayed data for Ethereum due to the indexer downtime, with data running up to 1 hour behind. The indexer has since caught up and data is current. **Affected Services:** Figment APIs (Rewards, Reward Rates) and Rated APIs for Ethereum. **Start Time:** Sept 16, 2026 - 07:10 UTC. **Resolution Time:** Sept 16, 2026 - 09:00 UTC. **Resolution:** Figment notified the third-party RPC provider of the timeouts on the beacon rewards endpoints. The provider identified elevated network load on their end and added capacity to resolve it. Figment confirmed the indexer had fully caught up. As a follow-up, Figment plans to test additional RPC providers as an automated backup for this endpoint. **Root Cause:** The third-party RPC provider experienced elevated network load, causing a burst of HTTP 429s followed by sustained request timeouts on the Ethereum Beacon REST rewards endpoints; this was not caused by Figment..

This incident has been resolved..

**Incident Summary:** Intermittent failures signing and broadcasting NEAR and SUI transactions in FigApp for customers using Fireblocks via WalletConnect. **Status:** Actively Managing — Figment is coordinating with Fireblocks to isolate the cause. **Impact:** Affected customers had NEAR and SUI transactions that signed successfully in Fireblocks but did not reflect as broadcast or confirmed in FigApp, delaying visibility into withdrawals and stakes. **Affected Services:** FigApp NEAR and SUI transaction flows via the Fireblocks WalletConnect integration. **Resolution Time:** Ongoing. **Resolution:** Figment has engaged Fireblocks to review the signing and broadcast flow and has advised affected users to disconnect and re-establish a fresh WalletConnect session as a temporary workaround while the cause is isolated..

We have deployed an update to improve our WalletConnect error detection logic. The issue is now fully resolved, and all related services are operating normally..