Live / Providers / Fireblocks
Fireblocks
fireblocks.comNo open incidents
SaaS & business software · SquidGrid tracks Fireblocks’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.
Public — what Fireblocks is reporting
Current & recent incidents
ResolvedFB567U: Authentication Issues with Fireblocks Console and API
Minor impact · 2026-10-30 06:47 UTC · source
ResolvedFB561U: Delayed Webhook notifications and new webhook creation
Minor impact · 2026-10-14 08:35 UTC · source
ResolvedFB559U: Transaction Processing Issue
Minor impact · 2026-10-06 09:55 UTC · source
Track record
SquidGrid has archived 9 incidents from Fireblocks’s own status page since 2026-09-08.
- Median time from first post to resolved: 52 min (last 180 days)
- Longest in the last 90 days: 4 h
- Most recent incident: 16 days ago
- Status page last checked 2026-11-16 01:24 UTC
Recent incidents in the archive
With SquidGrid — where the route changes
Independent path health
A status page tells you what Fireblocks has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.
Fireblocks runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Fireblocks is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.
🔒 Sign in to see
Incident track record: 90-day trend, median and worst time to fix
What tends to break, from their own incident write-ups
Recent public reports of problems with this service
Included with any paid plan.
See the full report →