No — Fireblocks is operational.

Where does Uptimus get the official Fireblocks status?

Uptimus reads the official Fireblocks status source and normalizes its incidents, maintenance windows and component states. The links below let you verify the provider information directly. Fireblocks Status Page: https://status.fireblocks.com Fireblocks Home Page: https://www.fireblocks.com

Fireblocks says it is up, but I am having issues. What could be wrong?

The official page may not yet reflect a new incident, the problem may affect only a small group of accounts or one region, or it may be local to your device, network, software or ISP. Check the affected components and community reports above, test another connection or device, and contact Fireblocks support if the problem continues.

How can I check whether Fireblocks is having issues?

Compare the normalized status and recent incidents on this page with the official provider source. Uptimus keeps official component changes, maintenance, community reports and recent incident details together so you can distinguish a broad outage from a local problem.

How to get notified about Fireblocks outages?

Add Fireblocks to your Uptimus workspace, then choose the event types and delivery channels you want to use. Depending on your plan and configuration, alerts can be sent by email, push, webhook or configured integrations for major outages, smaller issues, maintenance and recovery. If Fireblocks exposes components, you can monitor all of them or restrict official alerts to the products your team uses.

Fireblocks Status, Incidents and Uptime

Loading status page

Checking service and reports...

About Fireblocks monitoring on Uptimus

Uptimus monitors Fireblocks through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.

This page currently includes 125 monitored components, 51 indexed incidents, 50 maintenance windows and 37 days of known history.

Uptimus is an independent monitoring service and is not affiliated with Fireblocks. A healthy status does not guarantee that every user, device or region is unaffected.

Outage notifications

Get notified when Fireblocks or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 51 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “FB539U: Blockchain TON Halt due to TON network issues”.

Issues notifications

Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 125 Fireblocks components: Algorand, Browser extension, Chainalysis AML, Transactions engine. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.

Maintenance notifications

Receive alerts when Fireblocks publishes planned, scheduled or active maintenance affecting the service. Uptimus has indexed 50 maintenance windows from the available Fireblocks history. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.

Recovery notifications

Know when Fireblocks or an affected component returns to healthy operation after an issue or outage. The current page contains 37 days of known status history, while resolved events remain available for later review. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.

Status messages

Uptimus stores the incident headline published by Fireblocks and presents it with the normalized service status. The available history contains 51 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “FB539U: Blockchain TON Halt due to TON network issues”.

Status details

Incident and maintenance updates are preserved so you can follow investigations, mitigations and recovery progress. A recent official update preserved by Uptimus reads: “This incident has been resolved.”.

Component status filtering

Choose all components or only the Fireblocks products you use. Official alerts then respect that component selection. Uptimus currently tracks 125 Fireblocks components: Algorand, Browser extension, Chainalysis AML, Transactions engine. Filtering changes which official alerts are delivered; it does not remove the provider's events from the public history.

Fireblocks Status

Recent outage reports

No recent outage reports

Report a problem

Service uptime history

Fireblocks: Recent outages and issues

Fireblocks outage map

See where reports are coming from

Fireblocks tracked components

About Fireblocks monitoring on Uptimus

Frequently Asked Questions

Get notified when Fireblocks changes status