Live  /  Fireblocks  /  Incident

Fireblocks: FB560U: Transactions and balance updates issues on Ripple blockchain

Fireblocks · fireblocks.comMinor incidentResolved2026-10-09 15:58 UTC
Public — what happened

Summary

Fireblocks reported a minor problem on October 9, 2026, in which transactions and balance updates on the Ripple blockchain were affected. The company said its transaction processing systems were having trouble completing Ripple transactions, beginning around 15:15 UTC, and posted that it was looking into the matter. Fireblocks did not name a cause in its update, and it marked the incident as resolved at 15:55.

Affected

Ripple

As listed on Fireblocks’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Fireblocks against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Fireblocks: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Fireblocks report →

More from Fireblocks

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Fireblocks status & history page.

Related: Fireblocks status & history. SquidGrid is not affiliated with Fireblocks.