Fireblocks logo

Is Fireblocks Down?

SaaSLive status, outages, and incident history

No. Fireblocks is up right now.

Every monitored Fireblocks system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Fireblocks breaks

Fireblocks is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Fireblocks status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Fireblocks Component Status

The main Fireblocks systems on this page. All 123 are operational right now.

123operational
API
Operational
API co-signer
Operational
Audit logs
Operational

120 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Automation Engine, Blockchain nodes » Aevo, Blockchain nodes » Algorand, Blockchain nodes » Arbitrum, Blockchain nodes » Astar, Blockchain nodes » Aurora, Blockchain nodes » Avalanche, Blockchain nodes » Axelar, Blockchain nodes » Base, Blockchain nodes » Berachain, Blockchain nodes » Binance Smart Chain, Blockchain nodes » Bitcoin, and 108 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Fireblocks Outages & Incidents

Incident history from the official Fireblocks status page, including resolution updates.

System Maintenance on October 4th, 2026 - Oct 15, 2026Scheduled for Oct 4, 2026 · 276h 0mScheduled

Our system will undergo daily maintenance to enhance security on October 4th, 2026, 08:00 UTC, until Oct 15, 2026, 20:00 UTC. During the maintenance, our system will remain online and functional. We will update accordingly once the maintenance is completed.

Cosmos Mainnet Network StalledScheduled for Sep 22, 2026 · 1h 0mScheduled

The scheduled maintenance has been completed. --- [2026-09-23T12:53:02.703Z] (verifying) Verification is currently underway for the maintenance items. --- [2026-09-22T12:12:08.885Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-22T12:11:48.397Z] (scheduled) Currently, the Cosmos infrastructure (not Fireblocks infrastructure) is experiencing unplanned downtime. Cosmos Mainnet appears to have stalled. Fireblocks operations will resume once the issue is resolved.

FB558U: Plasma Node IssuesResolved Sep 16, 2026 · 2h 21mResolved

This incident has been resolved. --- [2026-09-16T13:17:27.769Z] (monitoring) We are continuing to monitor for any further issues. --- [2026-09-16T13:08:33.859Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-16T12:40:43.512Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-09-16T12:40:18.646Z] (investigating) We are continuing to investigate this issue. --- [2026-09-16T12:39:58.733Z] (investigating) We are currently investigating this issue.

Fireblocks Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Fireblocks incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 8 days with incidentsSep 25

Live Fireblocks Outage Reports

Problems reported by engineers using Fireblocks. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Fireblocks problems reported yet.

Something wrong with Fireblocks on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Fireblocks

Is Fireblocks down? Fireblocks reports live availability for 126 components at status.fireblocks.com, among them Algorand, Transactions engine and Chainalysis AML. Track Fireblocks outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Fireblocks uptime at 100.00%. Response times, incident history, and SLA tracking for Fireblocks are available on the PulsAPI dashboard.

Fireblocks Status FAQ

Is Fireblocks down right now?

The verdict at the top of this page comes from the latest poll of the official Fireblocks status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Fireblocks is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Fireblocks recovers.

How do I check Fireblocks uptime history?

PulsAPI tracks Fireblocks uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Fireblocks changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Fireblocks outages?

PulsAPI reads the official Fireblocks status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Fireblocks components?

Yes. PulsAPI monitors 123 individual Fireblocks components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Fireblocks goes down?

Yes. Create a free account and subscribe to Fireblocks: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Fireblocks to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Fireblocks problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Fireblocks?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Fireblocks plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Fireblocks with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services