PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Fireblocks is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Fireblocks. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Fireblocks issues today?

As of Oct 12, 2026 20:16 UTC, 0 users had reported issues with Fireblocks in the previous 24 hours.

How can I report a Fireblocks outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Other

Is Fireblocks down right now?

UnknownOfficial status last polled Oct 12, 2026 19:58 UTCfireblocks.com Official status page

Are you on the Fireblocks team and see something inaccurate? Report it to us. We respond within one business day.

Is Fireblocks down right now?

Unknown. Fireblocks does not have a conclusive current status. PulseWatch observations are not fully available. No all-clear is implied.

Status as of Oct 12, 2026 20:16 UTC

Unknown

Fireblocks: status unknown

As of Oct 12, 2026 20:16 UTC

Product-check coverage is unavailable. Overall service status has not been established.

Reports 24h

Last incident

Sep 16, 2026 16:10 UTC

Trend

0/15m

Monitoring

Coverage unavailable

PulseWatch observations are unavailable. No all-clear is implied.

Observed health

Unavailable

Current measurements are not available for a health score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Fireblocks.

Incident days

No recorded incident

7h 35m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Fireblocks. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

2 incidents

Busiest day

7h 35m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Fireblocks outage on September 16 — 2h 19m disruption

Sep 16, 01:51 PM → Sep 16, 04:10 PM · 2h 19m · medium

On September 16, Fireblocks experienced a service disruption. This incident was detected by automated monitoring systems and lasted for 2 hours and 19 minutes. The disruption was resolved at 16:10 UTC.

Duration

2h 19m

tracked by PulseWatch

Impact

During the 2-hour and 19-minute service disruption, Fireblocks experienced a medium-severity incident. This event was identified through automated monitoring and the vendor's own status page. No user-reported data was collected for this incident, and therefore no specific user-reported issue types or affected regions were recorded.

Incident timeline

Sep 16, 01:51 PM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
Sep 16, 01:51 PM
Status updated: possible issue
Sep 16, 04:10 PM
Signals cleared — incident resolved

Official updates

Sep 16, 01:51 PM
Fireblocks status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

98.9%

90-day uptime

99.52%

Calculated from Fireblocks's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

Fireblocks: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/16/2026, 1:51:02 PM · 2h 19m

01:51 PM04:10 PM

Detection9/16/2026, 1:51:02 PM · 26d ago

Detected — medium severity

ResolvedMedium

Fireblocks: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/13/2026, 3:11:22 AM · 2h 9m

03:11 AM05:20 AM

Detection9/13/2026, 3:11:22 AM · 29d ago

Detected — medium severity

Fireblocks: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

ResolvedMedium

Fireblocks: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/12/2026, 11:47:04 PM · 3h 18m

11:47 PM03:05 AM

Detection9/12/2026, 11:47:04 PM · 29d ago

Detected — medium severity

Fireblocks: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

ResolvedMedium

Fireblocks incident correlated across 1 signal group: official/vendor.

8/21/2026, 5:12:25 AM · 1h 29m

05:12 AM06:41 AM

Detection8/21/2026, 5:12:25 AM · 1mo ago

Detected — medium severity

Fireblocks incident correlated across 1 signal group: official/vendor.

ResolvedMedium

Fireblocks incident correlated across 1 signal group: official/vendor.

8/16/2026, 6:34:03 PM · 1h 3m

06:34 PM07:37 PM

Detection8/16/2026, 6:34:03 PM · 1mo ago

Detected — medium severity

Fireblocks incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Fireblocks enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

0 reports aggregated in last 24h
Crowdsourced baseline detection
Official status page

Live signal

Status: Normal
Monitoring: Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage: Verified against the vendor's own incident history
Reports (24h): 0
Baseline / hour: 5
Open threshold: 3x

Official site

fireblocks.com

Related services

01.AI

Other

Unknown

1Password

Other

Normal

AI21 Studio

Other

Normal